Thanks for that. I wasn't sure which config to add it to.
I now have the following in /etc/default/spamass-milter...
OPTIONS="-u spamass-milter -i 127.0.0.1 -- -s 800"
... which works.
On 28.11.19 16:40, Linkcheck wrote:
Belated thans again to all who helped me with this problem. It has
been running reasonably well since my last posting. I now have only a
couple of minor problems left, one of which (I think) more suited to
the postfix forum.
The other one is max-size. I had
Belated thans again to all who helped me with this problem. It has been
running reasonably well since my last posting. I now have only a couple
of minor problems left, one of which (I think) more suited to the
postfix forum.
The other one is max-size. I had gradually uprated this to 800 in
On 24/11/2019 18:23, Bill Cole wrote:
setting "smtpd_delay_open_until_valid_rcpt = no" should make it available
Just tried that in main.cf, but no difference. No queue ID until after
the connect line, just before the SPF tests. I wonder if the confMILTER
error mitigates against it.
It also
On 24 Nov 2019, at 11:23, Bill Cole
wrote:
> setting "smtpd_delay_open_until_valid_rcpt = no" should make it available. By
> default, postfix does not commit a file descriptor and queue ID to a message
> until it has an accepted recipient. Setting that option to "no" causes it to
> open the fi
Thank you for the explanation. Appreciated. :)
On 24 Nov 2019, at 12:34, Matus UHLAR - fantomas wrote:
On 24/11/2019 15:57, Matus UHLAR - fantomas wrote:
I have explained that this was caused by receiving mail for "admin"
thus
spamass-milter provider username admin. Since the admin doesn't
exist
locally (apparently alias or remote user), s
On 24/11/2019 15:57, Matus UHLAR - fantomas wrote:
I have explained that this was caused by receiving mail for "admin" thus
spamass-milter provider username admin. Since the admin doesn't exist
locally (apparently alias or remote user), spamd falled back to nobody.
On 24.11.19 16:05, Linkcheck
On 24/11/2019 15:57, Matus UHLAR - fantomas wrote:
I have explained that this was caused by receiving mail for "admin" thus
spamass-milter provider username admin. Since the admin doesn't exist
locally (apparently alias or remote user), spamd falled back to nobody.
Then how can I get it to use
On 24/11/2019 14:47, Matus UHLAR - fantomas wrote:
then you have your problem fixed.
On 24.11.19 15:21, Linkcheck wrote:
More or less. It works (although not sure what will happen on reboot -
will it auto-run spamass-milter and spamd?) but I am trying to clean
up the remaining log entries.
On 24.11.19 15:35, Linkcheck wrote:
Almost there now. I found a reference online that said to add "-u
spamd" to the end of the OPTIONS line in /etc/defauls/spamassassin and
that removed the log entry...
this is the worst solution. It disables per-user config files.
spamd: still running as ro
Almost there now. I found a reference online that said to add "-u spamd"
to the end of the OPTIONS line in /etc/defauls/spamassassin and that
removed the log entry...
spamd: still running as root: user not specified with -u, not found,
or set to root, falling back to nobody
The posting als
On 24/11/2019 14:47, Matus UHLAR - fantomas wrote:
> then you have your problem fixed.
More or less. It works (although not sure what will happen on reboot -
will it auto-run spamass-milter and spamd?) but I am trying to clean up
the remaining log entries.
comment any messages when you have
On 24/11/2019 14:00, Matus UHLAR - fantomas wrote:
relative to the chroot value.
On 24.11.19 14:22, Linkcheck wrote:
I repeat, no chroot involved! Otherwise, the two values are the same...
if you don't use chroot, then it's "/".
main.cf
unix:/var/run/spamass/spamass.sock
etc/default/spam
On 24/11/2019 14:00, Matus UHLAR - fantomas wrote:
relative to the chroot value.
I repeat, no chroot involved! Otherwise, the two values are the same...
main.cf
unix:/var/run/spamass/spamass.sock
etc/default/spamass-milter
/var/run/spamass/spamass.sock
> set values of SOCKETOWNER and SOC
On 24.11.19 12:33, Linkcheck wrote:
As I understand it, altering those values in default/spamass-milter
should be sufficient? Those have been changed for several days now.
the SOCKET value in default/spamass-milter MUST agree with value in
smtpd_milters in main.cf relative to the chroot value.
As I understand it, altering those values in default/spamass-milter
should be sufficient? Those have been changed for several days now.
Following a lead from elsewhere I have altered the owner to
spamass-milter:postfix and the socket permissions follow it in the file
manager. However, the PID
On 18/11/2019 10:46, Edda wrote:
You did not start/restart spamass-milter?
I found no mention of such a thing, although I did look and concluded
there was no such thing. This has been my problem all along: lots of
Howto Install but always missing vital bits. :(
Searching now, I found how to
On 17.11.19 18:38, Linkcheck wrote:
Thank you for your responses. Sorry it's taken a while to reply.
no problem.
Bearing in mind your comments - and those of the other contributors -
I now have the following setup / observations but I still can't get it
to work.
/etc/default/spamassassin
Am 10.11.19 um 16:55 schrieb Linkcheck:
I've tried altering things but the best I can get is the message:
"warning: connect to Milter service
unix:/var/run/spamass/spamass.sock: No such file or directory"
This is the socket the spamass-milter daemon has to create for postfix
to communicate
Linkcheck skrev den 2019-11-17 23:49:
Thanks for the response.
I looked into replacing unix:/var/run/spamass/spamass.sock with
inet:localhost:783 in main.cf (which I'm pretty sure is wrong!)
and it logged errors and refused mail.
glibc have ipv6 prefered over ipv4, so if spamd only listen on i
Thanks for the response.
>> I looked into replacing unix:/var/run/spamass/spamass.sock with
>> inet:localhost:783 in main.cf (which I'm pretty sure is wrong!)
>> and it logged errors and refused mail.
> glibc have ipv6 prefered over ipv4, so if spamd only listen on ipv4 ?
> change localhost with
Linkcheck skrev den 2019-11-17 19:38:
I looked into replacing unix:/var/run/spamass/spamass.sock with
inet:localhost:783 in main.cf (which I'm pretty sure is wrong!) and it
logged errors and refused mail.
glibc have ipv6 prefered over ipv4, so if spamd only listen on ipv4 ?
change localhost w
Thank you for your responses. Sorry it's taken a while to reply.
Bearing in mind your comments - and those of the other contributors - I
now have the following setup / observations but I still can't get it to
work.
/etc/default/spamassassin
ENABLED=1
OPTIONS="--create-prefs --maxchildren
On 13.11.19 12:01, Linkcheck wrote:
I was rather hoping someone could supply a basic setup that would
allow spamass-milter to run with postfix, which is why I originally
posted so much information.
On 13.11.19 14:12, Matus UHLAR - fantomas wrote:
You mention having Mint (Ubuntu 16). Ubuntu
On 11/11/2019 19:23, Benny Pedersen wrote:
i am confused from your first post where you show spamPd and spamD
config files
On 13.11.19 12:01, Linkcheck wrote:
I posted all I could find relating to spamassassin. I missed chroot,
which never occurred to me might be relevant since I've never appl
On 11/11/2019 19:23, Benny Pedersen wrote:
i am confused from your first post where you show spamPd and spamD
config files
I posted all I could find relating to spamassassin. I missed chroot,
which never occurred to me might be relevant since I've never applied it.
spamPd is a smtp proxy th
> "with postfix, you may need to set up milter wocket within its chroot"
Ok, but since I do NOT use chroot which should I set up, bearing in mind
the other milters all run successfully?
My original posting gives my setup AS FAR AS I CAN DISCOVER IT.
Presumably something in it is incorrect or
On 11/11/2019 19:15, Reindl Harald wrote:
because it's common sense
Sorry, but that is NOT an explanation.
when postfix is configured to a unix socket which is a path it needs to
live within the chroot postfix is using
I am not using chroot
then why did you respond at all to something talki
with postfix, you need to set up milter wocket within its chroot.
on debian/ubuntu consult /etc/default/spamass-milter
On 11.11.19 16:40, Linkcheck wrote:
Elsewhere I've read the opposite. It does not sound reasonable anyway:
clam, opendkim etc work without chroot.
maybe the postfix smtpd is
Linkcheck skrev den 2019-11-11 20:11:
On 10/11/2019 20:15, Benny Pedersen wrote:
then use milter in postfix to inet:[127.0.0.1]:spamass-milter-port
How do I find the spamass port? Is it the spamd DESTPORT? I assume I
then have to add the LISTENPORT into master.cf?
i am confused from your fir
On 10/11/2019 20:15, Benny Pedersen wrote:
then use milter in postfix to inet:[127.0.0.1]:spamass-milter-port
How do I find the spamass port? Is it the spamd DESTPORT? I assume I
then have to add the LISTENPORT into master.cf?
> with postfix, you need to set up milter wocket within its chroot.
> on debian/ubuntu consult /etc/default/spamass-milter
Elsewhere I've read the opposite. It does not sound reasonable anyway:
clam, opendkim etc work without chroot.
--
Dave Stiles
Linkcheck skrev den 2019-11-07 16:25:
/etc/default/spamass-milter
OPTIONS="-u spamass-milter -i 127.0.0.1"
then use milter in postfix to inet:[127.0.0.1]:spamass-milter-port
On 10.11.19 15:55, Linkcheck wrote:
I've tried altering things but the best I can get is the message:
"warning: connect to Milter service
unix:/var/run/spamass/spamass.sock: No such file or directory"
The folder exists with the permissions postfix:postfix 0660. I have
also tried spamass-milt
I've tried altering things but the best I can get is the message:
"warning: connect to Milter service
unix:/var/run/spamass/spamass.sock: No such file or directory"
The folder exists with the permissions postfix:postfix 0660. I have also
tried spamass-milter:postfix.
On restarting spamassa
On 07.11.19 15:25, Linkcheck wrote:
I have run spamassassin as a postfix content filter (master.cf) for
several years on Linux Mint (Ubuntu 16.04) but I now need to run
spamass-milter instead. I have spent several hours trying to find the
correct setup but those I've found are somewhat conflict
I have run spamassassin as a postfix content filter (master.cf) for
several years on Linux Mint (Ubuntu 16.04) but I now need to run
spamass-milter instead. I have spent several hours trying to find the
correct setup but those I've found are somewhat conflicting and I cannot
determine which fil
38 matches
Mail list logo