The mailing list for listmasters using Sympa

["McLaren, Terrence M" <address@concealed>]

Is anyone else having problems with bin/queue in v6.1.23?  The queue binary definitely spitting out a default error message:  “SYMPA internal error : unable to open /etc/sympa.conf”.  It appears v6.1.23 queue will not accept any input and throws the error. 

 

sympa> ~/bin

>queue

queue: usage error, one one list-name argument expected.

 

sympa> ~/bin

>queue ?

SYMPA internal error : unable to open /etc/sympa.conf

 

I was able to fix the email interface by swapping /bin/queue  from 6.1.23 version with our previous version (v6.1.15) .   Now the email interface is processing email commands as expected.

 

-Terry McLaren

 

PS> I didn’t see an open bug at https://sourcesup.renater.fr/projects/sympa/.   

 

 

From: address@concealed [mailto:address@concealed] On Behalf Of McLaren, Terrence M
Sent: Monday, October 06, 2014 5:04 PM
To: address@concealed
Subject: [sympa-users] 6.1.23 upgrade, email commands not working

 

Folks - I upgraded to 6.1.23 and have been testing the system.  The web interfaces works as designed but I’m running into an error with the email interface.  I’m looking for your input on a couple of issues:

 

1)     The mail daemon reply’s to the sender of an “unsubscribe listName” email with an error stating the server can’t’ find /etc/sympa.conf.  There is only one sympa.conf on the system in /home/sympa/etc/  and it seems to be working since I can boot the list service and the web interface is working.   The error is:

--------

The mail system

<address@concealed>: Command died with status 255: "
    /home/sympa/bin/queue address@concealed ".
    Command output: SYMPA internal error : unable to open /etc/sympa.conf

Final-Recipient: rfc822; address@concealed
Original-Recipient: rfc822; address@concealed
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; SYMPA internal error : unable to open /etc/sympa.conf

            ---------

2)      A second issue may be the cause of the 1^st, and is related to the default file permissions in the /bin directory.  We run sympa in a sand box and I noticed the permissions were changed after the upgrade.  I had to chmod 755 all files in the /bin to the meet the security requirement of the sandbox and I may have stepped on required default permissions.   I’m also wondering if certain files need to have sticky bit set?  I did tried to change the queue executable to ‘chmod u+s queue’, restarted the server but it gave the same error.

 

Any thoughts or ideas would be appreciated.

 

-Terry McLaren