Zenaan Harkness wrote: > Brian wrote: > > Fortunately, Mutt users have the opportunity to take advantage of its > > ability to construct a custom Message-ID: header for a mail sent to > > debian-user. Like so: > > > > send-hook . 'unmy_hdr Message-ID:' > > send-hook 'debian-user@lists\.debian\.org' 'my_hdr Message-ID:<`date > > +"%Y%m%d%H%M%S"`NoCcsPlease@example.com>' > > > > A mail with NoCcsPlease in its In-Reply-To or References headers can > > only have had the mailing list mail as its source. However, the CC will > > not contain a List-ID: header. This makes it possible to distinguish > > between a list mail and a CC. Procmail recipes based on these two > > conditions can now file list mail with certainty and, if desired, delete > > CCs. > > Cool :) > > Thanks for sharing. Appreciated. +1. I also think that is pretty cool. Since Message-Id is one of the few that would be passed through. However many clients do not do this. I have many problem friends who reply with bad MTAs that break threads. Pretty cool just the same though. > Would it be possible to also pipe outgoing mail through procmail or > similar, on its way to the MTA/SMTP server? Mutt has the $sendmail variable. The manual has a section "Change Settings Based Upon Message Recipients" that gives this teaser. send2-hook is executed after send-hook, and can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender address. Which implies to me (although I have not tried it) that you could pipe messages for particular addresses through whatever filter you wanted and could automatically add headers or track outbound messages. As long as you consistently used mutt to do the sending. Bob
Attachment:
signature.asc
Description: Digital signature