Skip to Content.
Sympa Menu

en - Re: [sympa-users] Message::new() Cannot open message file ... Permission

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Cefiar <address@concealed>
  • To: Simon Taylor <address@concealed>
  • Cc: Thomas Berry <address@concealed>, address@concealed
  • Subject: Re: [sympa-users] Message::new() Cannot open message file ... Permission
  • Date: Fri, 21 Nov 2008 14:10:46 +1100

Simon Taylor wrote:
Hello again Thomas,

I've done some digging and found that wwsympa.fcgi (sympa's web interface) uses the Sympa module to construct the message using methods mail_file and sending to construct and place the message in the "send spool" That spool looks like its the "queue" directory which is sympa/spool/msg in my configuration. From there, the running process is what monitors the "queue" directory for messages waiting to be distributed. should move the message to the "distribute" queue where it then adds the recipients and prepares the message for the outbound mailer (postfix, sendmail, etc.).

That's very clear. Thanks for digging in to this.

So, it sounds like the Sympa web interface isn't running as sympa. The apache process hosting Sympa should be running as user sympa.

Going back to the process list, check for sympa-httpd:

My site is setup differently.

I'm running one apache for the site, at is configured to run as user 'apache' group 'apache'

[root@anzaas bin]# ps -ef|grep http
root 26310 1 0 Nov20 ? 00:00:00 /usr/sbin/httpd
apache 29154 26310 0 04:23 ? 00:00:00 /usr/sbin/httpd
apache 29155 26310 0 04:26 ? 00:00:00 /usr/sbin/httpd

Note that I seem to remember you might be able to get around this by adding the apache user into the sympa group, and the sympa user into the apache group, but that was a long time ago. Whether this is a good thing security wise is another matter.

Stuart Young - aka Cefiar - address@concealed

Archive powered by MHonArc 2.6.19+.

Top of Page