Re: [Mailman-Users] Mailman Bug?/no Admin level web access
Elissa wrote: I'm hoping someone can help me fix this. I installed mailman, and couldn't figure out why the web interface didn't work. It seems I CAN access any of the pages, but the admin ones. I get a lovely message in the browser: Bug in Mailman version 2.1.6rc3 We're sorry, we hit a bug! Not sure what your environment is, but I've seen that message in a multi-domain cPanel environment, where you can set up a domain before it's actually living on that host (preparing to move in). You can get as far as creating a list, but when you go to access the admin pages, it fails with that message. As soon as the domain actually resolves to that host, the problem goes away. Scot -- 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 2.1.5, please help
Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/local/mailman/scripts/driver, line 87, in run_main main() File /usr/local/mailman/Mailman/Cgi/create.py, line 55, in main process_request(doc, cgidata) File /usr/local/mailman/Mailman/Cgi/create.py, line 226, in process_request sys.modules[modname].create(mlist, cgi=1) File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create _update_maps() File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) -- 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] confimation system for outside postings
Hi, is there any mailman extension that implements a challange / confirm based system for outside postings? I guess that would stop spam very well, and neither cause much work for the listadmin, and would be very comfortable for the occasional poster (that might read the mailing list via gmane and thus is not subscribed). Regards, Andreas -- [ SECURITY NOTICE ] To: [EMAIL PROTECTED] For your security, [EMAIL PROTECTED] digitally signed this message on 17 May 2005 at 11:11:17 UTC. Verify this digital signature at http://www.ciphire.com/verify. --- [ CIPHIRE DIGITAL SIGNATURE ] --- Q2lwaGlyZSBTaWcuAVdtYWlsbWFuLXVzZXJzQHB5dGhvbi5vcmcAYWpAY2lwaGlyZWxhY nMuY29tAGVtYWlsIGJvZHkAHAEAAHwAfAEAAABV0YlCHAEAAIsCAAIAAgACACCFlI VZ9h6KxvOWMDarP70UatGMqsu0GuBSJ7VpCrEAhwEAXFjiekCd8DXx05lJ0kX8quFhoCB 61nfVM/+P+sXKh71HpyWoyRQGV0SbmGXEizA1qQwvbrWVQWwdlBlJ1l3o1CYkcgkrU2ln RW5k - [ END DIGITAL SIGNATURE ] - -- 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] SOLVED Re: mp3 attachment
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: John Fleming [EMAIL PROTECTED]; mailman-users@python.org Sent: Tuesday, May 17, 2005 12:11 AM Subject: Re: [Mailman-Users] SOLVED Re: mp3 attachment John Fleming wrote: Another very weird thing is the the limited headers on the mail that was successfully delivered with the attachment to the list: Date: Mon, 16 May 2005 21:29:30 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_01C55A5E.581B7FB0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Any comments about the Content Type? The top level Content-Type: multipart/mixed is exactly what it should be for a message with any kind of attachment. That's why if you're filtering, you need multipart/mixed in mime_pass_types as well as audio/mpeg or whatever since the audio/mpeg is a sub part of a multipart/mixed part. And I'm missing my usual headers from ClamAV and SpamAssassin for this mail only! Oh well, this is getting a little disjointed (my fault). I'll report back if and when things clarify a little. - John Maybe the message came to you via some other route? I think it has to do with the way SpamAssassin and ClamAV are integrated with Mailman as handlers. I think they can't handle the attachment. This whole thing really bothered me a couple of days ago because it appeared that after this mp3 attachment was sent, then SA and ClamAV never processed any further email until they were restarted. However, this observation is no longer reproducible (thankfully!), so things are OK. I still don't know why the attachment passes now, when content filtering has been OFF all along. Oh well - CASE CLOSED for now. Thanks for the discussion. - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.11 - Release Date: 5/16/2005 -- 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] confimation system for outside postings
At 1:08 PM +0200 2005-05-17, Andreas Jellinghaus wrote: is there any mailman extension that implements a challange / confirm based system for outside postings? I guess that would stop spam very well, and neither cause much work for the listadmin, and would be very comfortable for the occasional poster (that might read the mailing list via gmane and thus is not subscribed). TMDA is a challenge-response system, and is one of the most loathed attempts to solve the anti-spam problem. Among other things, it turns you into a spam amplifier -- someone sends you millions of spam messages in the name of some other poor sap, and your system sends back millions of challenges which bury his mail server. Even if you solve the Joe Job/spam amplification problem, someone can joe-job you and send out millions of spams in your name, and when people complain to you or the spam bounces (because the recipient address was invalid), your mail machine gets buried trying to send out all those challenges. Bad idea. Really bad idea. Really heinously bad idea. In fact, I can't think of any worse ideas I've heard of in this field. However, if you just have to get an idea of how bad it is, take a look at one example of how to get Mailman working with TMDA at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.007.htp. Keep in mind that I help run the mailman-users and mailman-developers mailing lists, as well as the mail services for python.org and a number of other sites, and this set of instructions scares the willies out of me. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 2.1.5, please help
Sometime on Tue, May 17, 2005 at 05:37:33PM +0800, Alias Mohd FKE said: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! I am also facing same problem. This has something to do with unicode mails waiting in the moderation queue. I couldn't find any solution yet. Anurag -- 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] Mailman user interface
Hi! I would like to know if someone of you have heard of a possible mailman web user interface that could allow you to reply directly at a post (like a forum for example). Best reguards, Jean-Philippe Giola -- 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] Allow a domain to post to a list
The syntax does not work. I put the config directive in a file posters.config and when I aply the config this is the result: system:~/scripts/listas/mailman/config# cat posters.config posters='[EMAIL PROTECTED]' system:~/scripts/listas/mailman/config# config_list -v -i posters.config testlist attribute posters changed system:~/scripts/listas/mailman/config# config_list -o - testlist | grep posters posters = '[EMAIL PROTECTED]' forbidden_posters = [] As you can see, the config_list script adds one extra backslash before the dot, so the regexp is not correct, I don't figure how to solve it and I don't know why it happens. -Mensaje original- De: Mark Sapiro [mailto:[EMAIL PROTECTED] Enviado el: lunes, 16 de mayo de 2005 17:38 Para: Miguel Tarazona Belenguer; mailman-users@python.org Asunto: Re: [Mailman-Users] Allow a domain to post to a list Miguel Tarazona Belenguer wrote: This is my config file: ... = [] posters = ['@my.uni.es'] ... And I want to allow all members of the domain my.uni.es to post to the list but I don't fint the correct syntax to do this (if it can be done) This is an old version of Mailman. Those attributes don't exist in current versions, but assuming that current syntax might apply here, try posters = ['[EMAIL PROTECTED]'] This assumes that a regular expression is allowed in the 'posters' list and an initial '^' signals a regular expression. In current Mailman, this would be 'accept_these_nonmembers' and the above syntax would work. -- 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] Mailman user interface
At 3:26 PM +0200 2005-05-17, Jean-Philippe GIOLA wrote: I would like to know if someone of you have heard of a possible mailman web user interface that could allow you to reply directly at a post (like a forum for example). Before asking questions like this, you should search the Mailman FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py. Question 1.26 has some relevant info. Oh, and be sure you also read 1.22 and 1.23. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] Mailman Bug?/no Admin level web access
May 10th was the day I put in the new hard drive after the old one died. So basically I did a clean install. I had set up the domain/host stuff on the old drive so all I did was reinstall. I only have one domain/host name, and SELinux is on, but not on the snmpd daemon. My firewall is technically on, but since I'm trying to debug, it's set to allow everything. The admin interface never worked since May 10th. It did work on the old drive, but I had the last build of mailman then. There was nothing in /var/log/messages except the usual service starts and stops. Elissa - -- Message: 3 Date: Tue, 17 May 2005 14:46:36 +0900 From: Jim Tittsler [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Mailman Bug?/no Admin level web access To: [EMAIL PROTECTED] Cc: Mailman-users list mailman-users@python.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 17, 2005, at 11:25, [EMAIL PROTECTED] wrote: In response to the question about checking permissions, yes, I've run it several times, and genaliases, check_db and anything else I thought might provide a clue. All checked out ok. Are you running with SELinux enabled? (Are there additional clues about the permission failures in /var/log/messages? If you start with SELinux disabled, is Mailman happy?) My mailman log shows nothing, hasn't been updated since May 10th, but [...] So, what changed on May 10th? :-) -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman -- Message: 4 Date: Mon, 16 May 2005 23:41:10 -0700 From: Scot Hacker [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Mailman Bug?/no Admin level web access To: mailman-users@python.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Elissa wrote: I'm hoping someone can help me fix this. I installed mailman, and couldn't figure out why the web interface didn't work. It seems I CAN access any of the pages, but the admin ones. I get a lovely message in the browser: Bug in Mailman version 2.1.6rc3 We're sorry, we hit a bug! Not sure what your environment is, but I've seen that message in a multi-domain cPanel environment, where you can set up a domain before it's actually living on that host (preparing to move in). You can get as far as creating a list, but when you go to access the admin pages, it fails with that message. As soon as the domain actually resolves to that host, the problem goes away. Scot -- -- 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] Mailman Bug?/no Admin level web access
On Tue, 2005-05-17 at 13:02 -0400, [EMAIL PROTECTED] wrote: May 10th was the day I put in the new hard drive after the old one died. So basically I did a clean install. I had set up the domain/host stuff on the old drive so all I did was reinstall. I only have one domain/host name, and SELinux is on, but not on the snmpd daemon. How did you reinstall? This is important to determine if the security labels were applied. SELinux's control of smtpd is not relevant, its the httpd (e.g. apache) policy that probably affecting you. (I assume when you say the admin interface is not working you mean web access to it). Did you look for avc messages in /var/log/messages? Did you look at /var/log/audit/audit.log? (may not be present) -- John Dennis [EMAIL PROTECTED] -- 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] Mailman Bug?/no Admin level web access
I''m guessing you mean permissions. I installed it exactly the same way as I had in the previous install, with cgi-gid under apache- which is the same as httpd. I have the SELinux disabled for httpd. None of this would explain why the rest of the scripts work except for admin and admindb. They did work in version 2.1.5, but not in the current version I have (2.1.6rc3). As I already stated, nothing is showing up in any logs for those scripts except in the apache log and I posted that yesterday. I trashed the old mailman error log. I now have a new 0k file called error. I can send invites, etc using mailman so I know it's working as expected. Elissa -Original Message- From: John Dennis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: mailman-users@python.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tue, 17 May 2005 13:23:47 -0400 Subject: Re: [Mailman-Users] Mailman Bug?/no Admin level web access On Tue, 2005-05-17 at 13:02 -0400, [EMAIL PROTECTED] wrote: May 10th was the day I put in the new hard drive after the old one died. So basically I did a clean install. I had set up the domain/host stuff on the old drive so all I did was reinstall. I only have one domain/host name, and SELinux is on, but not on the snmpd daemon. How did you reinstall? This is important to determine if the security labels were applied. SELinux's control of smtpd is not relevant, its the httpd (e.g. apache) policy that probably affecting you. (I assume when you say the admin interface is not working you mean web access to it). Did you look for avc messages in /var/log/messages? Did you look at /var/log/audit/audit.log? (may not be present) -- John Dennis [EMAIL PROTECTED] -- 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 2.1.5, please help
Alias Mohd FKE wrote: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/local/mailman/scripts/driver, line 87, in run_main main() File /usr/local/mailman/Mailman/Cgi/create.py, line 55, in main process_request(doc, cgidata) File /usr/local/mailman/Mailman/Cgi/create.py, line 226, in process_request sys.modules[modname].create(mlist, cgi=1) File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create _update_maps() File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) You are creating a new list via the web. You have specified Postfix as your MTA so the last part of the process tries to update /usr/local/mailman/data/aliases and run /usr/sbin/postalias to update /usr/local/mailman/data/aliases.db. It is failing - probably for lack of permission. Be sure that both /usr/local/mailman/data/aliases and /usr/local/mailman/data/aliases.db are in the mailman group and are group writeable. Unfortunately bin/check_perms doesn't check this completely. -- 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
[Mailman-Users] mailman.pid
I did a mondoarchive of my whole server to CDs today, and afterward noticed these: 1. On the server I backed up, Mailman was not running after backup. When I tried to restart it, I got a message about no mailman.pid and no Mailman list. I restored /var/lib/Mailman from a previous backup, and Mailman started and is running fine. 2. I also used today's backup CD to nuke another machine I have that makes it a clone of the primary. On reboot after the restore procedure, I also got messages about Mailman not running and no pid file. (As expected, since it is a clone of the first machine.) Can you imagine anything about the pid file that would get trashed during a backup procedure? I know this is a nonspecific question and maybe should be asked on the Mondo list, but I don't know much about the mailman.pid file so thought I'd ask about IT here. Thanks any thoughts on this! - John -- 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] Allow a domain to post to a list
Miguel Tarazona Belenguer wrote: The syntax does not work. I put the config directive in a file posters.config and when I aply the config this is the result: system:~/scripts/listas/mailman/config# cat posters.config posters='[EMAIL PROTECTED]' First of all, posters is a list of strings, not a string so that should be posters=['[EMAIL PROTECTED]'] system:~/scripts/listas/mailman/config# config_list -v -i posters.config testlist attribute posters changed system:~/scripts/listas/mailman/config# config_list -o - testlist | grep posters posters = '[EMAIL PROTECTED]' forbidden_posters = [] As you can see, the config_list script adds one extra backslash before the dot, so the regexp is not correct, I don't figure how to solve it and I don't know why it happens. It appears that config_list is escaping the '\' character by doubling it. If this still occurs after you make it a list, You can try setting posters using withlist. For example: $ bin/withlist -l testlist Loading list testlist (locked) The variable `m' is the testlist MailList instance m.posters=['[EMAIL PROTECTED]'] m.Save() - control-D Unlocking (but not saving) list: mailman Finalizing $ -- 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] Mailman Bug?/no Admin level web access
Elissa wrote: I trashed the old mailman error log. I now have a new 0k file called error. I can send invites, etc using mailman so I know it's working as expected. How did this file get created? Did Mailman create it? If so, then the question is why can Mailman create this file but not be allowed to write to it?. Would SELinux be the answer? Have you tried testing with SELinux turned completely off just to see if that helps? -- 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
[Mailman-Users] mailman holding non member emails before spam filter rules apply - fix?
Hello,
I have mailman set to hold non-member posts to email list. I also have
all lists setup to discard any message the has been tagged as spam by
spammassassin. I have tried filtering on the {spam?} subject line and
also on the x-spamcheck headers. Unfortunately the lists grab the
message as a non-member post before it identifies it as spam so most of
my held messages are spam messages. Is there a way to change the order
of this so it will discard the spam messages before it checks for
list-membership?
Thanks for any help.
Colby
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Colby Walsworth
System Administrator
National Center for Ecological Analysis and Synthesis
735 State St., Suite 300
Santa Barbara, CA 93101-5504
phone: (805) 892-2507, fax: (805) 892-2510
email:[EMAIL PROTECTED] http://www.nceas.ucsb.edu/~walswort
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Dream as if you'll live forever.
Live as if you'll die today.
--James Dean
--
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] mailman holding non member emails before spamfilter rules apply - fix?
Colby Walsworth wrote:
I have mailman set to hold non-member posts to email list. I also have
all lists setup to discard any message the has been tagged as spam by
spammassassin. I have tried filtering on the {spam?} subject line and
also on the x-spamcheck headers. Unfortunately the lists grab the
message as a non-member post before it identifies it as spam so most of
my held messages are spam messages. Is there a way to change the order
of this so it will discard the spam messages before it checks for
list-membership?
How are you checking Subject: and/or X-Spamcheck* headers? If you are
using header_filter_rules and have not modified the GLOBAL_PIPELINE or
set a pipeline attribute for the list, the header_filter_rules should
be checked before anything else. If this is the case, and the spam
isn't being handled according to your rule's action, maybe your rules
are not correctly constructed.
If you are using bounce_matching_headers, this is checked after list
membership and the various *_these_nonmembers tests, and it results an
a held message anyway, not a reject or discard.
bounce_matching_headers is called Legacy anti-spam filters because
it's only for compatibility with something from the past.
Note also that the entries for header_filter_rules and for
bounce_matching_headers don't have the same meaning. For example, an
entry of
subject: .*spam.*
in bounce_matching_headers means match the contents of the subject:
header against the regexp '.*spam.*' while the same entry in
header_filter_rules means match the entire message header string
against the regexp 'subject: .*spam.*'.
--
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] mailman holding non member emails before spam filter rules apply - fix?
At 5:16 PM -0700 2005-05-17, Colby Walsworth wrote: Is there a way to change the order of this so it will discard the spam messages before it checks for list-membership? Yeah, I'd like to see that, too. That's why I made my entry on the Mailman Request for Enhancements page. See http://sourceforge.net/tracker/index.php?func=detailaid=1073232group_id=103atid=350103 for the one I posted on this issue. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] Mailman Bug?/no Admin level web access
On Tue, 2005-05-17 at 21:33 -0400, [EMAIL PROTECTED] wrote: Mailman created a new file, but the others show as plain text and the new one as octet stream. I'm afraid I don't understand. What others and what do you mean the new log file is octet stream? Right now I'm at accept all on ports/firewall, with SELinux enabled and enforcing but turned off on the httpd daemon. I can access all of the pages except the Admin ones. Please turn ALL of SELinux off. There are many parts of the security policy that might come into play, not just httpd. For instance mailman has its own security policy that is mated to the red hat mailman rpm's, which you're not using, there is a tremendous opportunity here for problems due to the mismatch. Let's try to eliminate SELinux as a factor altogether. -- John Dennis [EMAIL PROTECTED] -- 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] erroneous tabs in long digest subject lines
Greetings. On digests automatically generated by the mailman system, I'm finding that long subject lines are having tabs inserted into them in unexpected ways in the topic summary, often related to commas. For example, on a message that had the subject line: Subject: this is a test of a longer, subject line, longer yet and which was formatted properly in the non-digest distribution of the message, the digest version looks like this: Today's Topics: 1. this is a test of a longer, subject line,longer yet ([EMAIL PROTECTED]) In this case, a tab has appeared between the comma and longer. Also, there are some inconsistencies in the way that Subjects folded onto a second line are indented in the topics summary (i.e., the second line of different subjects in the Today's Topic may not all be indented exactly the same amount), but the erroneous tab is a bigger problem and is the one I'd really like to nab, since it is significantly breaks the format and is happening so frequently. I've looked at the ToDigest and Utils.wrap routines and don't see an obvious cause. Any clues? Thanks very much. -- 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] erroneous tabs in long digest subject lines
Misc.wrote: Greetings. On digests automatically generated by the mailman system, I'm finding that long subject lines are having tabs inserted into them in unexpected ways in the topic summary, often related to commas. For example, on a message that had the subject line: Subject: this is a test of a longer, subject line, longer yet and which was formatted properly in the non-digest distribution of the message, the digest version looks like this: Today's Topics: 1. this is a test of a longer, subject line,longer yet ([EMAIL PROTECTED]) In this case, a tab has appeared between the comma and longer. Also, there are some inconsistencies in the way that Subjects folded onto a second line are indented in the topics summary (i.e., the second line of different subjects in the Today's Topic may not all be indented exactly the same amount), but the erroneous tab is a bigger problem and is the one I'd really like to nab, since it is significantly breaks the format and is happening so frequently. I've looked at the ToDigest and Utils.wrap routines and don't see an obvious cause. That's because Mailman isn't doing it. It's the MUA that composed the original message. The differences/discrepancies/whatever are the result of folding the Subject: header across multiple lines and an unclear standard covering how to do so. The old standard RFC 822 in section 3.1.1 said The general rule is that wherever there may be linear-white-space (NOT simply LWSP-chars), a CRLF immediately followed by AT LEAST one LWSP-char may instead be inserted. and The process of moving from this folded multiple-line representation of a header field to its single line representation is called unfolding. Unfolding is accomplished by regarding CRLF immediately followed by a LWSP-char as equivalent to the LWSP-char. This seems to say that extra indentation can be inserted when folding, but not removed when unfolding. The current RFC 2822 section 2.2.3 is more clear. It says in part, The general rule is that wherever this standard allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP. Thus some MUAs based on RFC 822 insert multiple spaces or a tab when creating a folded subject line and software such as Mailman following either standard doesn't remove them. -- 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
