A little update.
Having dug a little deeper into this, it appears that the problem is not
the "From" header but the "Return-Path" which is getting set to the
machine name.
Here are the headers from one of the offending emails. The return-path
should be the same as the "From" header.
Return-Path: <me(_at_)sydsrv56(_dot_)mydomain(_dot_)tld>
Received: from sydsrv56.mydomain.tld (localhost.localdomain [127.0.0.1])
by mail.mydomain.tld (8.13.1/8.13.1) with ESMTP id oAG0JcOD032690
for <prosmart(_at_)mydomain(_dot_)tld>; Tue, 16 Nov 2010 11:19:38 +1100
Received: (from me(_at_)localhost)
by sydsrv56.mydomain.tld (8.13.1/8.13.1/Submit) id oAG0Jcmg032688;
Tue, 16 Nov 2010 11:19:38 +1100
Date: Tue, 16 Nov 2010 11:19:38 +1100
From: End User <me(_at_)mydomain(_dot_)tld>
Message-Id:
<201011160019(_dot_)oAG0Jcmg032688(_at_)sydsrv56(_dot_)mydomain(_dot_)tld>
To: support(_at_)mydomain(_dot_)tld
Subject: Re: Test - Please Ignore - Five
References: <4CE1CE15(_dot_)5050107(_at_)mydomain(_dot_)tld>
In-Reply-To: <4CE1CE15(_dot_)5050107(_at_)mydomain(_dot_)tld>
X-Loop: your(_at_)own(_dot_)mail(_dot_)address
Precedence: junk
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
(mail.mydomain.tld [127.0.0.1]); Tue, 16 Nov 2010 11:19:39 +1100 (EST)
X-Scanned-By: MIMEDefang 2.68 on 192.168.0.56
Does anyone have any idea how I can prevent this please?
TIA
Nigel.
On 11/11/2010 16:35, Nigel Allen wrote:
Hi All
Self-confessed procmail newbie.
I am using a simple procmail recipe to send an auto-reply when one of my
customers employees is away from the office.
Here it is:
:0 h c
* !^FROM_DAEMON
* !^X-Loop: your(_at_)own(_dot_)mail(_dot_)address
* ? /usr/bin/test -f $HOME/vacation_msg
| (formail -r -I"Precedence: junk" -A"X-Loop:
your(_at_)own(_dot_)mail(_dot_)address" ;
cat $HOME/vacation_msg) | $SENDMAIL -t
I'm getting bounces from servers that look like this:
*****************************************************
The original message was received at Thu, 11 Nov 2010 11:47:10 +1100
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<recipient(_at_)destination(_dot_)tld>
(reason: 550 5.1.0 <billc(_at_)server(_dot_)mydomain(_dot_)tld> sender
rejected -
sender domain has no MX/A record)
----- Transcript of session follows -----
... while talking to mx1.bne.server-mail.com.:
MAIL From:<<billc(_at_)server(_dot_)mydomain(_dot_)tld>> SIZE=1701
<<< 550 5.1.0 <<billc(_at_)server(_dot_)mydomain(_dot_)tld>> sender rejected
- sender
domain has no MX/A record
554 5.0.0 Service unavailable
******************************************************
I assume it's because we're not getting masquerading done for some
reason - my invocation of sendmail perhaps?
"Normal" email (Thunderbird / Sendmail) works perfectly.
Please note that I have (obviously) modified the actual domains for
anonymity.
Any pointers on where I can search for enlightenment please? I need to
ensure that any emails going out of here go from mydomain.tld and NOT
from server.mydomain.tld.
Thanks and Regards
Nigel.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail