On 12/11/2013 20:36, Simon Loewenthal wrote:
> On 12/11/2013 20:29, Wietse Venema wrote:
>> Simon Loewenthal:
>>> On 12/11/2013 19:30, Wietse Venema wrote:
>>>> Simon Loewenthal:
>>>>> Please! You are mixing up different email threads.
>>>>>
>>>>> The error message is and running without chroot.
>>>>>
>>>>> Nov 12 13:37:08 lt postfix/smtpd[30776]: warning: connect to Milter
>>>>> service unix:/var/spool/postfix/spamass/spamass.sock: No such file or
>>>>> directory
>>>> Does /var/spool/postfix/spamass/spamass.sock exist?
>>>>
>>>> Why do you believe that Postfix chroot is turned off?
>>>>
>>>> Wietse
>>> Because:
>>> # ls -ld /var/spool/postfix/spamass/spamass.sock
>>> srw-rw---- 1 postfix postfix 0 Nov 11 15:08
>>> /var/spool/postfix/spamass/spamass.sock
>> Turn off selinux.
>>
>> Turn off apparmor.
>>
>> Or tell them that it is OK for Postfix to access the socket in this
>> location.
>>
>> Wietse
> Hi, I am not using SELinux nor apparmor that I am aware of.
>
> # dpkg -l apparmor
> No packages found matching apparmor.
> # dpkg -l selinux-basics selinux-policy-default
> No packages found matching selinux-basics.
> No packages found matching selinux-policy-default.
>
> And just in case for auditd:
> # auditctl -l
> No rules
>
Problem solved :
"try a relative pathname:
smtpd_milters = unix:spamass/spamass.sock
chroot or not chroot, it's always relative to the current directory
( postconf ${queue_directory} in most cases )"
,
smtpd_milters = unix:/spamass/spamass.sock
to this
smtpd_milters = unix:spamass/spamass.sock
And now this works :D
