%TOC% All GNHLUG mailing lists are currently hosted on the server rogue at Codemeta (thanks, Bruce!), and run via Mailman. As of this writing, all the lists are open to self-subscription, and most allow any subscriber to post. Admin work is generally done via the web-based admin interface for each list. See the [[http://mail.gnhlug.org/mailman/admin][list of list admin pages]]. A link to each list's admin page is also present at the bottom of each list's listinfo page. The admin passwords are not documented on this public website. If you need access, contact one of the existing list admins; if they trust you, they will presumably give you the password. You can find out the current list admins for a given list on the listinfo page for said list. ---+ Announce List Posts to gnhlug-announce are restricted. This is done mainly to keep mis-directed messages from annoying people who just want announcements. Posts can be manually approved by a list admin (see Queue Management on this page). There is also a short list of addresses whose posts are not held for approval. The exact critera for inclusion on said list are not formally defined. Generally speaking, this is the various chapter coordinators. ---+ Queue Management Messages from non-subscribers are held for manual disposition. Since the list posting addresses are in circulation on the Internet, they get spam. The queue of held messages thus quickly accumulate spam. They need to be cleaned on a regular basis -- at least weekly, sometimes daily. Failure to do so results in the queue growing to unworkable proportions depressingly quickly. To clear the queue: Log in to the admin interface, click "Tend to pending administrative requests", and deal with the resulting pile of crap^W^W^W list of messages. Most messages will be spam. So you generally go along, set each message to "Discard", and then click "Submit". ---++ Quick Links For convenience, the following links to the various queues may be useful. * http://mail.gnhlug.org/mailman/admindb/gnhlug-discuss * http://mail.gnhlug.org/mailman/admindb/gnhlug-jobs * http://mail.gnhlug.org/mailman/admindb/gnhlug-announce * http://mail.gnhlug.org/mailman/admindb/gnhlug-org Tip: Put the above links in a bookmark folder in Firefox, and use the "Open in tabs" option that appears at the bottom of the resulting bookmark menu. ---++ Discard-All Bookmarklet Most messages end up being discarded. One quickly wishes "Discard" were the default, rather then "Defer". The following bookmarklet will accomplish that; it sets all the checkboxes to "Discard". Of course, you still have to weed through all the spam and set any non-spam to "Approve". A little caution is in order; it is easy to accidentally discard a useful post this way. <A HREF="javascript:(function(){var af,fi,f,ci,c;af=document.forms;for(fi=0;fi<af.length;++fi){f=af[fi];for(ci=0;ci<f.length;++ci){c=f[ci];if((c.type==%22radio%22)&&(c.value==%223%22)){c.checked=true;}}}})();">Discard All</A> The above bookmarklet is a kludge; it may break if the Mailman config or version changes, or on browsers other then Firefox 1.5, or if the wind blows. ---++ More automation As of 11/03/2005, Jeff Kinz is running a curl/bash/bogofilter script which automatically discards 92-95% of these on the gnhlug-org list. The idea for this tool was generated by the thread seen here: http://www.mail-archive.com/gnhlug-org@mail.gnhlug.org/msg01363.html The final shape of the script bears almost no resemblance to the ideas in the discussion. The final approach is based on the principle of "Do No harm". No false positives are allowed, no submissions approved without direct human intervention, no notification emails can be generated that might be sent to forged addresses, must not interfere with the existing system's function and the tool must not put extra load on the servers. Current approach: 0. When Mailman gets a non-member submission it sends an email to gnhmod@Jeff's domain activating a procmail recipe which kicks off the script. 1. A curl command is used to fetch the gnhlug mailman pending requests page, containing fragments of non-member submissions to the list. 2. The script loops through each submission, extracting the fragment and using bogofilter to score its "spaminess". 3. If the score is twenty percent higher than the cutoff for spam, the email is automatically discarded. Because the spam going to the list is very uniform this results in more than 90% of the spam being discarded immediately despite the 20% higher score requirement. 4. Low-scoring, non-discarded fragments are kept until a human can review them using the same tool in a different mode. The human can discard the spam and/or feed the spam into bogofilter so that any more of the same spam will be identified by the system. Stats as of: Mon 01/02/06 09:43 Total reviewed: 1411, killed: 1320 (93%), ignored: 91 The approach is described here so that it can be reviewed for potential problems. From its it activation to Jan 1, 2006, this system was carefully watched. It seems to be performing well and will not be so carefully monitored. If you notice any real or even potential problems with this approach please let Jeff Kinz know immediately.
This topic: Org
>
MailingLists
>
ServerMailLists
Topic revision: r5 - 2006-01-02 - JeffKinz
All content is Copyright © 1999-2025 by, and the property of, the contributing authors.
Questions, comments, or concerns?
Contact GNHLUG
.
All use of this site subject to our
Legal Notice
(includes Terms of Service).