On 31Dec2012 09:04, Jamie Paul Griffin <ja...@kode5.net> wrote:
| * Cameron Simpson <c...@zip.com.au> [2012-12-31 10:34:45 +1100]:
| > On 30Dec2012 12:11, Chris Green <c...@isbd.net> wrote:
| > | My mail is initially delivered by SMTP (to a postfix server running
| > | locally) and then filtered by a python script at the moment. Thus, if
| > | I switch to maildir just now it's the Python libraries which create
| > | the maildirs.
| >
| > Surely then the naming scheme is under your control?
| > Like you, I have my own filing program.
[...]
| I'd be interested to know more about the python methods you guys use
| though. The Maildirs are created in a normal way though, I've not known
| or seen delivery programs create Maildirs with the odd naming schemes
| Chris has described.
I would expect the maildir naming to be totally under Chris' control.
Mine is. The weird names may be Chris trying to work with something
else, like Dovecot which by default has a fairly horrible filesystem
naming scheme for maildirs.
As pointed out elsewhere, telling dovecot to use the "LAYOUT=fs" scheme
improves this.
Regarding filtering tools, my own is mailfiler. Man pages:
Invocation:
https://bitbucket.org/cameron_simpson/css/src/tip/man/mailfiler.1.pod
Rule syntax:
https://bitbucket.org/cameron_simpson/css/src/tip/man/mailfiler.5.pod
The source is up there too.
I run it in a screen session thus:
mailfiler monitor -d 1 ~/mail/spool ~/mail/spool-in ~/mail/spool-out
~/mail/spool-xref ~/mail/spool-spam-subj
to watch a bunch of spool directories for incoming email.
It polls each in sequence regularly, so an arriving nonspam message
gets completely processed almost immediately.
It watches the rules files for updates, so I don't need to restart it if
I change the rules. Because it runs as a daemon it doesn't need to
parse/compile the rules for every new message, unlike procmail.
If I change the rules and want to test them, all I have to do is copy
a test message into =spool or =spool-in to watch mailfiler process it
again. This is surprisingly handy.
New mail is dropped into =spool by procmail.
The mailfiler rules for =spool trim some spam and pass the rest to
=spool-in.
The rules for =spool-in pass things out to various folders for mailing lists
and so forth. Particular items get forwarded to an external account monitored
by my iphone - monitoring alerts, email from particular people, etc.
My muttrc has record=+spool-out. Mailfiler watches that too and
processes sent messages:
< env
out,me,spool-xref,"|cs-aliases-add-email known" . .
That copies anything to =me (my "priority" mailbox) so I have complete
threads there, to =out (my "real" record dir), =spool-xref for
crossfiling, and records email addresses in the "known" group for anyone
I email, thus whitelisting them.
Cheers,
--
Cameron Simpson <c...@zip.com.au>
We're blowing dog-whistles in a city full of cats.
- overhead by WIRED at the Intelligent Printing conference Oct2006
