> -----Original Message----- > From: Jens E. Madsen Jr. [mailto:[EMAIL PROTECTED] > Sent: Friday, February 13, 2004 1:20 PM > To: [EMAIL PROTECTED] > Subject: Approaches to handling mail lists > > > Dear Spamassassin User List, > > Thanks for the excellent program. It has proven to be very effective. > > I am looking for a good way to handle mail list that go through > spamassassin. It should be able to handle both moderated and unmoderated > lists. It should also be user configurable so that I do not have to > change the system configuration file each time a user adds a mail list. >
I don't know if such a tool exists, but it would be great if there were a CGI driven GUI page that let users configure their $HOME/.spamassassin/user_prefs without knowing that's what they're doing. Whitelists/blacklists, spam cutoff threshold, spam tagging style, etc. could all go there. It'd be nice if the tool was integrated into a web mail interface, where they could go through their inbox, spam folders, and perhaps other folders and click in a check box for "spam", "ham", "whitelist sender", "whitelist maling list", and so on. > I currently provide procmail to filter either the tag in the Subject > line or the list id in the header to sort into my mail list buckets for > the users here. This is done at the user level. There are some nice procmail scripts out there that detect lists and file automatically. Nancy McGough has collected a couple of them here: http://www.ii.com/internet/robots/procmail/qs/#genericSBE > Subject tags always work > even if spamassassin tags it as spam. The List id is lost in the > attached spam email. take a look at 'report_safe_copy_headers'. Maybe something like: report_safe_copy_headers List-ID Mailing-List Precedence and so on. see: http://www.spamassassin.org/doc/Mail_SpamAssassin_Conf.html#message%20taggin g%20options > I would like to have the mail list filter all mail > into the mail list bucket, even if it is spam. > > In a previous thread some one mention using the following: > > whitelist_from_rcvd [EMAIL PROTECTED] > > to white list all mail for spamassassin and I can easily show my users > how to do this. Technically that isn't a filter for mailing lists only, however. If [EMAIL PROTECTED] sends you something, it'll be whitelisted as well. > This should allow those user that are listed in RBLs or > whose mailer isn't liked by spamassassin to make it into the bucket. > Could get complicated for the users, if they don't have a clear GUI to establish those settings. > My concern now is for the unmoderated or unfiltered mail list. How can I > put the mail into the correct bucket and tag the real spam as spam? > See the link above, for some ideas. If the lists are filtered first, they're never passed to SA, btw. That's what I do, and it works fine, though sometimes even the most esteemed technical lists are spammed. For a lot of lists, if you're filtering all incoming mail, you can use whitelist_to. For example: whitelist_to [EMAIL PROTECTED] whitelist_to [EMAIL PROTECTED] would whitelist all yahoogroups and all the GNU groups in one fell swoop. The To: check won't avoid spoofs however, and some mailing lists frankly need a spam filter, so you need to balance risks versus ease of use. Reading the docs. I couldn't tell if header checks could check for things like List-ID, but it would seem so: header SYMBOLIC_TEST_NAME header op /pattern/modifiers [if-unset: STRING] Define a test. SYMBOLIC_TEST_NAME is a symbolic test name, such as 'FROM_ENDS_IN_NUMS'. header is the name of a mail header, such as 'Subject', 'To', etc. 'ALL' can be used to mean the text of all the message's headers. 'ToCc' can be used to mean the contents of both the 'To' and 'Cc' headers. 'MESSAGEID' is a symbol meaning all Message-Id's found in the message; some mailing list software moves the real Message-Id to 'Resent-Message-Id' or 'X-Message-Id', then uses its own one in the 'Message-Id' header. The value returned for this symbol is the text from all 3 headers, separated by newlines. op is either =~ (contains regular expression) or !~ (does not contain regular expression), and pattern is a valid Perl regular expression, with modifiers as regexp modifiers in the usual style. Note that multi-line rules are not supported, even if you use x as a modifier. If the [if-unset: STRING] tag is present, then STRING will be used if the header is not found in the mail message. Test names should not start with a number, and must contain only alphanumerics and underscores. It is suggested that lower-case characters not be used, as an informal convention. Dashes are not allowed. Note that test names which begin with '__' are reserved for meta-match sub-rules, and are not scored or listed in the 'tests hit' reports. Test names which begin with 'T_' are reserved for tests which are undergoing QA, and these are given a very low score. If you add or modify a test, please be sure to run a sanity check afterwards by running spamassassin --lint. This will avoid confusing error messages, or other tests being skipped as a side-effect. ----- might be some interesting possibilities there. > We do not mind having FPs since we do not use spamassassin to delete > mail, through procmail of course. > Sounds good. > What would be nice is a user configurable option such as maillist that > could have a user set value, say -4, and not the -100 from whitelist. Take a look at 'more_spam_to', I don't know what weight it scores (I think -10) or whether that is configurable?
