A solution that worked for me (but isn't optimal) was to set the permissions back how they were and add the celeryd user to the postfix group.
Doing that made it all work correctly. I wonder if there was some mistake in the way that permissions were assigned? I can't understand what it was. Cheers, Christian On 13 August 2012 21:04, Christian De Kievit <[email protected]> wrote: > ls: cannot access > /var/spool/MailScanner/quarantine/20120813/4D47B5F799.A5112/message: > Permission denied > > If I run that with postfix as the user, it's fine. In desperation, I > changed all the directories from quarantine on to have celeryd as an owner, > but I still get permission denied. > > Cheers, > Christian > > On 13 August 2012 20:55, Andrew Colin Kissa <[email protected]> wrote: > >> >> On 13 Aug 2012, at 12:44 PM, Christian De Kievit wrote: >> >> > Fiddling around in message.py (under >> /usr/share/pyshared/baruwa/utils/mail/message.py) I can see that the path >> that baruwa is searching for is the correct path, and the os.path.exists >> call just returns false, which is very annoying. >> > >> > As you say, it could be an apparmor thing. >> >> Well you can check to see if the celeryd user can access the file. >> >> su - -s /bin/bash celeryd -c 'ls >> /var/spool/MailScanner/quarantine20120813/4D47B5F799.A5112/message' >> >> If its apparmor blocking access, it should log something when you run the >> above. >> >> - Andrew >> >> -- >> www.baruwa.org >> >> >> >> >> _______________________________________________ >> Keep Baruwa FREE - http://pledgie.com/campaigns/12056 >> > > > > -- > Christian De Kievit > -- Christian De Kievit
_______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
