Re: [ietf-smtp] Proposal: Updating VERP Specification

Viruthagiri Thirumavalavan writes:

>    I don't see any way around this. I see no other ways to handle this.
>
>
>
> I'm not sure how viable this method is. I think the client should look for  
> MAIL FROM command response and then retry with a non VERP address when the  
> local-part exceed 64 characters.
>  
> 501 Syntax error in parameters or arguments
> 455  Server unable to accommodate parameters
> 555  MAIL FROM/RCPT TO parameters not recognized or not implemented
I see this as a trade-off. This is gambling that if this gets forwarded on  
with the original list of recipients, as is, any eventual bounce will be a  
parsable DSN. But if it's not, the original purpose of using VERPs – which  
is always being able to identify a bouncing address – has been defeated.  
Now, the mail robots is going to get stuck with undeliverable addresses that  
will bounce forever, and cannot be identified.

pgp0aJWUlAw7R.pgp
Description: PGP signature

_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp