<<< Date Index >>>     <<< Thread Index >>>

Re: mutt/2465: [PATCH] Use Delivered-to header in



The following reply was made to PR mutt/2465; it has been noted by GNATS.

From: Kyle Wheeler <kyle-mutt-dev@xxxxxxxxxxxxxx>
To: Mutt Developers <mutt-dev@xxxxxxxx>
Cc: bug-any@xxxxxxxxxxxxx
Subject: Re: mutt/2465: [PATCH] Use Delivered-to header in
        set_reverse_name()
Date: Thu, 7 Sep 2006 00:26:49 -0400

 --CEUtFxTsmBsHRLs3
 Content-Type: text/plain; charset=us-ascii; format=flowed
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Thursday, September  7 at 04:45 AM, quoth Derek Martin:
 > On Sun, Sep 03, 2006 at 09:30:45PM +0200, nate-mutt@xxxxxxxxxxx=20
 > wrote:
 > > This patch makes use of the Delivered-to: header when building the
 > > From: address in set_reverse_name().  This is needed so that
 > > alternate addresses can be found in emails sent from mailing lists
 > > where the alternate address isn't in the normal To: or Cc: headers.
 >=20
 > I'm not sure if this is a particularly useful approach...  I have
 > mails delivered by two different MTAs, and none of them carry a
 > "Delivered-To" header...
 
 On MTAs that do add the header, it is also often not the same as the=20
 address that is exposed to the outside world. For example, since=20
 memoryhole.net is a virtual domain on my server, my mails all have=20
 Delivered-To: memoryhole.net-kyle-mutt-dev@xxxxxxxxxxxxxx, even though=20
 that's definitely not my email address.
 
 ~Kyle
 --=20
 The whole art of government consists in the art of being honest.
                   -- Thomas Jefferson: Rights of British America, 1774
 
 --CEUtFxTsmBsHRLs3
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Comment: Thank you for using encryption!
 
 iD8DBQFE/5+JBkIOoMqOI14RAq6BAKD+/DBsnDIJc9GMf8NE4PDo/JHhfwCgqo1q
 jXNzIwFFwmfCqLEaEGY0TZg=
 =JZC2
 -----END PGP SIGNATURE-----
 
 --CEUtFxTsmBsHRLs3--