Mail loop detected - in error, Mail loop detected - in error

[jiggy1com]

in my xmail q manager the SLOG states Mail loop detected

however i gone through all the options in the DIAGNOSTICS tab, and went over all of my changes but still i have RELAY DENIED coming from external servers and when sending through my own machine i have "Mail loop detected"

the only recent change to the server was an installation of a remote reboot card. i have added it's ip to the smtprelay.tab file, as well as other internal and external IPs. i have also made a DNS modification which i have since put back to the way it was, restarted services and the machine several times --- but the errors still occur.

i have been running xmail fine for over a year, close to 2 maybe until now.

any other suggestions???

please post here or email me at joevelez@ewingbeland.com

-=Joe

[hschneider]

I assume that this solved your prob: http://xmailforum.homelinux.net/index.php?showtopic=3493

[jiggy1com]

Well i thought that my issue was resolved completely.

I'm still having a few small issues. For the most part, mail is working, but there are still several messages (100's, some legit, some spam) stuck in the server.

My Queue Mgr states Loop Killed in the diagnosis column. However, some mail still is routed to the user (Pop or Forward) but some mail tends to get stuck.

Any ideas why? Could there a memory issue where Xmail tends to bomb out and force a Loop Killed statement? I even dropped the loop down from the default to 5.

Any suggestions?

Thanks - Joe

[bim]

You might want to check if the e-mails you're talking about have SLOG-files when examining them in XQM. If there isn't an SLOG-file, then the diagnoses might not be very accurate.
Mails that are "sending" will not have an SLOG-file.

I have noticed that, when spamd crashed on me, spamc would keep waiting for a response endlessly. XMailserver would (correctly) not wait and deliver the message after a time-out. But the message would still show up in the queue in "sending" status.

You might be able to find in the SMAIL-logs if the message was delivered or not. Every message in XMailserver has a unique ID which you will find inside the message when examining it with XQM and in the SMAIL-logs.

[jiggy1com]

------------------------------------------------------
SLOG DATA
------------------------------------------------------
[PeekTime] 1163613333 : Wed, 15 Nov 2006 11:55:33 -0600
<<
ErrCode = -173
ErrString = Mail loop detected
Message <S1A8D8> blocked by mail loop check !
SMTP-Error = "554 Message blocked by mail loop check"
>>
------------------------------------------------------
DIAGNOSIS DATA
------------------------------------------------------

LOOP_KILLED

XMail stopped this message from further looping.

Loops can be caused by one of these reasons:
- Entries in aliases.tab or MailRoot/cmdaliases pointing to each other.
- Entries in mailusers.tab with the same account ID.
- Filters that redirect mails in a loop.
- A third party mailer which produces malformed mailheaders. Hints for
this are missing e.g. subject lines.
- DNS misconfiguration.
- A not commented-out "DefaultSMTPGateways" entry in your server.tab.
------------------------------------------------------
SPOOL FILE DATA
------------------------------------------------------
[XX.XXX.XXX.XX]:4616;[192.168.10.208]:25;Wed, 15 Nov 2006 11:54:51 -0600
LOCAL_SERVER
S1A8D8
MAIL FROM:<EXTERNAL_SENDER> SIZE=2622345
RCPT TO:<LOCAL_RECEIVER>
<<MAIL-DATA>>
Received: from EXTERNAL_SERVER ([XX.XXX.XXX.XX]:4616)
by LOCAL_SERVER with [XMail 1.23 ESMTP Server]
id <S1A8D8> for <LOCAL_RECEIVER> from <EXTERNAL_SENDER>;
Wed, 15 Nov 2006 11:54:51 -0600
Received: from EXTERNAL_SERVER2 [SERVER IP] by EXTERNAL_SERVER with SMTP;
Wed, 15 Nov 2006 10:52:31 -0700
Received: from c-064-186-255-106.oc1.redwire.net [SENDING IP] by EXTERNAL_SERVER2 with SMTP;
Wed, 15 Nov 2006 10:48:12 -0700
From: "Joe Velez" <EXTERNAL_SENDER>
To: <LOCAL_RECEIVER>
Subject: FW: swatch update
Date: Wed, 15 Nov 2006 09:48:28 -0800
Message-ID: <LPECKEKFOBFJNBDPJACJEENMCAAA.EXTERNAL_SENDER>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_001E_01C7089B.339515B0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C7089B.339515B0
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_001F_01C7089B.339515B0"


------=_NextPart_001_001F_01C7089B.339515B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RE: swatch update
-----Original Message-----



----------------------------------------

Regardless if I DEFROST or FLUSH the messages no longer go out. But the base information is legit as far as I can tell. The TO email address exists, and is a POP account. So why would it think that there is a loop? Especially since I still receive email to that TO address.

It's just that some messages get through, and some say LOOP KILLED. Even though no such loop exists.

I'm kinda hoping this is a server memory issue, and I'm supposed to have upgrade from 512 to 2G this evening.

Any ideas, suggestions, recommendations?

- joe

[hschneider]

Check the hints above again carefully. Also keep in mind that naming your internal domain the same as an external domain which is hosted on another IP can confuse your DNS service.