On 6 jul 2009, at 20:07, Ned Freed wrote:
it was pretty painless for me to set up cron jobs to suck inwhatever messages I save to certain folders (that could have been namedanything) for training my spam filter.
Are you serious? Cron jobs? Do you have any idea how minute a fraction of the users of email even know what a cron job is, let alone know how to set one up?
Hey, everyone needs a hobby.I have my procmail set up to check whether I have an IMAP session with the server. If so, I let the client do the mail filtering, if not, the server does it. That way, the unread counters for folders get updated when the client is connected, but the client doesn't have to move large volume mailing list traffic to the correct folder, costing me expensive wireless data traffic and/or slowing things down.
About folders for spam: Apple's Mail lets the user select "use this folder for... {sent, drafts, junk, trash}, which is nice if you used a different client before that uses a different folder naming scheme for these things. Works well enough although a little more automation wouldn't hurt.
The point that working with folders can be done with existing software (I later train spamassassin with what Mail put in the "junk" folder, even though SA doesn't know about IMAP) is an important one. Requiring keywords that are hardcoded in clients and servers means deployment will be extremely slow, if it ever happens.