The mailing list for listmasters using Sympa

[Olivier Salaün - CRU <address@concealed>]

Marco Gaiarin wrote:

MG> In the meantime: there's really a way to 'wrap around' something the
MG> mhonarc call?

Ok, i've run thru all the sympa parameters, hoping not missing too many.
The only external binary called are mhonarc and sendmail, both are configurable. But sendmail probably get the full formatted message as
input, so after that i need to 'grep' into header to find the listname, or at least discriminate from real list mail from 'robot' moderation,
bounce, ... stuff. Too hard.

The parameter 'mhonarc':

	http://www.sympa.org/wiki/manual/web-interface#mhonarc
  

We've just written some more documentation regarding web archives in Sympa, see http://www.sympa.org/wiki/manual/web-archives#web_archives

seems perfect: can i have an hint on how they are called? I need to read the source?
  

You can read the archived.pl script to have details, but here is a brief explanation on how mhonarc is called :

• when adding a message : mhonarc -add -modifybodyaddresses -addressmodifycode \'$ENV{'M2H_ADDRESSMODIFYCODE'}\'  -rcfile $mhonarc_ressources -outdir $monthdir  -definevars \"listname='$listname' hostname=$hostname yyyy=$yyyy mois=$mm yyyymm=$yyyy-$mm wdir=$wwsconf->{'arc_path'} base=$Conf{'wwsympa_url'}/arc tag=$tag\" -umask $Conf{'umask'} < $queue/$file
  
• when removing a message : mhonarc -outdir $wwsconf->{'arc_path'}/$adrlist/$yyyy-$mm -rmm $msgid
• when rebuilding an archive : mhonarc -modifybodyaddresses -addressmodifycode \'$ENV{'M2H_ADDRESSMODIFYCODE'}\' -rcfile $mhonarc_ressources -outdir $wwsconf->{'arc_path'}/$adrlist/$yyyy-$mm  -definevars \"listname='$listname' hostname=$hostname yyyy=$yyyy mois=$mm yyyymm=$yyyy-$mm wdir=$wwsconf->{'arc_path'} base=$Conf{'wwsympa_url'}/arc tag=$tag\" -umask $Conf{'umask'} $wwsconf->{'arc_path'}/$adrlist/$arc/arctxt

Of course all $Conf['xx'} are sympa configuration parameters.

If you can make your own script compatible with this API, it should work fine.

MG> Speaking clearly: there's a way to setup a scenario or something like this in wich the news gateway 'do something' (S/MIME?) so that sympa accept the message ('trust it')?

Reading:

	http://www.sympa.org/wiki/manual/authentication#authentication

(second paragraph) seems that the only way to approve a generic message (eg, caming from a news server) are to sign S/MIME it.

Looking at:

	http://www.sympa.org/wiki/manual/authorization-scenarios#authorization_scenarios

confused a bit me. Seems that i can use simple From: authentication, but i've to manually subscribe (as nomail! ;) all news people, or use
S/MIME but in this way *all* user have to use S/MIME, even subscribed ones.

Can be setup a scenario like 'use From: auth for subscribers, try S/MIME for others and last reject'?
  

S/MIME is an option but it is probably not leightweight for you to implement it on the News gateway.
A simpler option (but less secure) would be for Sympa to trust one SMTP header field, set by the news gateway.
Example :

1. your news gateway adds a "X-Trust-Me: True" header field.
2. The Sympa mailling list has a "send private_or_news" configuration option
3. The send.private_or_news authorization scenario that looks like this :

is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
equal([header->X-Trust-Me],/True/) smtp,smime,md5 -> do_it

This way you don't even need to subscribe a mail gateway address to the list.
You'd probably need to configure the list so that the X-Trust-Me header field is removed before distribution, see http://www.sympa.org/wiki/manual/conf-parameters/part2#remove_headers


PS : If you need to go on this thread, please shift it to the sympa-dev mailing list, which is more appropriate.

Thanks.