Click to See Complete Forum and Search --> : SpamAssassin + Sendmail Problem


ddaas
09-29-2005, 09:41 AM
Hello,
I am running spamassassin-3.0.3-1.1 and spamass-milter-0.3.0-1.1 on RHEL3. The MTA is sendmail-8.12.
The rule is that every spam is forwarded to spams@mydomain.com.
Everything works great and I am pleased with the results.

The problem is that sometimes I get the same spam forwarded 8 times to spams@mydomain.com and root gets the following error:
The original message was received at Mon, 26 Sep 2005 18:26:52 +0200
from root@localhost

----- The following addresses had permanent fatal errors -----
spams
(reason: 554 5.4.6 Too many hops)
(expanded from: spams)

----- Transcript of session follows -----
554 5.4.6 Too many hops 27 (25 max): from root via localhost, to spams

Why is this happening? Why is that " Too many hops 27 (25 max)"?

I think that is because of return-path header which is set to root@mydomain.com. As I know this header is put by the final MTA.
Could this be the problem? Could I just strip off this header?

There could also be an alias loop. but I can't figure out how...

ddaas
10-05-2005, 07:19 AM
please, I would really need some help.
It seems a loop or something. I can't figure out...
Every spam mail gets the following header:

X-Envelope-From: <root@server.domain.de>
X-Envelope-To: <spams@server.domain.de>
Received: from server.domain.de (localhost.localdomain [127.0.0.1]) by server.domain.de;
Received: (from root@localhost) by server.domain.de (8.12.11/8.12.11/Submit) id j95An5Yt019008 for spams; Wed, 5 Oct 2005 12:49:05 +0200

At the end the spam collector account gets the same mail many times, every time with this header add on more time.

root gets a return mail:

The original message was received at Wed, 5 Oct 2005 12:49:07 +0200
from root@localhost

----- The following addresses had permanent fatal errors -----
spams
(reason: 550 5.7.1 Blocked by SpamAssassin)
(expanded from: spams)

----- Transcript of session follows -----
... while talking to [127.0.0.1]:

>>>>>> DATA

<<< 550 5.7.1 Blocked by SpamAssassin
554 5.0.0 Service unavailable



Reporting-MTA: dns; server.domain.de
Arrival-Date: Wed, 5 Oct 2005 12:49:07 +0200

Final-Recipient: RFC822; spams@server.domain.de
Action: failed
Status: 5.7.1
Remote-MTA: DNS; [127.0.0.1]
Diagnostic-Code: SMTP; 550 5.7.1 Blocked by SpamAssassin
Last-Attempt-Date: Wed, 5 Oct 2005 12:53:10 +0200

retsaw
10-05-2005, 08:52 AM
Just a thought, but might the spamassassin filter include checking mail for your spam account, thus sending it into a feedback loop.

ddaas
10-06-2005, 05:40 AM
It seemed it was something like this.
Thanks for your hint.