[exim] Changing Return-path with specific sender domain caus…

Pàgina inicial
Delete this message
Reply to this message
Autor: Lee Mason
Data:  
A: exim-users
Assumpte: [exim] Changing Return-path with specific sender domain causes remote mail servers to reject message
"
We are running Exim 4.50.

We need to be able to send e-mails with various different return addresses for example:

The Xyz Company <support@???>
or
Support Systems Ltd <info@???>

I have changed the return-path in the header of all outgoing e-mails by using:

return_path = $ reply_address

This
seemed to work fine. However some remote mail servers (by no means all)
and rejecting the the e-mails sent to the with a 501 error.

It appears that Exim could be constructing the return_path as follows:

<The Xyz Company <support@???>>

Adding
an extra set of < > around the complete address. This can be see
in the log file as P=<The Xyz Company <support@???>>.

I have a couple of questions about this:

1.
Is this expected behaviour and is the syntax of the return_path created
therefore legal (i.e. are the remote SMTP servers rejecting this
unnecessarily)?
2. How can this be changed to strip the excess <
> before sending? Can this be done with a rewrite rule or by some

other method?

Thanks in advance,

LeeFrom prvs=exim-users-20070913/087027b99e@??? Sun Dec 16 11:31:50 2007
Envelope-to: exim-users@???
Received: from mail.rudolf.org.uk ([91.84.196.3]:51919)
    by tahini.csx.cam.ac.uk with esmtp (Exim 4.69)
    (envelope-from <prvs=exim-users-20070913/087027b99e@???>)
    id 1J3ric-000692-Lu
    for exim-users@???; Sun, 16 Dec 2007 11:31:50 +0000
Received: from davide by mail.rudolf.org.uk with local
    id 1J3ric-0002In-EP-73d6e48d55c189aac5ef795251a556c17374ec2d
    for exim-users@???; Sun, 16 Dec 2007 11:31:38 +0000
Date: Sun, 16 Dec 2007 11:31:38 +0000
From: Dave Evans <exim-users-20070913@???>
To: exim-users@???
Message-ID: <20071216113138.GA8751@???>
Mail-Followup-To: exim-users@???
References: <18346958.1771197799251204.JavaMail.root@???>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
    protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI"
Content-Disposition: inline
In-Reply-To: <18346958.1771197799251204.JavaMail.root@???>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
X-Spam-Score: 0.9 (/) 
X-Spam-Status: No, score=0.9 required=5.0 tests=AWL=-0.095, BAYES_00=-1.5,
    FROM_ENDS_IN_NUMS=2.53 autolearn=no version=3.1.8
Subject: Re: [exim] Changing Return-path with specific sender domain
    causes    remote mail servers to reject message
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.7
Precedence: list
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
    <mailto:exim-users-request@exim.org?subject=unsubscribe>
List-Archive: <http://lists.exim.org/lurker/list/exim-users.html>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject=help>
List-Subscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
    <mailto:exim-users-request@exim.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2007 11:31:50 -0000



--oyUTqETQ0mS9luUI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 16, 2007 at 10:00:51AM +0000, Lee Mason wrote:
> We need to be able to send e-mails with various different return addresse=

s for example:
>=20
> The Xyz Company <support@???>
> or
> Support Systems Ltd <info@???>
>=20
> I have changed the return-path in the header of all outgoing e-mails by u=

sing:
>=20
> return_path =3D $ reply_address


The return path is just the address part, so you probably want to use

return_path =3D ${address:$reply_address}

See
http://www.exim.org/exim-html-current/doc/html/spec_html/ch11.html#SECTexpop

--=20
Dave Evans
http://djce.org.uk/
http://djce.org.uk/pgpkey

--oyUTqETQ0mS9luUI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHZQyanYOJTU6nkkkRArvFAJ989wUWuEfD9XL1pqu4j4KphlZO6wCfSKp6
qye0MIQZsDWagyQ5Gt41Jfw=
=hs07
-----END PGP SIGNATURE-----

--oyUTqETQ0mS9luUI--