The mailing list for listmasters using Sympa

["Patrick von der Hagen" <address@concealed>]

Am Dienstag, den 17.10.2006, 08:13 +0200 schrieb address@concealed:
[...]
> Looking at Sympa authorization scenario can show you that there is not a 
> static definition of allowed message senders. A message can be rejected 
> because of an attachment or some header or because some  complex 
> condition (example : user is not from domain X and then can't send 
> message with attachment unless he is subscriber of list Y etc etc). The 
> only way to known if a message will be rejected or not is to run the 
> appropriate scenario script. We could develop a new entry point for 
> Sympa.pl in order to test a message without submitting it to the list 
> (cat xx.msg | sympa.pl --test_authorization). I don't think this could 
> be easy but we can do the same on the soap server interface. This way 
> anyone could provide milter or any other MTA plug in to test a message 
> against Sympa authorization scenario.
Some time ago I already made a suggestion about having a milter
communicate with sympa to check wheter or not to accept a message. I
still believe that such a milter would be quite easy to develop at a
"proof-of-concept"-level and I'm still going to implement such a milter.
However, the milter-interface for exim is still in development and has
been delayed for quite some time, so I still didn't even start.

By the way, the sieve-idea is broken. Usually you run sieve-scripts
after accepting the message, so you wouldn't solve your
autoresponder-problems. So you'd have to create a milter and run sieve
scripts in a way they are not ment to be run. So it would be easier to
skip the sieve-layer and have the MTA directly communicate with the
MLM-software. qed.
-- 
CU,
   Patrick.

Attachment: smime.p7s
Description: S/MIME cryptographic signature