IRM gets duplicate emails

[maverickzee]

I set up a second domain (an IRM) off of my existing domain. I configured the email and everything is working fine, except that I am getting duplicate emails to my IRM domain. For example, I get two of the same email sent to info@exampleIRM.com, but only one email sent to info@example.com. I do not have email forwarding on this email account.

I don't know if this is related or not, but I just started to get the error message below when I try to send an email to my IRM account. I replaced "exampleIRM.com" instead of my real domain.

----- The following addresses had permanent fatal errors -----
<info@exampleIRM.com>

----- Transcript of session follows -----
554 too many hops 20 (20)

This error message doesn't happen every time. Only when sending email to info@exampleIRM.com from one particular email account. My other email accounts send email just fine, but I receive two emails for one sent.

Anyone have any suggestions?

MaverickZee

[sheila]

It would really be necessary to have specifics about your account setup in order to diagnose something like this. The first thing we would want to see is the complete set of email headers from a pair of "duplicate" messages, so that we could compare them and see why you are getting two copies. Undoubtedly, the second copy is going through a different delivery process than the first.

Here is information about email headers, if you do not already know what they are:
http://service.futurequest.net/kb107

[maverickzee]

Okay, here is the host header from the first email. I edited the @ symbol to "at".

Return-Path: <username "at" example.org>
Delivered-To: info "at" example.net
Received: (fqmail 31112 invoked from network); 07 Nov 2005 01:39:56 -0000
Received: from mx07.futurequest.net (mx07.futurequest.net [69.5.6.178])
by pt02.futurequest.net ([69.5.6.173])
with FQDP via TCP; 07 Nov 2005 01:39:56 -0000
Received: (qmail 32513 invoked from network); 7 Nov 2005 01:39:56 -0000
Received: from example.com (mail.example.com [x.x.x.x])
by mx07.futurequest.net ([69.5.6.178])
with ESMTP via TCP; 07 Nov 2005 01:39:56 -0000
Received: from someserver by example.com
(MDaemon.PRO.v8.0.3.R)
with ESMTP id md50000693511.msg
for <info "at" example.net>; Sun, 06 Nov 2005 17:57:55 -0800
From: "Joe User" <username "at" example.org>
To: "'RemovedByRequest'" <info "at" example.net>
Subject: testing 5:40pm
Date: Sun, 6 Nov 2005 17:41:32 -0800
Message-ID: <000001c5e33c$62084820$6802a8c0@example.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0001_01C5E2F9.53E50820"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcXjPGGReRWetXYHRDWWHA2EIoTdsA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
X-Authenticated-Sender: username "at" example.org
X-Spam-Processed: example.com, Sun, 06 Nov 2005 17:57:55 -0800
(not processed: message from valid local sender)
X-MDRemoteIP: 66.88.156.211
X-Return-Path: username "at" example.org
X-MDaemon-Deliver-To: info "at" example.net
X-MDAV-Processed: example.com, Sun, 06 Nov 2005 17:57:57 -0800

Here is the host header from the duplicate email:

Return-Path: <username "at" example.org>
Delivered-To: info "at" example.net
Received: (fqmail 31112 invoked from network); 07 Nov 2005 01:39:56 -0000
Received: from mx07.futurequest.net (mx07.futurequest.net [69.5.6.178])
by pt02.futurequest.net ([69.5.6.173])
with FQDP via TCP; 07 Nov 2005 01:39:56 -0000
Received: (qmail 32513 invoked from network); 7 Nov 2005 01:39:56 -0000
Received: from example.com (mail.example.com [x.x.x.x])
by mx07.futurequest.net ([69.5.6.178])
with ESMTP via TCP; 07 Nov 2005 01:39:56 -0000
Received: from someserver by example.com
(MDaemon.PRO.v8.0.3.R)
with ESMTP id md50000693511.msg
for <info "at" example.net>; Sun, 06 Nov 2005 17:57:55 -0800
From: "Joe User" <username "at" example.org>
To: "'RemovedByRequest'" <info "at" example.net>
Subject: testing 5:40pm
Date: Sun, 6 Nov 2005 17:41:32 -0800
Message-ID: <000001c5e33c$62084820$6802a8c0@example.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0001_01C5E2F9.53E50820"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcXjPGGReRWetXYHRDWWHA2EIoTdsA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
X-Authenticated-Sender: username "at" example.org
X-Spam-Processed: example.com, Sun, 06 Nov 2005 17:57:55 -0800
(not processed: message from valid local sender)
X-MDRemoteIP: 66.88.156.211
X-Return-Path: username "at" example.org
X-MDaemon-Deliver-To: info "at" example.net
X-MDAV-Processed: example.com, Sun, 06 Nov 2005 17:57:57 -0800

