On Sat, Apr 16, 2011 at 06:31:39AM -0600, Paul E Condon wrote:
On 20110415_163420, Ed Blackman wrote:
I have actually been migrating from Maildir to MH for backup
efficiency.  I have procmail sort email into folders, and put a
(sometimes modified) copy in my inbox where I can read and delete it,
secure in the knowledge that I kept the original.

That means that I don't regularly read any mail folder other than my
inbox.

This is very interesting. One thing you don't mention in this very
brief brief for MH is the placement in your processing chain of
spamassassin, or other spam filtering. Is the sending emails thru SA
done in the same procmail step that splits the emails into two streams,
inbox and archive?

I'm getting around to cleaning up old email, and saw that I didn't respond. Sorry for the delay.

The rough order of my procmailrc is:
- Emails consumed directly by programs, mostly from other programs.
- Anti-spam

Messages that get to this point either didn't trip anti-spam rules on a first pass, or tripped a rule and got segregated, but then got released and reinjected with a header that ensures that it skips the anti-spam rules on the second pass.

Decisions on archiving come next. I use bogofilter with a different config file and wordlist to add "X-Archivicity".

Messages that are identified as not-archive, and messages to identifiable mailing lists regardless of archivicity, get copied to a archive-not folder (and copied to the list folder, for identifiable mailing lists). A cron task prunes archive-not down to a fixed number of messages that represents an average month's worth of no-archive messages. That gives me a small fallback if I later wish I had saved something.

Messages that are identified as unsure-archive get copied to the archive-unsure folder, which I periodically empty manually with mutt macros that retrain bogofilter and save the email to archive or archive-not.

Messages that are identified as yes-archive get copied to the archive folder.

All three archive choices are copies, so the message is still being processed. The final stop is inbox.

--
Ed Blackman

Attachment: signature.txt
Description: Digital signature

Reply via email to