Developers of Sympa

[Thomas Berry <address@concealed>]

David,

  Yes.   The problem we were having was difficult to troubleshoot; the  
logs did not really give us an idea of where the problem was occurring.  
I realized that the problem was with the send scenario only after I 
started sending test messages through a list with the same configuration.

  I believe that scenario logging would have provided some additional 
information that might have made the problem more obvious--although, 
it's possible that an increased log level might have also helped.

 Also, the ability to test Sympa generated messages, such as 
authorization reject messages, without actually sending a message with 
the conditions to force a rejection would have shown that the reject 
message the scenario was using had not yet been defined in 
reject_authorization.tt2.  Not having the actual reject context also 
helped to make the problem we had more difficult to identify.

Thomas

David Verdin wrote:
> Is it related to the problem you submitted yesterday about Sympa not 
> logging the scenario output ?
> Regards,
>
> Thomas Berry a écrit :
> > Version: Sympa 5.3.2
> >
> >   We are experiencing a problem with authentication.  Sympa is 
> > rejecting messages sent to lists which restrict posting to members or 
> > owners.  I found that the messages being rejected are those that have 
> > a sender address in the From header where the name before the email 
> > address is not surrounded by double-quotes, but the email address is 
> > surrounded by angle-brackets.
> >
> >   Having read through RFC 2822, it is not clear to me whether the 
> > name (phrase) must be surrounded by double-quotes.  I have run some 
> > tests with Thunderbird, but was unable to get it to fail when leaving 
> > the name unquoted.
> >
> >   This was initially brought to our attention last week; I suggested 
> > the name component be quoted or removed, which fixed the problem. 
> > But, yesterday I receive another call for a different list with the 
> > same problem.  I need to know if I should continue to require the 
> > sender email address on the From header be quoted which appearing 
> > before the email address, or (if RFC 2822 allows the name to be 
> > unquoted as long as the email address is surrounded by 
> > angle-brackets) is there a patch that can fix this sender 
> > authorization issue?
> >
> > Thomas