Mark Sapiro writes:
On 2/27/21 4:36 AM, Stephen J. Turnbull wrote:
is legal, and I think that most servers will accept it, but RFC 5321 sets a limit of 64 octets on mailboxes[1], and your confirmation mailbox is 67 octets.
Since the -confirm+<token> part is fixed at 49 octets, this would imply a limit in list names of 15 octets. Ouch!
I'm pretty sure we would have run into this before, if there were a lot of servers out there imposing this limit. 15 octets is pretty darn short, there are probably quite a few list names out there longer than that. Not to mention that the RFC itself says "you SHOULD NOT be a jerk about this". :-) So I don't think this is a big problem in practice, and I hope Steve can reconfigure the obstructive server to not be so picky.
For Mailman, I doubt we need a full SHA1 (?) for the purpose. We can truncate the thing, probably opportunistically (ie, so the whole confirmation mailbox fits in 64 octets, or we could even parse the bounce message and resend only if we run into a problem).
Steve