Mailman 3 January 2003 - Mailman-Developers

Re: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
by Donn Cave Jan. 17, 2003

Jan. 17, 2003

Quoth Phil Barnett <philb(a)philb.us>: | On Tuesday 14 January 2003 4:25 pm, Barry A. Warsaw wrote: ... |> BTW, if anybody else is going to be at the Spam conference, let me |> know. I'd love to have a chat about Mailman, spam and other stuffis. |> I'll be getting in Thursday night. | | I'd love to see mailman get some spam recognition and some thresholds that we | can set to deliberately get rid of the most obvious stuff. The statistical approach sounds very good to me for lists - I guess the spambayes project that some notable Python people have been working with falls in that category, I've been using something called "spamoracle", etc. In this case, though, before you start thinking about thresholds, you have to train the classifier for your list's traffic - furnish it with examples of good and bad mail. After a couple of batches, it's surprisingly accurate with my own mail, and since lists should normally follow a narrower range of subject matter it ought to do even better there. I haven't thought of a real good way to set up the training, though. You want to be able to select particular messages from the archives and feed them into the classifier intact (headers and everything.) That sounds like writing a new archive index from the ground up (which might be a good thing anyway, but I hope I'm wrong and that isn't necessary!) Donn Cave, donn(a)u.washington.edu

2 1

mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
by Bryan Fullerton Jan. 17, 2003

Jan. 17, 2003

Howdy, Nobody seems to be answering questions in mailman-users (is Barry away?), so I'll try this one here. There's a setting in Defaults.py which seems to be just what my customers are looking for to limit the headers being shown in their plain digests - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS. However, this setting appears nowhere in the actual Mailman code except Defaults.py. Was it supposed to be included somewhere? They're rather unhappy that their plain digests are showing things like Precedence and various MIME headers for each message. Thanks, Bryan

4 7

spam filter
by Kory Wheatley Jan. 16, 2003

Jan. 16, 2003

Hi, I would like to discard any email that comes from the from address "big(a)boss.com". I know you can put a filter value in the mm_cfg.py and that will filter mail to be held for moderation; for example, "from: .big(a)boss.com", but I would rather have it be automatically discarded, so there is no need to manually discard these emails when they are held for approval. I would need this for mailman 2.0.13 and mailman 2.1 -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

3 2

Re: [Spambayes] spambayes fronting a mailing list?
by barry＠python.org Jan. 16, 2003

Jan. 16, 2003

[I added mailman-developers to this list because I think people will be interested in my prototype integration of Mailman and spambayes, a statistical learning classifier, which I've targeted for spam fighting on Mailman lists. -BAW]. >>>>> "SM" == Skip Montanaro <skip(a)pobox.com> writes: SM> In my case I sidestepped training altogether because the SM> list's content is a subset of the stuff I'm interested in SM> anyway. Most of the "spam" messages encountered by the list SM> at this point are really of the virus/worm variety, and since SM> it's set up for members only posting, little, if any garbage SM> actually gets through to the list, even without using SM> spambayes. I suspect python.org will be similar, since we have many other spam defenses in place. I've just been playing with my prototype, and yeah, it sure learns fast even with no a-priori training. I'm not 100% a train-on-the-fly approach will work, so it's worth some real world banging. In my simplified approach, you start out holding all unsure and spam. Legit messages will hit one of those first, likely unsure if your list wasn't advertised on Usenet before real people started posting <wink>. There's one extra button on the admindb page called "Train?". Click this if you want to train a held message based on your action. If you approve the message, it gets trained as ham, and if you reject or discard it, it gets trained as spam. Within about 10 messages (first a bunch of ham, then a random and unscientific barrage <wink> of spam and ham) the classifier was doing pretty good. It was catching all the spam and letting through most of the ham. The ham recognition definitely went up as I approved more messages. False positives get caught on the admindb screen, so you approve and train them in one action. Although I never saw any false negatives, I think the way to handle these will be to add a -spam address that people can send messages to. If the list admin sends it then it gets spam trained. If not, the list admin will have a chance to decide whether to spam train it or not. SM> One reason I'm interested in separating pop3proxy into two SM> functions ( POP retrieval/classifying and training/web UI) is SM> that the training/web component should be useful for other SM> spambayes users. Right now in my current environment, SM> training is clunky enough that I only train on unsures and SM> mistakes. While that works okay because my starting corpus SM> was so large (around 20,000 messages) the indications from SM> people who've experimented with that sort of training is that SM> the quality of classification does degrade over time. That's an important point. While I'm not sure that with my approach the quality of classification will improve over time <wink>, I think a training regimen integrated with the admindb stuff will be the most natural for a Mailman list admin. BTW, the hammie.py interface was all I needed for my prototype. One reason for going with hammie is that each mailing list needs its own database, and I can just create a Hammie, associate it with a list, and tie it easily into Mailman's load/save mechanism. -Barry

1 0

[ mailman-Bugs-669296 ] rmlist and held messages
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669296, was opened at 2003-01-16 22:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669296&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 2 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist and held messages Initial Comment: rmlist removes the mailinglist and listarchiv, but held messages are left in /var/spool/mailman/data! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669296&group_i…

1 0

[ mailman-Bugs-669200 ] need ability to block mail from a specific machine
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669200, was opened at 2003-01-16 13:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i… Category: security/privacy Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer(a)MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- >Comment By: jared mauch (jaredmauch) Date: 2003-01-16 14:59 Message: Logged In: YES user_id=131445 i assume this is for discard_these_nonmembers thanks. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 14:54 Message: Logged In: YES user_id=184577 Yes, this functionality exists. It is possible to use python regexps in the Sender Filters (Privacy Options->Sender Filters->Non-member filters). Example: ^.*(a)MX\.HOST$ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i…

1 0

[ mailman-Bugs-669200 ] need ability to block mail from a specific machine
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669200, was opened at 2003-01-16 19:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i… Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer(a)MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 20:54 Message: Logged In: YES user_id=184577 Yes, this functionality exists. It is possible to use python regexps in the Sender Filters (Privacy Options->Sender Filters->Non-member filters). Example: ^.*(a)MX\.HOST$ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i…

1 0

[ mailman-Bugs-669201 ] feature: unified membership allow post list.
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669201, was opened at 2003-01-16 13:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_i… Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: feature: unified membership allow post list. Initial Comment: i host a variety of lists that obtain posts from members and non-members alike. they also have times where the email address they send from changes. i'd like the ability to create a global list of people that are allowed to post to lists and have it be enabled/disabled on a per-list basis. eg: list1 - use list members, extra people and GLOBAL_allow_list list2 - use list members, extra people only. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_i…

1 0

[ mailman-Bugs-669200 ] need ability to block mail from a specific machine
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669200, was opened at 2003-01-16 13:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i… Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer(a)MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_i…

1 0

[ mailman-Bugs-669197 ] lock timeouts need to be reported
by SourceForge.net Jan. 16, 2003

Jan. 16, 2003

Bugs item #669197, was opened at 2003-01-16 13:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669197&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: lock timeouts need to be reported Initial Comment: when accessing the admindb/<listname> cgi, if the system is unable to obtain the list lock, it continually retries to get the lock. the cgi needs to time out after a specified amount of time (30 seconds perhaps?) and write a message saying "something is amiss, could not get list lock". this caused much puzzlement to me today trying to debug one of my lists. (the system was not cleanly restarted earlier today). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669197&group_i…

1 0