On Thu, Nov 20, 2014 at 9:32 AM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
>
>>
>> Without selinux, permission errors are usually pretty straightforward
>> - that is, if something logs a 'permission denied', it means exactly
>> that. I could be anywhere up the path, or the program accessing it
>> might not have the uid you expect, though.
>>
> It was permissions. I had added clam to the amavis group:
>
> gpasswd -a clam amavis
>
> But not given the group permissions to the directory. First did:
>
> chmod g+rx /var/spool/amavisd/tmp
>
> But was still getting the error so I went up a level:
>
> chmod g+rx /var/spool/amavisd
>
> and no longer getting the error.
>
> I **AM** making good notes on all of this. Perhaps I will someday put them
> up in Centos docs...
It would be even nicer if the packages that are likely to need to
access each other's files/sockets in the course of mail delivery had
a common group and appropriate permissions. I haven't set up a mail
server for a while, but used to have the same issues with
sendmail/mimedefang/clamav.
--
Les Mikesell
lesmikesell@xxxxxxxxx
.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
