On 13May2012 06:21, Jim Graham <[email protected]> wrote:
| On Sun, May 13, 2012 at 04:53:32PM +1000, Cameron Simpson wrote:
| > Try 'g'; it keeps both me and the mutt-users. Works nicely.
|
| On some lists I'm on, people get royally PO'd about it. :-)
| I just find it annoying. If I mention it (this case excepted, as it's
| keeping me from using 'L'ist reply) I just point out that it's a waste
| of time.
I should spent some time with a message hook to get my replies doing the
Right Thing on a case by case basis then...
[...snip scary stuff...]
| OB Mutt: I use fcc-hook frequently to store related groups of e-mail.
| For example, everyone from [publisher], and all e-mails I send to
| [publisher], go in ~/Mail/[publisher]. All e-mails to/from members of
| our local homebrew club go into ~/Mail/HBU, and so on. :-)
I do this in my mail filters. That way if I need to I can refile a
message without composing an email; just copy/move it to the right spool
folder. My setup goes:
cron runs getmail regularly, delivers to "spool"
once a second, my filtering program polls spool-in (divert spam, the rest
to "spool"), spool (filter inbound email to various folders), spool-out
(file outdound email - this is $record), spool-xref (cross file
messages)
The maifiler is a daemon, so there's no fork/exec load, and it rereads the
rules files and my maildb when they change, so no need to restart it.
So... messages that get though "spool-in" without a match land in
"UNKNOWN". 99% is spam, but for the legit stuff I add a new rule
then move the message into spool-in again. And it gets filed.
Most rules are one liners:
folder tag pattern
The folder field is a commas separate list of targets:
foo@bar forward to email address
|command pipe to command
foldername save in folder
The tag is set as the X-Label header (unless it is ".", meaning no
label). The patterns take the form:
foo@bar matches foo@bah in the to/cc/bcc headers
hdr,hdrs,...:foo@bah
matches foo@bah in the named headers
hdr,hdr,...:/foo
matches the regexp "foo" in the named headers,
typically the subject line
(GROUP|GROUP|...)
matches a member of the specified GROUPs in the headers,
so this is how I crossfile
Importantly, the "foo@bah" match is done by a proper RFC2822 address
parse instead of a regexp, avoiding a lot of the procmail parsing weaknesses.
I can afford the poll-once-a-second because unlike procemail, mailfiler
parses the rules just once.
Cheers,
--
Cameron Simpson <[email protected]> DoD#743
http://www.cskk.ezoshosting.com/cs/
Hang on everyone!!! Here comes another Swiiiiitch-baaaaack!!
- unnamed RCRII'er
