The mailing list for listmasters using Sympa

[Steve Rich <address@concealed>]

To add to this, I purged a closed list using the sympa.pl command and it took ~9 minutes.  That seems ridiculously long to me.  Maybe I have something misconfigured.

Thanks,

Steve

From: <address@concealed> on behalf of Steve Rich
Reply-To: Steve Rich
Date: Wednesday, August 19, 2015 at 1:18 PM
To: Steve Shipway, "address@concealed"
Subject: Re: [sympa-users] Postfix newaliases

Hi Steve,

Thanks for the advice.  It turned out to be that the sympa_newaliases-wrapper was somehow compiled to exec sympa_newaliases.pl at the wrong path.  I recompiled it to point to the correct path and it now works!  Really not sure how that even happened.

While I have your ear, I was wondering if you could provide some guidance on another issue I am having.  We are seeing timeouts on calls to SOAP, loading the list of lists for the main robot, and closing/purging lists from the web interface.  From what I can tell in the debug logs, it appears that the timeouts are occurring because these subroutines want to load the configs for all lists and then perform on-the-fly syncs for each list.  I’ve set the default_ttl and default_distribution_ttl values to 3600.  For what it’s worth, I have also configured cached_list_config to binary-file and db_list_cache is on.  Do you have any suggestions as to what may be causing these timeouts?  Everything else works just fine on the web interface.

 

Thanks,

Steve

From: Steve Shipway
Date: Tuesday, August 18, 2015 at 6:18 PM
To: Steve Rich, "address@concealed"
Subject: RE: Postfix newaliases

Might be a permissions issue.

 

Check the ownership and permissions on the sympa_aliases.db file.  Can you run ‘newaliases’ as root, but not as sympa?  I’m not sure about 6.2, but under 6.1 there was a sympa_newaliases-wrapper script that needed to have setuid set for it to run (to give permission to update the aliases databases).

 

Maybe move the sympa_aliases file under /etc/sympa, rather than /etc/postfix (have to change the postfix config file to point to the new location, and the sympa.conf as well).  This will allow the sympa user to compile the aliases into this directory (it is unlikely to have write permission to the postfix directory without the setuid wrapper).  We do it this way with Sympa 6.1.23

 

Steve

 

 

Steve Shipway

address@concealed

(GNU Terry Pratchett)

 

From:address@concealed [mailto:address@concealed] On Behalf Of Steve Rich
Sent: Wednesday, 19 August 2015 4:30 a.m.
To: address@concealed
Subject: [sympa-users] Postfix newaliases

 

I have Sympa 6.2.3 and postfix 2.10.1 installed in a RHEL 7 host and I’m having issues.  I have specified the following in the sympa config:

 

sendmail_aliases

/etc/postfix/sympa_aliases

aliases_program

postalias

 

aliases_db_type

Hash

 

We use ldap for aliasing our primary domain and so when a list is installed, we have a custom alias_manager script that creates an LDAP entry for the list and adds the list aliases to /etc/postfix/sympa_aliases.

 

For some reason, sympa is not rebuilding the database /etc/postfix/sympa_aliases.db when a new list is installed.  The logs don’t indicate that anything is wrong.  When I run the alias_manager.pl script manually like so,

 

alias_manager.pl add test example.com

 

I get "newaliases exited with status 255.”

 

The aliases are appended to /etc/postfix/sympa_aliases but the db is not rebuilt properly.  I would really appreciate some insight on this as it is creating quite a few problems for us.

 

Thanks,

Steve