Orphaned or bogus bounce messages

Forum for getting help with Project Gamera, Spamassassin, Clamav, qmail-scanner and other anti-spam tools.
singeX
Forum User
Forum User
Posts: 28
Joined: Sat Jul 21, 2007 7:31 pm

Orphaned or bogus bounce messages

Unread post by singeX »

I received a failure notice for a bounce but the email should not have been sent to the bad email address in the first place because it's my logwatch email. I received the regular logwatch email a minute before the failure notice. The same thing happened at the same time with 2 other nightly log emails.

I know this is kind of messy but the path that the email usually follows is:
root (local user)
webmaster@mydomain.com (alias)
myname@mydomain.com (redirect)

I checked the logs and found the regular email and everything looks normal in the logs. I searched 3 days of logs for the email address canarylady7@earthlink.net and couldn't find it anywhere. I'm guessing it didn't really try to send the logwatch email to canarylady7@earthlink.net but that it has to do something with a duplicate message id from an orphaned bounce or something. Any thoughts or suggestions are greatly appreciated. I posted this on the qmailrocks forum and nobody responded. Maybe I'm explaining it wrong.

Here's the failure notice:

Code: Select all

X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	mydomain.com
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,UNPARSEABLE_RELAY
	autolearn=ham version=3.2.5
Received: (qmail 15471 invoked by uid 10043); 16 Oct 2009 04:45:50 -0700
Received: from  by mydomain.com (envelope-from <>, uid 110) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.175738 secs); 16 Oct 2009 11:45:50 -0000
Delivered-To: 104-webmaster@mydomain.com
Received: (qmail 15418 invoked by uid 10043); 16 Oct 2009 04:45:34 -0700
Received: from  by mydomain.com (envelope-from <>, uid 110) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.175588 secs); 16 Oct 2009 11:45:33 -0000
Delivered-To: 1-root@mydomain.com
Received: (qmail 15401 invoked by uid 10043); 16 Oct 2009 04:45:32 -0700
Received: from  by mydomain.com (envelope-from <>, uid 2522) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.178651 secs); 16 Oct 2009 11:45:31 -0000
Date: 16 Oct 2009 04:45:31 -0700
From: MAILER-DAEMON@mydomain.com
To: root@mydomain.com
Subject: failure notice
Message-ID: <1255693531102515392@mydomain.com>

Hi. This is the qmail-send program at mydomain.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<canarylady7@earthlink.net>:
209.86.93.226 does not like recipient.
Remote host said: 550 canarylady7@earthlink.net...User account is unavailable
Giving up on 209.86.93.226.

--- Below this line is a copy of the message.

Return-Path: <root@mydomain.com>
Received: (qmail 15282 invoked by uid 10043); 16 Oct 2009 04:45:01 -0700
Received: from  by mydomain.com (envelope-from <root@mydomain.com>, uid 110) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.097608 secs); 16 Oct 2009 11:45:01 -0000
Delivered-To: 104-webmaster@mydomain.com
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	mydomain.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
	UNPARSEABLE_RELAY autolearn=ham version=3.2.5
Received: (qmail 15195 invoked by uid 10043); 16 Oct 2009 04:44:38 -0700
Received: from  by mydomain.com (envelope-from <root@mydomain.com>, uid 110) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.099137 secs); 16 Oct 2009 11:44:37 -0000
Delivered-To: 1-root@mydomain.com
Received: (qmail 15167 invoked by uid 10043); 16 Oct 2009 04:44:35 -0700
Received: from  by mydomain.com (envelope-from <root@mydomain.com>, uid 0) with qmail-scanner-2.06st 
 (clamdscan: 0.95.2/9899. spamassassin: 3.2.5. perlscan: 2.06st.  
 Clear:RC:1(127.0.0.1):. 
 Processed in 0.095275 secs); 16 Oct 2009 11:44:35 -0000
Date: 16 Oct 2009 04:44:23 -0700
Message-ID: <20091016114423.14847.qmail@mydomain.com>
To: root@mydomain.com
From: logwatch@mydomain.com
Subject: Logwatch for mydomain.com (Linux)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"


 ################### Logwatch 7.3 (03/24/06) ####################

etc...
singeX
Forum User
Forum User
Posts: 28
Joined: Sat Jul 21, 2007 7:31 pm

Re: Orphaned or bogus bounce messages (Update)

Unread post by singeX »

- Update -
I also just tonight received a bounce for an email that I sent a minute earlier however the bounce has the wrong email address. I sent an email to a verified working yahoo email address and this is the bounce I received:

Code: Select all

Hi. This is the qmail-send program at mydomain.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<ldrumonde@interhop.net>:
209.85.222.41 does not like recipient.
Remote host said: 550-5.1.1 The email account that you tried to reach does not exist. Please try
550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at                             
550 5.1.1 http://mail.google.com/support/bin/answer.py?answer=6596 7si8354622pzk.132
Giving up on 209.85.222.41.
I've been receiving other failure notices that suggest this is happening to other users on the server as well which has me a bit worried. So far I haven't received any complaints about it which is surprising. The problem is that it is seemingly random and unable to recreate at this point. Plus the bad email addresses in the failure notices are nowhere in the logs. My qmail logs only go back 3 days though.

By-the-way, I wasn't sure which forum to put this in. I thought maybe this issue has something to do with qmail-scanner. But feel free to move it if it doesn't belong in this forum.
Post Reply