also sprach Sven Verdoolaege <skimo@xxxxxxxxxx> [2007.08.17.1131 +0200]: > PS, please don't prune (me from) the CC list when replying. I am not used to lists where the policy is to CC posters, but seeing posts like http://marc.info/?l=git&m=113882569532399&w=2 and given my newcomer/not-(yet-)important-contributor status, I am happy to comply (and apologise for not doing so earlier). To help others in similar positions do the right thing I am sharing my relevant mutt configuration: # do not set M-F-T on mails to the git mailing list send-hook . 'set followup_to' send-hook '~C git@vger\.kernel\.org' 'unset followup_to' This takes care of not sending M-F-T in outgoing mail. The remaining issue is how to ensure that those (and only those) people end up on Cc who want to be there. I have come up with two ways: using mutt hooks and adding M-F-T to incoming mail: # do a <group-reply> for L when sending to the git mailing list # http://marc.info/?l=mutt-users&m=118734866910357&w=2 message-hook . 'bind pager L list-reply' message-hook '~C git@vger\.kernel\.org' 'bind pager L group-reply' macro index L '<display-message>L' This is a bit ugly, but it works. However, since it interferes with some other hooks and other parts of my configuration, I had to find another way: the theory is that my procmail *adds* the Mail-Followup-To header to incoming git list mails that don't have it yet, and puts all From/To/Cc addresses on there. This will cause my local mutt to behave exactly like it should when I press L, but since the send-hook has disabled followup_to, my reply will *not* contain/propagate the Mail-Followup-To header. :0 * ! ^Mail-Followup-To: * ^TO_git@vger\.kernel\.org$ { CORRESPONDENTS=`formail -cxTo: -xCc: -xFrom: | tr -s '\n' ,` :0 fw |$FORMAIL -A "Mail-Followup-To: $CORRESPONDENTS" } In addition, I advice to unset metoo in mutt's configuration to avoid CCing yourself on outgoing mail. Now all I need is to filter duplicate messages with procmail in such a way that the list mail makes it through and the personal CC (which usually arrives first) is dropped: :0 * ^X-Original-To: madduck@madduck\.net$ * ^TO_git@vger\.kernel\.org$ /dev/null Make sure this happens *before* you weed out duplicate mail with formail. Comments welcome, but off-list, please (Reply-To set). If important stuff turns up, I'll collect and append a summary to this thread in a bit. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck "for nasa, space is still a high priority." - george w. bush spamtraps: madduck.bogus@xxxxxxxxxxx
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
