Listmaster

… because they are bouncing. In my ongoing attempt to investigate and fix problems of our mailinglist-server, i found that we only had a working bounce-detection for lists starting debian-* minus debian-private and the three digest-lists. So i rewrote some parts of the bounce detection: We now have four categories of lists: high (30 or more mails a day) medium (20 or more mails a week) low (10 or more mails a month) very-low (the rest) for these four categories we calculate a spam-rate depending on the number of distributed messages and the number of bounces in the timerange of 24 hours for ‘high’ lists, 7 days for ‘medium’ lists, 30 days for ’low’ lists and 90 days for ‘very-low’ lists. ...

While analysing the pole setters in our internal bouncers-Hitlist i found that some of them run a mail2news-Gateway. The problem is: our Mailinglists leave Mail-Headers mostly untouched, and so headers like X-Trace or X-Complaints-To are passed through without modifications. If a mail containing those headers is handed over to inews (as in INN) it rejects it, and the bounce comes back to us: <> XXXXX@XXX.com> >: Command died with status 1: “/usr/bin/maildrop”. Command output: inews: cannot send article to server: 441 Can’t set system “X-Complaints-To” header inews: article not posted ...

Just a quick note: while wading through the list-archives, drop-boxes and list-configuration to find false positives and possiblities to optimise our mailinglists spam level i accidently removed the inclusion of our spamfilters from most lists. I appologise for this. Luckily zobel discovered my error and fixed it at 14:30 CET.

I’m just wadeing through Debian-Mailinglists on the search for enhancements and false-positives. and i just came over debian-security-announce, a lists that sends a helpful message back to submitters that aren’t allowed to send out advisories. That message didn’t contain a Precedence-Header so i added one, and wondered which value would be appropriate… I remember to have seen three values: ‘junk’, ‘bulk’ and ’list’ (the latter should be set for all our Mailinglists). ...

From time to time we have the problem that a mail posted to a list triggers an autoresponse (vacation, bounce, tdma) from an unexpected source. Sometimes it isn’t possible to identify the subscriber who is causing this. One example for this was “petsupermarket”. So i wrote a small tool, which takes Mailadresses as input and resolves the domains until it reaches IP-level, so it is possible to identify “related” addresses to such an incident. ...

Hi. We were notified that German DWN, and the Original DWN weren’t sent out. Investigation showed that Diplomats (in German translation Diplomaten) matched the bad word ‘Diploma’, so it is dropped in our spambox. I resent German DWN yesterday and the Original DWN some minutes ago. sorry for the inconvinience.

We get regular requests from Gmail-Users that don’t receive their own mails back, when they post something on a mailinglist to which they are subscribed. So if this happens to you, first check if your mail shows up in our mailarchive. If it appears there (wait some time that the archive can catch up) your mail has been successfully posted to the list, and your copy has also been send and is most likely accepted by Gmail. But Gmail seems to drop that mail internally (or sort it in a spamdropbox?) maybe because From and Receipient-address are the same. (We get two or three requests of that kind per week, and everytime we investigated, we found this is the case) ...