[Mailman-Users] Case-Sensitivity Problem?

[Ryan Steele]

I think I've actually identified the problem. 

Here is an excerpt from the mail header:

>Received: from FOO at aol.com
>         by imo-m26.mx.aol.com (mail_out_v38_r7.6.) id e.cef.43ab224 (57293);
>         Wed, 13 Dec 2006 09:41:44 -0500 (EST)
>From: FOO at aol.com
>Message-ID: <cef.43ab224.32b16b26 at aol.com>
>Date: Wed, 13 Dec 2006 09:41:42 EST

And here is a message from Mailman's bounce log:

 >Dec 13 09:42:38 2006 (2202) bounce message w/no discernable addresses: 
<cef.43ab224.32b16b26 at aol.com>
 >Dec 13 09:42:38 2006 (2202) forwarding unrecognized, message-id: 
<cef.43ab224.32b16b26 at aol.com>

For whatever reason, Mailman treated the message-id that AOL gave it as 
the sender address...thus causing the "Uncaught bounce notification" 
error.   The actual bounce occurred because it was sent for moderator 
approval due to the large number of recipients:

 >vette:Dec 13 09:38:51 2006 (2204) Igcpgrads post from foo at aol.com 
held, message-id=<cce.5a1853c.3
 >2b16a2d at aol.com>: Too many recipients to the message

Thank you for your insight about the RFC's though, Paul.  More 
disconcerting is the fact that Mailman seemed unable to extract the 
sender's email address from the bounce?  I'm running 2.1.8, if that's of 
any concern to the devs out there...


Best Regards,
Ryan

Paul Tomblin wrote:
> Quoting Ryan Steele (steele at agora-net.com):
>   
>>  From reading the docs, I thought that (for list membership purposes), 
>> the email addresses were case insensitive, thus complying with RFC 822.  
>>     
>
> RFC 822 says that the part before the @ sign *can* be case sensitive.  So
> the behavour you're seeing is allowed by RFC 822.
>
>   


-- 
Ryan Steele                         
Systems Administrator               steele at agora-net.com
AgoraNet, Inc.                      (302) 224-2475
314 E. Main Street, Suite 1         (302) 224-2552 (fax)
Newark, DE 19711                    http://www.agora-net.com