Re: [Mailman-Users] subject filtering
Hi Patrick! I've tried to put the subject: .*\*SPAM\*.* line into the bounce_matching_headers and it gave me an error , i try to translate it to english from hungarian. : in the bounce matching headers box you must give a valid filter line, unless it will be ignored and u asked me wheather *SPAM* is at the begining or at the end of the subject: AT THE BEGINNING. thanks for ur reply and for your help in advance! greets Tamas Gabor On 7/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: My server is behind a router, and all the mails coming via that router. THAT router tag the mails with a SPAM* subject line when it reaches a limited spam score. ANd now comes my problem: i cannot filter it out via the mailman admin interface. all the spams get into the list, and my users and me getting annoyed. Is the SPAM* at the beginning or end of the subject? Or does it replace the subject? Anyway, add to Privacy Options bounce_matching_headers: subject: .*\*SPAM\*.* ..This will match and filter anything that has '*SPAM*' in the subject. -- - Patrick Bogen P.s.: w8ing? Come on. :P This message was sent using IMP, the Internet Messaging Program. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] subject filtering
On 7/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've tried to put the subject: .*\*SPAM\*.* line into the bounce_matching_headers and it gave me an error , i try to translate it to english from hungarian. : in the bounce matching headers box you must give a valid filter line, unless it will be ignored What version of mailman are you running? 2.1.8 doesn't seem to do any validation on this field- or, at least, that regex is valid in my setup. Perhaps someone else knows more about where this error is coming from? -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] stange domain/url question
Not too long ago, we switched out domain from wwwadm.mydomain.com to lists.mydomain.com. I used fix-url on all the lists, and when we create all lists now, we create then as ./newlist [EMAIL PROTECTED] But when the email is sent to the administrator for these new lists it has wwwadm.mydomain.com referenced in it: There is also an email-based interface for users (not administrators) of your list; you can get info about using it by sending a message with just the word `help' as subject or in the body, to: [EMAIL PROTECTED] To unsubscribe a user: from the mailing list 'listinfo' web page, click on or enter the user's email address as if you were that user. Where that user would put in their password to unsubscribe, put in your admin password. You can also use your password to change member's options, including digestification, delivery disabling, etc. Please address all questions to [EMAIL PROTECTED] Does anyone know why this is happening? Or how I get this to change to lists.mydomain.com? My users are pretty much computer novices and this will confuse them. Any assistance is appreciated. Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] subject filtering
Patrick Bogen wrote: On 7/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've tried to put the subject: .*\*SPAM\*.* line into the bounce_matching_headers and it gave me an error , i try to translate it to english from hungarian. : in the bounce matching headers box you must give a valid filter line, unless it will be ignored What version of mailman are you running? 2.1.8 doesn't seem to do any validation on this field- or, at least, that regex is valid in my setup. Perhaps someone else knows more about where this error is coming from? I think Patrick is correct here, but what exactly did you put in bounce_matching headers. If it is exactly as above, it should be OK. Also, the '.*' is not really necessary at the beginning and end of the regexp since the regexp is found anywhere in the header, so you could use just subject: \*SPAM\* and it would be the same. You may not really want to use bounce_matching_headers since a match there will cause the message to be held and you may want to discard it. If you want it discarded, you have to use header_filter_rules. You may also find it easier to look at a different Spamassassin header such as the X-Spam-Flag: Yes header. See http://docs.python.org/lib/re-syntax.html. Also see http://mail.python.org/pipermail/mailman-users/2006-July/052298.html for a bit of general information about header_filter_rules. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] stange domain/url question
Anne Ramey wrote: Not too long ago, we switched out domain from wwwadm.mydomain.com to lists.mydomain.com. I used fix-url on all the lists, and when we create all lists now, we create then as ./newlist [EMAIL PROTECTED] snip you can get info about using it by sending a message with just the word `help' as subject or in the body, to: [EMAIL PROTECTED] snip Please address all questions to [EMAIL PROTECTED] This makes no sense. It shouldn't be -admin because that's a Mailman 2.0.x artifact, but the 'mailman' site list didn't appear until 2.1. Assuming this is a typo and is really [EMAIL PROTECTED], I proceed. Does anyone know why this is happening? Or how I get this to change to lists.mydomain.com? My users are pretty much computer novices and this will confuse them. This is really the same issue as http://mail.python.org/pipermail/mailman-users/2006-July/052345.html which see. If you only have the one domain, and it is DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST and is the only entry in VIRTUAL_HOSTS, you shouldn't need to specify a domain to newlist and everything should be OK. In your case, the domain in the mailman address comes directly from a lookup of DEFAULT_URL_HOST in the VIRTUAL_HOSTS dictionary. The domain in the list-request address is the host_name attribute of the list (on the General Settings page) which came from a lookup of lists.mydomain.com (based on your newlist command) in VIRTUAL_HOSTS or if not found, DEFAULT_EMAIL_HOST. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] subject filtering
Idézet (Mark Sapiro [EMAIL PROTECTED]): Patrick Bogen wrote: On 7/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've tried to put the subject: .*\*SPAM\*.* line into the bounce_matching_headers and it gave me an error , i try to translate it to english from hungarian. : in the bounce matching headers box you must give a valid filter line, unless it will be ignored What version of mailman are you running? 2.1.8 doesn't seem to do any validation on this field- or, at least, that regex is valid in my setup. Perhaps someone else knows more about where this error is coming from? my mailman v is 2.1.5 I think Patrick is correct here, but what exactly did you put in bounce_matching headers. If it is exactly as above, it should be OK. Also, the '.*' is not really necessary at the beginning and end of the regexp since the regexp is found anywhere in the header, so you could use just subject: \*SPAM\* i tried with it also on bounce matching header , but i got the same error as above. and it would be the same. You may not really want to use bounce_matching_headers since a match there will cause the message to be held and you may want to discard it. If you want it discarded, you have to use header_filter_rules. Yes, it'd be better not to discard each spam. You may also find it easier to look at a different Spamassassin header such as the X-Spam-Flag: Yes header. i've looked into the spam mail header, and i see these: X-SZTE-Spam-Status: YES X-Spam-Status: YES X-Spam-Flag: YES SZTE is my univ mail firewall server and it make this tag on the spams' header so whit this new info, what dou suggest me to do, to filter spam by subject? thanks you folks! greets: Tamas Gabor See http://docs.python.org/lib/re-syntax.html. Also see http://mail.python.org/pipermail/mailman-users/2006-July/052298.html for a bit of general information about header_filter_rules. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan This message was sent using IMP, the Internet Messaging Program. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] FW: FW: No One Can Post a Message but the Server
And the answer is ... The newsletter was held. [1] Subject: God's Vineyard -- The Power of His Presence Size: 6493 bytes Reason: Post by non-member to a members-only list Received: Wed Jul 19 04:23:01 2006 The header line in the newsletter looks like this: From: [EMAIL PROTECTED] This is also the name of the list that manages the newsletter distribution. The account the mail is sent from is [EMAIL PROTECTED] This is simply a server userid where the cron script is executed. No one receives mail on this server account and there is no pop mailbox setup for this user name. More clues! Greg -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 7:39 PM To: Greg Sims; 'Patrick Bogen' Cc: mailman-users@python.org Subject: RE: [Mailman-Users] FW: FW: No One Can Post a Message but the Server Greg Sims wrote: I found /var/log/vette and see an entry that matches the time the newsletter cron was run. Here is the log entry: Jul 18 04:23:01 2006 (8553) Message discarded, msgid: [EMAIL PROTECTED] I hope this gives you more clues. Is there some way for mailman to be verbose in the logs? I suggest until you get this debugged that you set Privacy options...-Sender filters-member_moderation_action and Privacy options...-Sender filters-generic_nonmember_action to Hold. Then the vette log, the held message notice and the admindb interface will all give the specific reason for the hold. Also, if Content filtering-filter_content is Yes, set Content filtering-filter_action to Forward to List Owner. Then after you get this debugged, you can set these back to Discard. My best guess at this point is that your Approved: pw header has trailing spaces. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] stange domain/url question
Mark Sapiro wrote: snip Please address all questions to [EMAIL PROTECTED] This makes no sense. It shouldn't be -admin because that's a Mailman 2.0.x artifact, but the 'mailman' site list didn't appear until 2.1. Assuming this is a typo and is really [EMAIL PROTECTED], I proceed. You are incorrect. That is not a typo...it was copied and pasted from the email I was sent this morning when I did a test. I'm running 2.1.8, but it's been upgraded time and again. Does anyone know why this is happening? Or how I get this to change to lists.mydomain.com? My users are pretty much computer novices and this will confuse them. This is really the same issue as http://mail.python.org/pipermail/mailman-users/2006-July/052345.html which see. If you only have the one domain, and it is DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST and is the only entry in VIRTUAL_HOSTS, you shouldn't need to specify a domain to newlist and everything should be OK. In your case, the domain in the mailman address comes directly from a lookup of DEFAULT_URL_HOST in the VIRTUAL_HOSTS dictionary. The domain in the list-request address is the host_name attribute of the list (on the General Settings page) which came from a lookup of lists.mydomain.com (based on your newlist command) in VIRTUAL_HOSTS or if not found, DEFAULT_EMAIL_HOST. My default url host was still the old. I'll change it and see if that makes the difference. Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] rejecting spam disables local subscribers on remote lists
We recently implemented a policy such that any incoming message that scores higher than 10 with SpamAssassin is rejected at our MX servers with: 550 5.7.0 message not delivered due to suspect content We've discovered that this policy has interaction problems with recipients at our site who are subscribed to external mailing lists. Here's what happens: 1. Someone at our site is subscribed to a random Mailman mailing list on the Internet. 2. The owners of the mailing list have made little to no attempt to filter spam. As a result, the mailing list passes on spam to subscribers at our site. 3. We detect the spam that Mailman attempts to relay to our subscribers and reject it per above. 4. Mailman, upon receiving the bounces, assumes that the messages bounced because the recipient addresses are no longer valid, and disables and/or removes them. 5. Our users, upon being given the brush-off by Mailman at the remote site, blame us. The fundamental problem is that the owners of the mailing list, by not taking steps to protect their list from spam, are essentially operating an opt-in spam amplification and relaying system. But given that we have no control over how these individuals [mis]manage their mailing lists, we are pondering how to best address this issue on our end. I just looked at Mailman/Bouncers/DSN.py, to see if Mailman was looking at the Status field of the message/delivery-status part, but alas, Mailman only pays attention to the Action field. Therefore, no matter what we return as the DSN code, Mailman will assume that any permanent failure occurred because the recipient address was invalid. One possibility would be to not reject incoming messages if they appear to be from Mailman. (We use David Skoll's excellent MIMEDefang package, so we easily have this capability.) But spammers are a devious and clever lot; I have no doubts that they'd quickly realize that they could bypass our spam blocking simply by adding a few Mailman headers to their messages. Another possibility would be to allow our recipients to opt out of the spam rejecting. But this is a last-ditch option. Have others encountered this situation? If so, how did you deal with it? Thanks, James -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Bug in Mailman version 2.1.7.cp2
Mailman version: 2.1.7.cp2 Operating System: Linux Apache version 1.3.36 (unix) I was trying to edit the welcome message subscribers receive upon confirming subscription to a newsletter mailing list for my client. I accessed the admin interface through cpanel and clicked on the link to edit public html pages then clicked on welcome email text file. I made the necessary changes and clicked submit changes. That's when I received the *bug* message: * * * * * Bug in Mailman version 2.1.7.cp2 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. * * * * * I had previously edited the other files without a problem, and those versions are still in tact, performing perfectly. Now, I need to edit this welcome message and can't. I tried the FAQs, but no matches were found for my problem...including going through the full index. Please advise. Thank you, Tiffany __ Eagle Designs Custom Web and Graphic Design Soaring Above the Competition ph: 302-540-7681 fax: 302-834-2416 www.eagle-designs.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] FW: FW: No One Can Post a Message but the Server
Greg Sims wrote:
And the answer is ... The newsletter was held.
[1] Subject: God's Vineyard -- The Power of His Presence
Size: 6493 bytes
Reason: Post by non-member to a members-only list
Received: Wed Jul 19 04:23:01 2006
The Approved: pw header is not working. I don't know why.
To debug further, look at Mailman/Handlers/Approve.py in the Mailman
installation. Immediately following the lines:
from Mailman import mm_cfg
from Mailman import Errors
add the line
from Mailman.Logging.Syslog import syslog
Then about 26 lines further, you will see the following 3 lines:
missing = []
passwd = msg.get('approved', msg.get('approve', missing))
if passwd is missing:
Add two lines so it reads:
missing = []
passwd = msg.get('approved', msg.get('approve', missing))
syslog('error', 'List: %s, Approved pw -%s-',
mlist.real_name, passwd)
if passwd is missing:
Preserve the indentation exactly
Then do 'bin/mailmanctl restart'. This will put an entry in Mailman's
'error' log for each post that contains List: listname, Approved pw
-%s- (with a time stamp and a pid), where %s is replaced either by
the contents of the Approved: (or Approve:) header or by [] if there
is no Approve(d): header.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2
Tiffany Miller wrote: Mailman version: 2.1.7.cp2 Operating System: Linux Apache version 1.3.36 (unix) See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp I was trying to edit the welcome message subscribers receive upon confirming subscription to a newsletter mailing list for my client. I accessed the admin interface through cpanel and clicked on the link to edit public html pages then clicked on welcome email text file. I made the necessary changes and clicked submit changes. That's when I received the *bug* message: * * * * * Bug in Mailman version 2.1.7.cp2 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. If you have access to Mailman's 'error' log, please provide the complete traceback from this error. Without this information, no one has much of a clue as to why this happened. I had previously edited the other files without a problem, and those versions are still in tact, performing perfectly. Now, I need to edit this welcome message and can't. I tried the FAQs, but no matches were found for my problem...including going through the full index. If you are able to 'see' the file system, you should see within Mailman's structure a lists/listname directory where listname is the name of your list followed by an underscore and the host domain, and in that directory, there will be a config.pck and other files and (assuming English language) an en/ subdirectory containing your edited templates. If you can, you can look at the permissions of the files and see what might be different about the subscribeack.txt file (which is the welcome message) vs. the html files you previously edited. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] subject filtering
[EMAIL PROTECTED] wrote: subject: \*SPAM\* i tried with it also on bounce matching header , but i got the same error as above. Perhaps there is some issue with the character set. Those characters must be entered as equivalent to us-ascii and must not be translated by your web server. You may also find it easier to look at a different Spamassassin header such as the X-Spam-Flag: Yes header. i've looked into the spam mail header, and i see these: X-SZTE-Spam-Status: YES X-Spam-Status: YES X-Spam-Flag: YES SZTE is my univ mail firewall server and it make this tag on the spams' header so whit this new info, what dou suggest me to do, to filter spam by subject? The prefixing of the subject with *SPAM* and the addition of the X-Spam-Status: and X-Spam-Flag: headers is done by Spamassassin (not a part of Mailman). I don't know about the X-SZTE-Spam-Status: header. The easiest thing is to filter on the X-Spam-Flag: YES header as that will be present only in spam and doesn't need special characters. Just put X-Spam-Flag: YES in bounce_matching_headers, or if you want to use header_filter_rules, you could just put X-Spam-Flag: as the rule since the header is only present in 'spam' and set the action to Hold for testing, and if you are confident it is working, you can set the action to Discard. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] stange domain/url question
Anne Ramey wrote: Mark Sapiro wrote: snip Please address all questions to [EMAIL PROTECTED] This makes no sense. It shouldn't be -admin because that's a Mailman 2.0.x artifact, but the 'mailman' site list didn't appear until 2.1. You are incorrect. That is not a typo...it was copied and pasted from the email I was sent this morning when I did a test. I'm running 2.1.8, but it's been upgraded time and again. Well then is your site list named 'mailman-admin' (I assumed it was 'mailman')? My default url host was still the old. I'll change it and see if that makes the difference. You need to not only make sure your DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST are correct, you also have to insure that old values from Defaults.py are removed from VIRTUAL_HOSTS. You do this by putting the following in mm_cfg.py: # Remove old VIRTUAL_HOSTS entry from Defaults.py VIRTUAL_HOSTS.clear() # Set correct Domains DEFAULT_URL_HOST = 'correct.web.domain' DEFAULT_EMAIL_HOST = 'correct.email.domain'. # Add to VIRTUAL_HOSTS add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (You don't need the comments). Then restart Mailman (bin/mailmanctl restart) and run fix_url on all lists via bin/withlist -l -a -r fix_url -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] rejecting spam disables local subscribers on remotelists
James Ralston wrote: We recently implemented a policy such that any incoming message that scores higher than 10 with SpamAssassin is rejected at our MX servers with: 550 5.7.0 message not delivered due to suspect content A SpamAssassin score of 10 is pretty liberal. I suspect your users are getting copious spam from their list subscriptions with scores in the 3 to 9.9 range :-) We've discovered that this policy has interaction problems with recipients at our site who are subscribed to external mailing lists. Here's what happens: 1. Someone at our site is subscribed to a random Mailman mailing list on the Internet. 2. The owners of the mailing list have made little to no attempt to filter spam. As a result, the mailing list passes on spam to subscribers at our site. 3. We detect the spam that Mailman attempts to relay to our subscribers and reject it per above. 4. Mailman, upon receiving the bounces, assumes that the messages bounced because the recipient addresses are no longer valid, and disables and/or removes them. 5. Our users, upon being given the brush-off by Mailman at the remote site, blame us. Yes, I see the problem. The fundamental problem is that the owners of the mailing list, by not taking steps to protect their list from spam, are essentially operating an opt-in spam amplification and relaying system. But given that we have no control over how these individuals [mis]manage their mailing lists, we are pondering how to best address this issue on our end. And I wonder how the users separate the wheat from the chaff on these lists and why they want to subscribe to them in the first place, but I digress ... I just looked at Mailman/Bouncers/DSN.py, to see if Mailman was looking at the Status field of the message/delivery-status part, but alas, Mailman only pays attention to the Action field. Therefore, no matter what we return as the DSN code, Mailman will assume that any permanent failure occurred because the recipient address was invalid. Well, really just undeliverable. That's why bounce processing is tunable to require bounces on n separate days with no m-day bounce-free periods in between and to disable delivery and send a number of warning messages at intervals before actually removing the user. But you're right, we could be more discerning about specific status, but even if we change this, by the time these offending sites install the upgrade, you will have solved the problem some other way anyway. One possibility would be to not reject incoming messages if they appear to be from Mailman. (We use David Skoll's excellent MIMEDefang package, so we easily have this capability.) But spammers are a devious and clever lot; I have no doubts that they'd quickly realize that they could bypass our spam blocking simply by adding a few Mailman headers to their messages. You are possibly correct here, but I doubt that spammers would spend the effort just for CMU (where the recipient base is possibly sophisticated enough that their response rate is at the 'too low to bother if there's any cost involved' level anyway). Another possibility would be to allow our recipients to opt out of the spam rejecting. But this is a last-ditch option. Actually, as a user, this would be the option I'd prefer, but I'm probably not a typical user. Have others encountered this situation? If so, how did you deal with it? I don't recall seeing this on the list before, but I hope others will jump in with ideas. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] rejecting spam disables local subscribers on remote lists
At 1:53 PM -0400 2006-07-19, James Ralston wrote: Another possibility would be to allow our recipients to opt out of the spam rejecting. But this is a last-ditch option. I'm in the process of writing an anti-spam article to be published on the LOPSA.org website. Suffice it to say that, if you are a service provider of some sort to multiple customers, it is your responsibility to provide a way to either opt out of the anti-spam processing that you typically perform, or to give your users a way to customize those rules to suit their particular needs. If you're not willing or able to do that, then you're not doing your job -- plain and simple. In that circumstance, your customers should vote with their feet. Their failure to vote with their feet does not absolve you of the responsibility to provide these features to them. And yes, I include myself and my responsibilities as a member of the mail services/postmaster team at python.org in this list. So far, we've gotten lucky and we've had to make relatively few customizations to the rules for specific users. But I don't know how much longer that's going to last. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2
Mark, thanks for the tips. Unfortunately, I do not have access to the root level of this web site, as it's hosted on another server. I'm almost to the point where I will have my own space on a server with access to the root level for my clients, but until then, I'm stuck. So, I can't 'see' the mailman error logs or the file system. I can only view the file manager through my FTP program or cpanel. I checked the error logs for the site, but nothing shows from today. And not sure if it helps, but when I try to edit *any* of the public html files for the newsletter list, I get the same error. Thankfully, the previous changes I made to other 3 files remained stored. Any other suggestions? Tiffany __ Eagle Designs Custom Web and Graphic Design Soaring Above the Competition ph: 302-540-7681 fax: 302-834-2416 www.eagle-designs.com - Original Message - From: Mark Sapiro To: Tiffany Miller ; mailman-users@python.org Sent: Wednesday, July 19, 2006 5:22 PM Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2 Tiffany Miller wrote: Mailman version: 2.1.7.cp2 Operating System: Linux Apache version 1.3.36 (unix) See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp I was trying to edit the welcome message subscribers receive upon confirming subscription to a newsletter mailing list for my client. I accessed the admin interface through cpanel and clicked on the link to edit public html pages then clicked on welcome email text file. I made the necessary changes and clicked submit changes. That's when I received the *bug* message: * * * * * Bug in Mailman version 2.1.7.cp2 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. If you have access to Mailman's 'error' log, please provide the complete traceback from this error. Without this information, no one has much of a clue as to why this happened. I had previously edited the other files without a problem, and those versions are still in tact, performing perfectly. Now, I need to edit this welcome message and can't. I tried the FAQs, but no matches were found for my problem...including going through the full index. If you are able to 'see' the file system, you should see within Mailman's structure a lists/listname directory where listname is the name of your list followed by an underscore and the host domain, and in that directory, there will be a config.pck and other files and (assuming English language) an en/ subdirectory containing your edited templates. If you can, you can look at the permissions of the files and see what might be different about the subscribeack.txt file (which is the welcome message) vs. the html files you previously edited. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Trying to tighten up my security...
Okay... Next hitch... I installed the patch, and tested it (by trying to send an e-mail to the group from an e-mail that I knew wasn't in the group). It was rejected (as expected). I just had an e-mail get through from a non-member! The e-mail is from: Bernardo Spicer [EMAIL PROTECTED] Who is definitely *not* on any of my lists. The group sender filter is set to 'Reject' postings from non-members for which no explicit action is defined. But, I was still notified. Here's the full header of the message that requested approval: Received: from mxs.mail.ru ([203.146.112.225]) by steeplechase-hoa.org (8.13.7/8.13.4) with ESMTP id k6K3TmZt017041 for [EMAIL PROTECTED]; Wed, 19 Jul 2006 21:30:03 -0600 Message-Id: [EMAIL PROTECTED] From: Bernardo Spicer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: wave surface Date: Thu, 20 Jul 2006 03:40:10 -0420 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Content-Type: multipart/related; type=multipart/alternative; boundary==_NextPart_000_006A_01C6ABE8.DFCD64A0 Why did I get a request to approve this message? Thanks!!! Jon -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Monday, July 17, 2006 4:57 PM To: Jon D. Slater Subject: RE: [Mailman-Users] Trying to tighten up my security... Since I'm running 2.1.8 (instead of 2.1.6 as the patch requires), I made the changes by hand, which broke MM. So now I've put it all back the way it was and, at least, MM is back... (Without the patch.) The 2.1.6 listinclusion patch applies cleanly to 2.1.8 without change. cd path/to/2.1.8mailman/Mailman patch -p2 path_to_listinclusion.patch or cd path/to/2.1.8mailman patch -p1 path_to_listinclusion.patch After applying the patch you need to do 'mailmanctl restart' so IncomingRunner will pick up the change to Mailman/Handlers/Moderate.py. What broke? When you patched by hand, did you preserve indentation exactly? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.1/389 - Release Date: 7/14/2006 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Trying to tighten up my security...
Jon D. Slater wrote: I installed the patch, and tested it (by trying to send an e-mail to the group from an e-mail that I knew wasn't in the group). It was rejected (as expected). I just had an e-mail get through from a non-member! The e-mail is from: Bernardo Spicer [EMAIL PROTECTED] Who is definitely *not* on any of my lists. The group sender filter is set to 'Reject' postings from non-members for which no explicit action is defined. But, I was still notified. Here's the full header of the message that requested approval: Received: from mxs.mail.ru ([203.146.112.225]) by steeplechase-hoa.org (8.13.7/8.13.4) with ESMTP id k6K3TmZt017041 for [EMAIL PROTECTED]; Wed, 19 Jul 2006 21:30:03 -0600 Message-Id: [EMAIL PROTECTED] From: Bernardo Spicer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: wave surface Date: Thu, 20 Jul 2006 03:40:10 -0420 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Content-Type: multipart/related; type=multipart/alternative; boundary==_NextPart_000_006A_01C6ABE8.DFCD64A0 Why did I get a request to approve this message? What was the reason in the approval notice you received (it's also in the 'vette' log). Do you have any header_filter_rules defined (in Privacy options...-Spam filters) with Hold action? These are applied before membership tests. Also, it's not relevant to this issue, but I am still interested in the entry from the 'error' log from the admindb bug from the first patch attempt. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
