Re: TMDA/fetchmail

On 2007-01-04, Stephen Warren wrote:
> Not all Received: lines actually include information about the address
> that the message is "to". As such, even though (3) is probably correct,
> one needs to limit the search to avoid going back far enough to the
> point at which the mailing list host received the message addressed to
> the list. How to implement that is probably undefined. A simple
> implementation might look at solely the very first Received: header, but
> I could conceive a site with internal mail routing where you might need
> to look back N hops, where N is as far back as the site-level
> Internet-visible MX system.

  The perl code I put on the wiki takes the longest address that matches
  USERNAME(\+[^@]+)?@HOSTNAME, looking first at to, then cc, then through 
Received.  I'm looking for the longest match so that a tagged address will be 
preferred over one that is not tagged.  So in a message that is To: me, and 
 Cc: me+dated+address, it'll take the dated one.

> >   So... can someone who is running TMDA on a mail server look at their 
> > incoming log for this message and let me know if TMDA thought the recipient 
> > was tmda-users, or if it was the address that you subscribed with?
>
> See the headers below.

  Thank you, but I was more interested in the contents of a 
~/.tmda/log/incoming.   Here's a stanza from mine while I was testing BCC'ing 
a dated address.

Date: Thu, 04 Jan 2007 02:57:42 -0600
From: "Corey Halpin" <[email protected]>
  To: [email protected]
Subj: how about a BCC?
Actn: OK good_dated_cookie (Tue, 09 Jan 2007 02:50:55 -0600)            (2771)

  In the stanza for a mailing list message, what shows up in "To"?
  Is it the mailing list address?
  Or is it something that matches USERNAME(\+[^@]+)?@HOSTNAME ?

crh

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD4DBQFFnYxWWBjzOA9cliERAlhAAJYotWfjRZrxnRYP9UR7DmSRQpUXAJsEytC5
wpsRabeVtIH6Tk3ctzGLdA==
=u7RN
-----END PGP SIGNATURE-----