/ Cameron Simpson wrote on Sat 3.Nov'12 at 20:08:03 +1100 / > On 02Nov2012 20:15, Russell L. Harris <rlhar...@oplink.net> wrote: > | * Jamie Paul Griffin <ja...@kode5.net> [121102 19:36]: > | > I have set up macros that bind keys to pass messages to spamassassin > | > using sa-learn and then puts the message into the spam mailbox. Is > | > this the type thing you mean? The spam mailbox can later be used to > | > train spamassassin for future filtering, using procmail. > | > | Is the "return path" the true address of the sender? > > No. > > In legitimate messages it is where errors should go. For a person, that > would normally be themselves. But for a mailing list it would be the > list admin. > > | If so, I would > | like to blacklist such addresses. > > Not a lot of point. > > | The "From:" field shown in the > | message index of Mutt almost always is rewritten -- sometimes to an > | address from which valid messages may originate -- so I hesitate to > | blacklist such addresses. > > Indeed. > > I've just implemented a script for this (adding a message subject as a > spam filter rule), and I have this macro: > > macro index,pager SS > "<save-message>+spool-spam-subj<enter><next-undeleted>" "delete message as > spam by subject" > > I have arranged that messages saved to "+spool-spam-subj" get their subjects > saved to my "spam-subj" mail filing rules file. Details below. > > I am not using spamassassin myself, but have a fairly effective > strategy:
See this is where experience prevails. I would not have thought of something like this. Thanks Cameron for sharing, it looks like an effective method. I just have my mail delivered by smtp so use OpenBSD spamd and spamassassin as well as clamav and unofficial sigs, with procmail sorting as i mentioned. So my set up is different of course.
