[opensuse] spamd and mail loops
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd?
How/where do you call spamc (to talk to spamd) and what do you do with the scanned email afterwards? /Per -- Per Jessen, Zürich (18.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, October 28, 2013 11:01:58 AM Per Jessen wrote:
Roger Oberholtzer wrote:
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd?
How/where do you call spamc (to talk to spamd) and what do you do with the scanned email afterwards?
Originally, I called spamc from my procmail config. I thought I may set up spam filtering at a system level so each user did not need to do this.
/Per
-- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Monday, October 28, 2013 11:01:58 AM Per Jessen wrote:
Roger Oberholtzer wrote:
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd?
How/where do you call spamc (to talk to spamd) and what do you do with the scanned email afterwards?
Originally, I called spamc from my procmail config. I thought I may set up spam filtering at a system level so each user did not need to do this.
I wrote this about ten years ago, it might still be useful: http://www.jessen.ch/articles/spamassassin-and-postfix/ -- Per Jessen, Zürich (22.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, October 28, 2013 02:34:31 PM Per Jessen wrote:
Roger Oberholtzer wrote:
On Monday, October 28, 2013 11:01:58 AM Per Jessen wrote:
Roger Oberholtzer wrote:
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd?
How/where do you call spamc (to talk to spamd) and what do you do with the scanned email afterwards?
Originally, I called spamc from my procmail config. I thought I may set up spam filtering at a system level so each user did not need to do this.
I wrote this about ten years ago, it might still be useful:
The reason I enabled spamd was that the calls to spamc in my procmail rc file were generating these log messages: 2013-10-28T14:28:34.279776+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused 2013-10-28T14:28:35.279945+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused 2013-10-28T14:28:36.280034+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused 2013-10-28T14:28:37.280187+01:00 acme spamc[1219]: connection attempt to spamd aborted after 3 retries So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2013-10-28 at 16:13 +0100, Roger Oberholtzer wrote:
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
We need looking at your procmailrc file. At a minimum, the entire recipe used from spamc. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJugUsACgkQtTMYHG2NR9WEFwCfd3VXS4rhp8NLo1KR9HVtBkjb GQ4An3sMXWbj6FC9r/McAvFdxSyTtJII =RrrF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, October 28, 2013 04:22:51 PM Carlos E. R. wrote:
On Monday, 2013-10-28 at 16:13 +0100, Roger Oberholtzer wrote:
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
We need looking at your procmailrc file. At a minimum, the entire recipe used from spamc.
Same one I have used for years. First it sorts mail from things I recognize. There are many rules like this: :0 * ^From:.*@delta\.dk ".Suppliers.Delta/" All messages from other sources are then checked for spam. # Check for SPAM # pipe files smaller than 256k through stand alone spamassassin :0fw * < 256000 | spamc If they seem to be spam, put them in a SPAM folder: # Spam :0: * ^X-Spam-Status: Yes ".SPAM/" All else is in my inbox # Accept all the rest to default mailbox :0 "./" -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Monday, October 28, 2013 02:34:31 PM Per Jessen wrote:
Roger Oberholtzer wrote:
On Monday, October 28, 2013 11:01:58 AM Per Jessen wrote:
Roger Oberholtzer wrote:
On openSUSE 12.3 I run postfix for local mail delivery, If I enable spamd (systemctl enable/start spamd), mail stops getting delivered. postfix complains that there are too many hops. So there is some sort of a loop when spamd is running. If I disable spamd all is okay again. Have I missed having to configure something with spamd?
How/where do you call spamc (to talk to spamd) and what do you do with the scanned email afterwards?
Originally, I called spamc from my procmail config. I thought I may set up spam filtering at a system level so each user did not need to do this.
I wrote this about ten years ago, it might still be useful:
The reason I enabled spamd was that the calls to spamc in my procmail rc file were generating these log messages:
How was your spamd started before you enabled it?
2013-10-28T14:28:34.279776+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused 2013-10-28T14:28:35.279945+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused 2013-10-28T14:28:36.280034+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused 2013-10-28T14:28:37.280187+01:00 acme spamc[1219]: connection attempt to spamd aborted after 3 retries
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
Roger, we simply don't have enough information to even begin to suggest where to look. -- Per Jessen, Zürich (15.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, October 28, 2013 09:15:29 PM Per Jessen wrote:
How was your spamd started before you enabled it?
A call to spamc in via a rule in my procmail rules.
2013-10-28T14:28:34.279776+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused 2013-10-28T14:28:35.279945+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused 2013-10-28T14:28:36.280034+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused 2013-10-28T14:28:37.280187+01:00 acme spamc[1219]: connection attempt to spamd aborted after 3 retries
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
Roger, we simply don't have enough information to even begin to suggest where to look.
Same thing here. I don't know where to look either :) -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Monday, October 28, 2013 09:15:29 PM Per Jessen wrote:
How was your spamd started before you enabled it?
A call to spamc in via a rule in my procmail rules.
No, that's my point - spamc talks to spamd, it doesn't _start_ it.
2013-10-28T14:28:34.279776+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused 2013-10-28T14:28:35.279945+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused 2013-10-28T14:28:36.280034+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused 2013-10-28T14:28:37.280187+01:00 acme spamc[1219]: connection attempt to spamd aborted after 3 retries
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
Roger, we simply don't have enough information to even begin to suggest where to look.
Same thing here. I don't know where to look either :)
Well, to start with, as you have been using spamc, it is reasonable to assume that spamd was running. Therefore no need to enable it. However, as spamc expects to find it running on 127.0.0.1, and it isn't, that must be your first stop - spamd was running before, why isn't it running now? -- Per Jessen, Zürich (10.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, October 29, 2013 08:39:42 AM Per Jessen wrote:
Roger Oberholtzer wrote:
On Monday, October 28, 2013 09:15:29 PM Per Jessen wrote:
How was your spamd started before you enabled it?
A call to spamc in via a rule in my procmail rules.
No, that's my point - spamc talks to spamd, it doesn't _start_ it.
2013-10-28T14:28:34.279776+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused 2013-10-28T14:28:35.279945+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused 2013-10-28T14:28:36.280034+01:00 acme spamc[1219]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused 2013-10-28T14:28:37.280187+01:00 acme spamc[1219]: connection attempt to spamd aborted after 3 retries
So I thought I should enable spamd. But that caused the complaint about max hops being too many and the message being dropped. Which seems to imply a loop somewhere.
Roger, we simply don't have enough information to even begin to suggest where to look.
Same thing here. I don't know where to look either :)
Well, to start with, as you have been using spamc, it is reasonable to assume that spamd was running. Therefore no need to enable it. However, as spamc expects to find it running on 127.0.0.1, and it isn't, that must be your first stop - spamd was running before, why isn't it running now?
I updated this system from 11.2 to 12.3. I am guessing that, initially, I missed having spamd run in the new 12.3 install. I did not move any databases from the old spamd to the new system. I figured I would let it get built new. So I was not surprised when some spam was not marked so. As a bit of time went by, I felt something was not learning. It was then that I realized that spamd was not running. So I enabled it (sysctl enable/start spamd). When I did this, mail was no longer delivered. Returned messages complained that the max hops was exceeded. When I disabled spamd the error went away. That is when I posted this question. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
Well, to start with, as you have been using spamc, it is reasonable to assume that spamd was running. Therefore no need to enable it. However, as spamc expects to find it running on 127.0.0.1, and it isn't, that must be your first stop - spamd was running before, why isn't it running now?
I updated this system from 11.2 to 12.3.
Ah, okay.
I am guessing that, initially, I missed having spamd run in the new 12.3 install. I did not move any databases from the old spamd to the new system. I figured I would let it get built new. So I was not surprised when some spam was not marked so. As a bit of time went by, I felt something was not learning. It was then that I realized that spamd was not running.
Which is when you found spamc complaining about not being able to connect.
So I enabled it (sysctl enable/start spamd). When I did this, mail was no longer delivered. Returned messages complained that the max hops was exceeded. When I disabled spamd the error went away. That is when I posted this question.
Check one of the messages with too many hops - which hops are they? Check /var/log/mail to find out what's going on. -- Per Jessen, Zürich (12.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, October 29, 2013 11:49:07 AM Per Jessen wrote:
Roger Oberholtzer wrote:
Well, to start with, as you have been using spamc, it is reasonable to assume that spamd was running. Therefore no need to enable it. However, as spamc expects to find it running on 127.0.0.1, and it isn't, that must be your first stop - spamd was running before, why isn't it running now?
I updated this system from 11.2 to 12.3.
Ah, okay.
I am guessing that, initially, I missed having spamd run in the new 12.3 install. I did not move any databases from the old spamd to the new system. I figured I would let it get built new. So I was not surprised when some spam was not marked so. As a bit of time went by, I felt something was not learning. It was then that I realized that spamd was not running.
Which is when you found spamc complaining about not being able to connect.
So I enabled it (sysctl enable/start spamd). When I did this, mail was no longer delivered. Returned messages complained that the max hops was exceeded. When I disabled spamd the error went away. That is when I posted this question.
Check one of the messages with too many hops - which hops are they? Check /var/log/mail to find out what's going on.
/var/log/mail unfortunately says very little. When things are working, there
is something like this:
postfix/smtpd[21472]: connect from internal.opq.se[10.209.160.46]
postfix/smtpd[21472]: 7C869202A6A: client=internal.opq.se[10.209.160.46]
postfix/cleanup[21476]: 7C869202A6A: message-
id=
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-10-29 at 12:10 +0100, Roger Oberholtzer wrote:
What is curious is that when spamd is running, postfix says that the message is accepted for delivery. But the max hops issue seems to result in it not getting delivered. However, when spamd is not running, the delivery command is listed as procmail.
Ah! Maybe postfix has another rule to send to spamc on its own. As you upgraded, check the entire /etc/postfix/ directory for files with rpmnew or old in the name, and also main.cf and master.cf for references to spamd. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJvrbsACgkQtTMYHG2NR9UTmQCghsVTiogL4xRXNm4idsDaZ2Ft P6QAn3T+8uHfoNS69OGfDy8/dEs1BQdg =sUvY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, October 29, 2013 01:44:43 PM Carlos E. R. wrote:
On Tuesday, 2013-10-29 at 12:10 +0100, Roger Oberholtzer wrote:
What is curious is that when spamd is running, postfix says that the message is accepted for delivery. But the max hops issue seems to result in it not getting delivered. However, when spamd is not running, the delivery command is listed as procmail.
Ah!
Maybe postfix has another rule to send to spamc on its own.
As you upgraded, check the entire /etc/postfix/ directory for files with rpmnew or old in the name, and also main.cf and master.cf for references to spamd.
No such files. And no references to spam at all in any of the files. grep -ri spam /etc/postfix/ returns nothing. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
when they are not, it is like this:
postfix/smtpd[24048]: connect from internal.opq.se[10.209.160.46] postfix/smtpd[24048]: 866D9201E4C: client=internal.opq.se[10.209.160.46] postfix/cleanup[24052]: 866D9201E4C: message-id=<526DF633.8010300@att.net> postfix/qmgr[3017]: 866D9201E4C: from=
, size=7834, nrcpt=1 (queue active) postfix/smtpd[24048]: disconnect from internal.opq.se[10.209.160.46] postfix/smtp[24053]: 866D9201E4C: to= , relay=stockholm.opq.se[10.209.160.46]:25, delay=2.2, delays=0.12/0/2/0.04, dsn=2.0.0, status=sent (250 2.0.0 r9S5TlIc019160 Message accepted for delivery) postfix/qmgr[3017]: 866D9201E4C: removed
An email comes in from 10.209.160.46 and is then promptly sent back to 10.209.160.46. Sounds like a loop. -- Per Jessen, Zürich (13.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, October 29, 2013 02:40:57 PM Per Jessen wrote:
Roger Oberholtzer wrote:
when they are not, it is like this: postfix/smtpd[24048]: connect from internal.opq.se[10.209.160.46] postfix/smtpd[24048]: 866D9201E4C: client=internal.opq.se[10.209.160.46] postfix/cleanup[24052]: 866D9201E4C: message-id=<526DF633.8010300@att.net> postfix/qmgr[3017]: 866D9201E4C: from=
roger=opq.se@opensuse.org>, size=7834, nrcpt=1 (queue active)
postfix/smtpd[24048]: disconnect from internal.opq.se[10.209.160.46] postfix/smtp[24053]: 866D9201E4C: to=
, relay=stockholm.opq.se[10.209.160.46]:25, delay=2.2, delays=0.12/0/2/0.04, dsn=2.0.0, status=sent (250 2.0.0 r9S5TlIc019160 Message accepted for delivery)
postfix/qmgr[3017]: 866D9201E4C: removed
An email comes in from 10.209.160.46 and is then promptly sent back to 10.209.160.46. Sounds like a loop.
Could that be the bounce message that tells that the message was not delivered because of too many hops? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Tuesday, October 29, 2013 02:40:57 PM Per Jessen wrote:
Roger Oberholtzer wrote:
when they are not, it is like this: postfix/smtpd[24048]: connect from internal.opq.se[10.209.160.46] postfix/smtpd[24048]: 866D9201E4C: client=internal.opq.se[10.209.160.46] postfix/cleanup[24052]: 866D9201E4C: message-id=<526DF633.8010300@att.net> postfix/qmgr[3017]: 866D9201E4C: from=
roger=opq.se@opensuse.org>, size=7834, nrcpt=1 (queue active)
postfix/smtpd[24048]: disconnect from internal.opq.se[10.209.160.46] postfix/smtp[24053]: 866D9201E4C: to=
, relay=stockholm.opq.se[10.209.160.46]:25, delay=2.2, delays=0.12/0/2/0.04, dsn=2.0.0, status=sent (250 2.0.0 r9S5TlIc019160 Message accepted for delivery)
postfix/qmgr[3017]: 866D9201E4C: removed
An email comes in from 10.209.160.46 and is then promptly sent back to 10.209.160.46. Sounds like a loop.
Could that be the bounce message that tells that the message was not delivered because of too many hops?
No, that would be an NDR - non-delivery report - which is generated as a separate email. Besides, the recipient is clearly roger@acme.pacific, which is not the sender of the email. -- Per Jessen, Zürich (13.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, October 29, 2013 02:56:38 PM Per Jessen wrote:
Roger Oberholtzer wrote:
Could that be the bounce message that tells that the message was not delivered because of too many hops?
No, that would be an NDR - non-delivery report - which is generated as a separate email. Besides, the recipient is clearly roger@acme.pacific, which is not the sender of the email.
No idea. But it seems that the behavior is triggered by enabling spamd. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-10-29 at 14:53 +0100, Roger Oberholtzer wrote:
An email comes in from 10.209.160.46 and is then promptly sent back to 10.209.160.46. Sounds like a loop.
Could that be the bounce message that tells that the message was not delivered because of too many hops?
You can enable debug logging in /etc/postfix/main.cf debug_peer_level = 2 #debug_peer_level = 3 #debug_peer_list = mail.sourceforge.net - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJvyQ8ACgkQtTMYHG2NR9VeOgCfQRTG44Hjo0MbUtJpgQLEKu7x HuYAn3T3jiTnLIA3cjBVdoFXCH47++Ud =f2/w -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2013-10-28 at 11:07 +0100, Roger Oberholtzer wrote:
Originally, I called spamc from my procmail config. I thought I may set up spam filtering at a system level so each user did not need to do this.
Typically, people use "amavis-new" in that role. It includes spamassassin, antivirus, and some rules. It does not use spamd/spamc. However, I disable the spamassassin part of amavis, using instead spamd/spamc per user, because that way the Bayesian filter has a different database per user. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJublQACgkQtTMYHG2NR9UIvACdGaxcfMJmOq+3ABoso63CYZIQ ARAAn3vEoJw1hHaxteaEAyprvFI/1TqT =NdGy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2013 7:01 AM, Carlos E. R. wrote:
However, I disable the spamassassin part of amavis, using instead spamd/spamc per user, because that way the Bayesian filter has a different database per user.
Yes this is an important thing which amavis simply doesn't handle well. Using a common Bays database works if every on the mail server is engaged in the same business, (a group of programmers for instance) but not when there are diverse interests or people engaged in different fields of expertise. The reverse side of that coin is that spamd/spamc running per-user can impost a pretty high load at times. We found that a mail server set up to only handle a bunch of programmers engaged int the same type of work could be more easily handled with amavis, and because that server really didn't handle any unrelated mail it was actually more efficient than per-user processes. Of course, on your own laptop, amavis works just fine. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R.
-
John Andersen
-
Per Jessen
-
Roger Oberholtzer