While it is true that https://www.rfc- editor.org/rfc/rfc5321.html#section-4.5.3.1.1 says:
The maximum total length of a user name or other local-part is 64 octets. https://www.rfc-editor.org/rfc/rfc5321.html#section-4.5.3.1 says: However, some Internet mail constructs such as encoded X.400 addresses (RFC 2156 [35]) will often require larger objects. Clients MAY attempt to transmit these, but MUST be prepared for a server to reject them if they cannot be handled by it. To the maximum extent possible, implementation techniques that impose no limits on the length of these objects should be used. As I read this, It is OK for an envelope sender local part to be longer than 64 octets as long as we are prepared for a reject, and MTAs should if possible be implemented to accept these. Also, I tested with Postfix and there was no problem sending my test which had an envelope sender local part of 104 octets. Thus, I don't want to disable VERP arbitrarily just because the VERPed local part exceeds 64 octets. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1905962 Title: local-part of VERP sender may exceed 64 octet To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1905962/+subscriptions _______________________________________________ Mailman-coders mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-coders.python.org/ Member address: [email protected]
