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: Simon Taylor <address@concealed>
  • To: Thomas Berry <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] Message::new() Cannot open message file ... Permission
  • Date: Fri, 21 Nov 2008 11:04:47 +1100

Thomas Berry wrote:
Although, I don't really see how these two binaries factor in when the problem you are having and maybe there are difference between your version and the one we have, but aliaswrapper on our system is owned by root, and both aliaswrapper and virtualwrapper both have a sticky bit permission that is similar to bouncequeue, queue, and familyqueue

-rwsr-x--- 1 sympa sympa 6659 Jul 10 2007 virtualwrapper
-rwsr-x--- 1 root root 6609 Jul 10 2007 aliaswrapper

I've changed the ownership and permissions to match yours, and restarted sympa, but alas I still get the same problem.

(Though thanks for your thoughtful help, it was definitely worth a try).

I'm new enough to Sympa that I don't get the internals well enough, but when I use the web interface to send my test message to my "test1" list, I see that the web interface seems to send my test message to "sympa@......" :

... Processing /address@concealed ; sender: ...
... Processing web message for address@concealed
... Message for address@concealed sent

and debugging at this point reveals that the message file is owned by symsa and has permissions that look usable.

Then this apparently results in a new message being sent to "test1@...", and it is this new message file that has the
incorrect (?) permissions, (it's owned by root):

... Cannot open message file /address@concealed : Permission denied
... Unable to create Message object /address@concealed

Can anyone tell me which process creates this second message file?



Archive powered by MHonArc 2.6.19+.

Top of Page