Re: Not FCC-ing mail addressed to subscribed mailing lists
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, November 22 at 12:41 PM, quoth Michael Williams:
> I currently have the following rules in my .muttrc, which are
> designed to prevent saving copies of outgoing mail (FCCs) to
> subscribed mailing mailing lists.
>
> fcc-hook ~u /dev/null
> fcc-hook . =Sent
Not bad... a little wasteful, though (not that this is incredibly
important). Your fcc-hook there are out of order (I'm assuming you
just put them backwards in the email?); what you have there, since all
matching hooks are executed in order, should make it so that ALL mails
get saved to =Sent.
This fixes that problem:
fcc-hook . =Sent
fcc-hook ~u /dev/null
Personally, though, I'm picky enough that I don't want mutt to go to
the trouble of actually *writing* the FCC, even if it's just writing
it to /dev/null; so I use this:
send-hook . 'set record="=Sent"'
send-hook ~u|~p 'set record='
> This seems to be working, but is this the canonical way of
> preventing multiple copies of emails from me to subscribed mailing
> lists ending up in my archives? Is there a more robust way of doing
> this in mutt, or (wondering off-topic), should I really be doing
> this in, e.g. procmail?
Nope, you're on the right track. Doing things the procmail route is...
well, wasteful, and probably too complicated. The only drawback to
this way of doing things in mutt is that if you post a message to a
mailing list that is temporarily down, you can't see what exactly you
sent until the mailing list comes back up. But if you're okay with
that (I am), then this is a great way to do it.
~Kyle
- --
The search for the truth is the noblest occupation of man. Its
publication is a duty.
-- Anne Louise Germaine de Stael
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFFZHlUBkIOoMqOI14RAvsWAJ47zq7VOUFz/hQjAuYUiIY/KvXdpACbB35X
Jalqs40fjWMOpOqIHzdWdmE=
=FC73
-----END PGP SIGNATURE-----