I put these messages side by side and they are the identical.

Here is the host header on the email that comes back from too many hops. The @ symbol is replaced with "at" .

Received: from mail.outflow.net
by mail.outflow.net (Mail Server v.1.3.2) with SMTP id AEH38536
for <RemovedByRequest "at" example.com>; Sun, 6 Nov 2005 17:47:40 -0800
Date: Sun, 6 Nov 2005 17:47:40 -0800
From: Mail Delivery Subsystem <MAILER-DAEMON@outflow.net>
To: <RemovedByRequest "at" example.com>
Message-Id: <862359028@mail.outflow.net>
Subject: Returned mail: too many hops
Content-Type: multipart/report; report-type=delivery-status; boundary="862359028200511061747404FF7@mail.outflow.net"

I hope this helps.

Russ

[sheila]

The email headers you posted are in fact identical. They are the exact same headers twice for a single email message.

Our mail system received only a single email at 8:39 pm from the sender address you showed. Here are the email logs for the single entry on the receiving MX server (I have replaced the @ symbol similar to what you did):

2005-11-06 20:39:46.015702500 tcpserver: pid 32512 from x.x.x.x
2005-11-06 20:39:46.017816500 tcpserver: ok 32512 mx07.futurequest.net:69.5.6.178:25 mail.example.com:x.x.x.x::2392
2005-11-06 20:39:46.725050500 smtpfront-qmail[32512]: MAIL From:<username "at" example.org> SIZE=2916
2005-11-06 20:39:46.794577500 smtpfront-qmail[32512]: RCPT To:<info "at" example.net>
2005-11-06 20:39:46.965255500 smtpfront-qmail[32512]: Accepted message qp 32513 bytes 2976a
2005-11-06 20:39:47.038534500 smtpfront-qmail[32512]: bytes in: 3045 bytes out: 258
2005-11-06 20:39:47.038865500 tcpserver: end 32512 status 0

Only a single email delivery was delivered by our POP mail server to the "info" mailbox on your account. I searched the POP Toaster mail logs and this is the only matching result for a scan during the 8:00-8:59 PM hour from the domain example.org

2005-11-06 20:39:46.975105500 tcpserver: pid 31112 from 69.5.6.178
2005-11-06 20:39:46.975851500 tcpserver: ok 31112 pt02.futurequest.net:69.5.6.173:1021 mx07.futurequest.net:69.5.6.178::51783
2005-11-06 20:39:46.995066500 fqdpfront-fqmail[31112]: from <username "at" example.org> to <info "at" example.net> bytes 3283 accepted
2005-11-06 20:39:46.995251500 fqdpfront-fqmail[31112]: fqdeliver: Delivered to account 'info'
2005-11-06 20:39:46.995339500 fqdpfront-fqmail[31112]: bytes in: 3114 bytes out: 42
2005-11-06 20:39:46.995401500 tcpserver: end 31112 status 0

This means that the duplication is occuring AFTER the email has been received in your email box.

Possibilities include...
Some email filter in your mail program is creating the duplicate?
Or, maybe...you are retrieving the message multiple times? I notice that there are currently 10 "read" emails in your "info" mailbox on that account. If you are leaving the messages on the server instead of downloading them, perhaps your mail client is downloading it again later when you check for email again later?

In short, it appears that our mail system is delivering only a single copy to the "info" mailbox. I don't know what else we can tell you except to check how your mail retrieval process or configurations in your email client may be creating duplicates.