I've seen many asynchronous bounces where the local part is cut-off after 64 characters... It seems some mta's are pedantic in this regard.
Yours, David On 17 February 2018 at 18:46, John Levine <jo...@taugh.com> wrote: > In article <CAHVBJ+=-byOuu86w+Vk_Lme_C1MAeryp2c7Nw3tMsdtEi5d-_w@ > mail.gmail.com> you write: > >The use of IDs instead of the real original email in the return-path > >may also be because of length limits. > >Max length of an email address is 254 chars. If you have to insert it > >"almost clear" in a return path and change the domain then there are > >chance your return-path address will be more than 254 chars. > >so if your original address is "a 242 ti...@example.com" how do you > >add VERP to it without some sort of obfuscation? > > Actually, you're more likely to hit the local-part limit of 64 first, > but how many real addresses (as opposed to artificial stress tests > ones) have you seen where that's a problem? > > I'm not opposed to using tokens but I don't see it as a security > issue, just something that might save a lookup in bounce processing. > > R's, > John > > _______________________________________________ > mailop mailing list > firstname.lastname@example.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > -- -- My opinion is mine.
_______________________________________________ mailop mailing list email@example.com https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop