[Mimedefang] Question about bounces - How do I do this?

[Troy Carpenter]

Ok,

I finally found something that works.

In filter_end, I added:

    if ($Sender eq "<>" ) {
        resend_message(@Recipients);
        action_discard()
    }

This works, but the only problem (but not really a problem, but probably
a bug) is that the Return-Path header reads "<-odd at carpenter.cx>" and
the maillog shows that the message was resent like it was from
"<-odd at carpenter.cx>".  However, I verified that the bounce does indeed
goes back to the originator, and the originator's MTA shows the bounce
came from the mailer-daemon of the bouncing system.

Here's the header from the bounce message as it appears on the
originator's system (notice the Return-Path and X-Authentication-Warning
headers):

Return-Path: <-odd at carpenter.cx>
Received: from imf04bis.bellsouth.net ([205.152.58.44])
          by mailmtx.acnet.net (Post.Office MTA v3.5.3 release 223
          ID# 0-52476U50000L50000S0V35) with ESMTP id net
          for <someuser at tiagris.com>; Mon, 21 Oct 2002 22:45:26 -0500
Received: from sol.carpenter.cx ([66.156.35.15]) by
imf04bis.bellsouth.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with
ESMTP
          id
<20021022034948.OLHY14545.imf04bis.bellsouth.net at sol.carpenter.cx>
          for <someuser at tiagris.com>; Mon, 21 Oct 2002 23:49:48 -0400
Received: from sol.carpenter.cx (sol.carpenter.cx [192.168.1.10] (may be
forged))
	by sol.carpenter.cx (8.12.6/8.12.6) with ESMTP id g9M3m4Se011521
	for <someuser at carpenter.cx>; Mon, 21 Oct 2002 23:48:04 -0400
Received: (from MIMEDefang at localhost)
	by sol.carpenter.cx (8.12.6/8.12.6/Submit) id g9M3m4Pn011519
	for <someuser at carpenter.cx>; Mon, 21 Oct 2002 23:48:04 -0400
X-Authentication-Warning: sol.carpenter.cx: MIMEDefang set sender to
-odd using -f
Received: from mail by m1.dnsix.com with local (Exim 3.34 #1)
	id 183q1R-0005L6-00
	for someuser at carpenter.cx; Mon, 21 Oct 2002 20:48:01 -0700
X-Failed-Recipients: baduser at awesomenet.net
From: Mail Delivery System <Mailer-Daemon at m1.dnsix.com>
To: someuser at carpenter.cx
Subject: Mail delivery failed: returning message to sender
Message-Id: <E183q1R-0005L6-00 at m1.dnsix.com>
Date: Mon, 21 Oct 2002 20:48:01 -0700
X-Spam-Flag: No
X-Spam-Score: -0.6 () MAILER_DAEMON,SPAM_PHRASE_03_05,X_AUTH_WARNING
X-Virus-Flag: No
X-Scanned-By: MIMEDefang 2.23 (www . roaringpenguin . com / mimedefang)


> -----Original Message-----
> From: Troy Carpenter
> Sent: Monday, October 21, 2002 1:19 PM
> To: 'mimedefang at lists.roaringpenguin.com'
> Subject: Re: [Mimedefang] Question about bounces - How do I do this?
> 
> 
> See inline comments:
> 
> >Date: Mon, 21 Oct 2002 11:22:58 -0400 (EDT)
> >From: "David F. Skoll" <dfs at roaringpenguin.com>
> >To: mimedefang at lists.roaringpenguin.com
> >Subject: Re: [Mimedefang] Question about bounces - How do I do this?
> >Reply-To: mimedefang at lists.roaringpenguin.com
> >
> >On Mon, 21 Oct 2002, Troy Carpenter wrote:
> >
> > Now, I can relay email through my ISP's mail server all day long, as

> > long as there is a from address.  However, my ISP will not accept 
> > messages from "<>" if the destination address is NOT local
> to my ISP,
> >
> >Your ISP is behaving badly!
> 
> I though so too, but then again they do accept bounces
> destined for users on their system...it's just when it is 
> bound for another system and "just passing through" that 
> there is a problem.  I will eventually take this up with them 
> again when I have time to fight that battle.
> 
> >As a workaround, put this in your Sendmail's .mc file:
> >
> >	define(`SMTP_MAILER_FLAGS', `g')
> >	define(`confMAILER_NAME', `MAILER-DAEMON at yourdomain.com')
> >
> >It will make bounce messages appear to come from
> >MAILER-DAEMON at yourdomain.com instead of ><>
> 
> I tried this, but it did not fix my problem.  Does this cause
> sendmail to rewrite bounce messages that it receives from 
> other mailservers?
> 
> Here's the complex path taken to get this problem:
> 
> 1. User1 sends email through MailserverA to User2 at mailserverB
> using a return email address of user1 at mailserverD 2. 
> Forwarding MailserverB accepts message and forwards to 
> user2 at mailserverC. 3. User2 does not exist on MailserverC, so 
> MailserverB bounces message to user1 at mailserverD. 4. 
> MailserverD attempts to forward bounce to user1 at mailserverA 
> via MailserverE (which is D's smarthost, user1 is listed in 
> virtualusertable). 5. Because the envelope sender address is 
> "<>", MailserverE rejects the relay. 6. Bounce message then 
> goes to postmaster at mailserverD for final burial.
> 
> Clear as mud?
> 
> I have also used MIMEDefang to modify the "Return-Path" and
> "Sender" headers, but to no avail.
> 
> Right now I am quarantining these messages, and can provide
> the message plus the SMTP logs where I have them.  However, 
> due to third party privacy issues, I would need to take some 
> time to modify the information.
> 
> Troy Carpenter
> troy at carpenter.cx
>