Re: spamass.sock - No such file or directory

2021-06-27 Thread Dave Funk
Make sure to start spamasmilter before postfix. The milter creates the socket which must exist for postfix to be able to open it. Start the milter then use "lsof" to make sure that it has created the socket and that it's in the place which postfix expects to find it. Also make sure that the

Re: SPF plugin ignores existing Authentication-Results

2021-06-27 Thread David Bürgin
Matus UHLAR - fantomas: Matus UHLAR - fantomas: this is more an issue of how milter itself operates. the milter is supposed to see e-mail as it was received from (smtp) client - even without Received: headers, just with other milters' modifications. If SpamAssassin (SA from now) has to see Aut

Re: spamass.sock - No such file or directory

2021-06-27 Thread Dominic Raferd
Try unix:/run/spamass/spamass.sock On Sun, 27 Jun 2021, 18:28 , wrote: > Still the same > > Jun 27 19:21:03 nmail postfix/smtps/smtpd[4946]: warning: connect to Milter > service unix:spamass/spamass.sock: No such file or directory > Jun 27 19:25:37 nmail postfix/smtps/smtpd[5552]: warning: c

AW: spamass.sock - No such file or directory

2021-06-27 Thread mauric
Still the same Jun 27 19:21:03 nmail postfix/smtps/smtpd[4946]: warning: connect to Milter service unix:spamass/spamass.sock: No such file or directory Jun 27 19:25:37 nmail postfix/smtps/smtpd[5552]: warning: connect to Milter service unix:run/spamass/spamass.sock: No such file or directory

Re: SPF plugin ignores existing Authentication-Results

2021-06-27 Thread Matus UHLAR - fantomas
Matus UHLAR - fantomas: this is more an issue of how milter itself operates. the milter is supposed to see e-mail as it was received from (smtp) client - even without Received: headers, just with other milters' modifications. If SpamAssassin (SA from now) has to see Authentication-Results: head