[Mageia-sysadm] Various stuff to clean on alamut

[Michael Scherer]

Le lundi 28 mars 2011 à 19:09 +0200, Michael Scherer a écrit :
> Hi,

> - it seems that cron is unable to backup ldap on valstar. I didn't
> look at it fully, but feel free to do so.

I looked, seen no error message. So we will have to wait until it appear
again next time ( as i erased the mails due to my cleaning fury ).

> - there is also a obscure issue with sympa, it seems to loop somewhere.
> I do not have much idea, so I am on it since a few days. maybe we
> wrongly installed it :/

Ok so this error is solved. In short, our sympa setup was broken because
of subtle stuff and previous errors. See the various commits of the
night for details.

So the loop was caused because sympa-request was not correctly set on
postfix, and the mail just said "cannot sync some list". The syncing
error was due to sympa parser not removing trailling space in the
configuration ( in this case, in the password configuration ), thus
making sympa unable to connect ( 30 minutes of debugging to understand
that ).

While on it, I also enabled aliases as asked in rfc2142 ie  postmaster@,
hostmaster@, etc. I redirected all technical one to the system group
email, except those related to web, that goes to the web team group
email. 

For this, I used the whole group email stuff that I spoke before.

Basically, toto at group.mageia will be expanded to the list of all people
of the mga-toto ldap group

And also, I finally fixed remaining sympa issues related to council and
board mls ( but I have no doubt that sympa will strike again ). 

To add someone to the ml, just add them in ldap in the proper group
( mga-board , mga-council ). Sympa sync from ldap every hour and can be
forced with the command ( replace $LISTE with the proper list name ) :

perl  /usr/sbin/sympa.pl --sync_include=$LISTE at ml.mageia.org


-- 
Michael Scherer