From bob at ucc.gu.uwa.edu.au Thu Nov 22 00:30:31 2012 From: bob at ucc.gu.uwa.edu.au (Andrew Adamson) Date: Thu, 22 Nov 2012 00:30:31 +0800 (WST) Subject: [tech] SpamAssassin Changes Message-ID: Hi all, As part of my mission to reduce the amount of spam that lands in my inbox, I've made a fairly large change to our spamassassin setup on mooneye. The change is to turn on network checks, so public DNS blacklists are checked for known spammers [1], and there is also some fuzzy hash checking of our incoming mail against known spam emails [2] using pyzor [3] and razor2 [4]. The changes were too numerous to list, but it's worth noting for future reference that I came up against python deprecation warnings thanks to pyzor being written for python 2.4. The warnings cause spamassassin to fail parsing the response. The fix is to simply ignore deprecation warnings in the script for now [5]. CAN YOU PLEASE KEEP AN EYE OUT FOR FALSE POSITIVES. I don't want to have legitimate emails going into spam folders! Andrew Adamson bob at ucc.asn.au |"If you can't beat them, join them, and then beat them." | | ---Peter's Laws | [1] http://wiki.apache.org/spamassassin/DnsBlocklists [2] http://wiki.apache.org/spamassassin/HashSharingSystem [3] http://wiki.apache.org/spamassassin/UsingPyzor [4] http://wiki.apache.org/spamassassin/UsingRazor [5] https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/394775 From bob at ucc.gu.uwa.edu.au Sat Nov 24 21:21:16 2012 From: bob at ucc.gu.uwa.edu.au (Andrew Adamson) Date: Sat, 24 Nov 2012 21:21:16 +0800 (WST) Subject: [tech] SpamAssassin Changes In-Reply-To: References: Message-ID: Today I had the amazing idea of checking how many people are actually using UCC's spam filtering. Six. Yes, SIX people use it. Which is a shame, because it's actually pretty good. Only 23 people use UWA's spam filter! In short, I pity you all because you must have spam coming out your ears (unless you're one of those heathens who forwards your email to gmail, boooo). There's two available levels of filtering - UWA level filtering, and UCC level filtering. The UWA filtering only blocks the most obvious of spam, so I don't think it's all that useful. UCC's spam filter is getting better by the day, and I haven't had any issues with false positives since it was reconfigured earlier this year. To enable the weak UWA filtering, log into motsugo or mussel and run `touch ~/.filter-my-spam` To enable the awesome-sauce UCC filtering, log into motsugo or mussel and run `touch ~/.filter-my-spam-more` If you want, you can also help with training the spam filter. If something makes it through and isn't recognised as spam, bounce it to spameater at ucc.asn.au, and the filter will learn from it for next time. Please note you should only bounce actual spam from senders you have never given permission to email you - other people might still want to get emails from that mailing list you don't want to be a member of anymore! Andrew Adamson bob at ucc.asn.au |"If you can't beat them, join them, and then beat them." | | ---Peter's Laws | On Thu, 22 Nov 2012, Andrew Adamson wrote: > Hi all, > > As part of my mission to reduce the amount of spam that lands in my inbox, > I've made a fairly large change to our spamassassin setup on mooneye. The > change is to turn on network checks, so public DNS blacklists are checked > for known spammers [1], and there is also some fuzzy hash checking of our > incoming mail against known spam emails [2] using pyzor [3] and razor2 > [4]. > > The changes were too numerous to list, but it's worth noting for future > reference that I came up against python deprecation warnings thanks to > pyzor being written for python 2.4. The warnings cause spamassassin to > fail parsing the response. The fix is to simply ignore deprecation > warnings in the script for now [5]. > > CAN YOU PLEASE KEEP AN EYE OUT FOR FALSE POSITIVES. I don't want to have > legitimate emails going into spam folders! > > Andrew Adamson > bob at ucc.asn.au > > |"If you can't beat them, join them, and then beat them." | > | ---Peter's Laws | > > [1] http://wiki.apache.org/spamassassin/DnsBlocklists > [2] http://wiki.apache.org/spamassassin/HashSharingSystem > [3] http://wiki.apache.org/spamassassin/UsingPyzor > [4] http://wiki.apache.org/spamassassin/UsingRazor > [5] https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/394775 > From bob at ucc.asn.au Fri Nov 30 09:31:51 2012 From: bob at ucc.asn.au (Bob Adamson) Date: Fri, 30 Nov 2012 09:31:51 +0800 Subject: [tech] Fw: Cron /usr/bin/python2.4 -S /usr/local/mailman/cron/disabled (failed) Message-ID: <0C610B89D0B14B62B4D526D2896934CE@Prometheus> Hi all, We've been getting the below errors in emails for some time now and I think it should probably be dealt with. My python foo is pretty poor, but as far as I can tell the getBouncingMembers function is implemented in /usr/local/mailman/Mailman/OldStyleMemberships.py. Would somebody on wheel mind taking a look? Of course, non-wheelians are welcome to comment but unfortunately we can't give you root access on mooneye to fix it yourself. Bob -----Original Message----- From: Cron Daemon Sent: Friday, November 30, 2012 9:00 AM To: mailman at ucc.gu.uwa.edu.au Subject: Cron /usr/bin/python2.4 -S /usr/local/mailman/cron/disabled (failed) Traceback (most recent call last): File "/usr/local/mailman/cron/disabled", line 220, in ? main() File "/usr/local/mailman/cron/disabled", line 161, in main for member in mlist.getBouncingMembers(): File "/usr/local/mailman/Mailman/MemberAdaptor.py", line 207, in getBouncingMembers raise NotImplementedError NotImplementedError From bob at ucc.gu.uwa.edu.au Fri Nov 30 11:07:02 2012 From: bob at ucc.gu.uwa.edu.au (Andrew Adamson) Date: Fri, 30 Nov 2012 11:07:02 +0800 (WST) Subject: [tech] Testing VERP Message-ID: I've just enabled VERP on our mailman instance. This is a test to see if it's working. http://cr.yp.to/proto/verp.txt if you're interested. Andrew Adamson bob at ucc.asn.au |"If you can't beat them, join them, and then beat them." | | ---Peter's Laws |