[Mailman-Users] Major admin problems
Hi all, I am new to this list. I have been using Mailman 2.0.13 for over a year to deliver a mailing list to about 1200 subscribers. Something has gone wrong and I don't know enough about Linux to fix it, so I am hoping someone would be willing to give me a hand. Here are the symptoms.. 1. Regular mail is not being delivered. 2. Digests are being delivered. 3. Any message sent to the list address doesn't seem to bounce, but it doesn't go out to regular subscribers Digest users do get the messages. 4. The archives have disappeared. There are no files in the archive directories, but it takes time to get a ls -al from that directory. The systems admin who is NOT a unix expert thinks the drive is seriously corrupted. So, I need to pull off the subscriber list and rebuild the drive. It is configured with Linux SuSe which has a nice webmin browser interface that I have been able to use to administrate certain things. This has been helpful for me since I don't know much unix. Can anyone help me? I am in the process of moving everyone over to digest mode so that I can send them all a message explaining the problem.. Is there a way to do that easily? Right now I am going through all the screens in the Membership Management area clicking digest on every name. Its taking forever.. Is there an easier, more global way? Thanks in advance for all the help. Michael Anderson http://tpin.okcu.org - Trumpet Players' International Network. -- 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=show&file=faq01.027.htp
[Mailman-Users] content filtering not working as expected
I have a 2.1.5 installation, and one list is using the following content_filter options: filter_content = True filter_mime_types = '' pass_mime_types = """multipart text application/pgp-signature application/pdf""" convert_html_to_plaintext = True filter_action = 1 # reject We just received a message with a application/octet_stream attachment. My interpretation of the settings are that the message should have been rejected. However, the message merely got filtered, the attachment was stripped, and the message passed through without an attachment. Is this a bug or expected behaviour? -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [EMAIL PROTECTED] "sometimes the urge to do bad is nearly overpowering" -- ben horne signature.asc Description: 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=show&file=faq01.027.htp
Re: [Mailman-Users] content filtering not working as expected
martin f krafft wrote: > >I have a 2.1.5 installation, and one list is using the following >content_filter options: > > filter_content = True > filter_mime_types = '' > > pass_mime_types = """multipart > text > application/pgp-signature > application/pdf""" > > convert_html_to_plaintext = True > filter_action = 1 # reject > >We just received a message with a application/octet_stream >attachment. My interpretation of the settings are that the message >should have been rejected. However, the message merely got >filtered, the attachment was stripped, and the message passed >through without an attachment. > >Is this a bug or expected behaviour? This is expected. filter_action is only taken when nothing remains after filtering. The following text is on the Details for filter_action page. One of these actions is take when the message matches one of the content filtering rules, meaning, the top-level content type matches one of the filter_mime_types, or the top-level content type does not match one of the pass_mime_types, or if after filtering the subparts of the message, the message ends up empty. Note this action is not taken if after filtering the message still contains content. In that case the message is always forwarded on to the list membership. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] content filtering not working as expected
also sprach Mark Sapiro <[EMAIL PROTECTED]> [2005.03.19.2301 +0100]: > Note this action is not taken if after filtering the message still > contains content. In that case the message is always forwarded on to > the list membership. Sorry for not seeing this. Now I wonder if it's possible to somehow make Mailman reject posts with unwanted attachment types... is it? If so, how? -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [EMAIL PROTECTED] the heineken uncertainty principle: you can never be sure how many beers you had last night. signature.asc Description: 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=show&file=faq01.027.htp
[Mailman-Users] Re: Getting Mailman to work
Mark Sapiro <[EMAIL PROTECTED]> wrote: > It looks to me like a Postfix configuration problem, i.e. Mailman is > sending the mail as it should and Postfix is not accepting it because > it doesn't like the sender <[EMAIL PROTECTED]>. Shouldn't that be <[EMAIL PROTECTED]> (as per rfc2821, 4.1.3)? Zoran -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] content filtering not working as expected
martin f krafft wrote: > >Sorry for not seeing this. Now I wonder if it's possible to somehow >make Mailman reject posts with unwanted attachment types... is it? >If so, how? Beginning in 2.1.6, Privacy options...->Spam filters->header_filter_rules will match sub-part headers allowing you to match things like content-type of subparts, attachment file name extensions, etc. and specify Hold, Reject, Discard or Accept for messages that match. See http://mail.python.org/pipermail/mailman-users/2005-February/042372.html although note that that post has a link to 2.1.6b2 and the current is 2.1.6b4 on sourceforge.net. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Re: Getting Mailman to work
On 3/19/2005 16:16, "Zoran Dzelajlija" <[EMAIL PROTECTED]> wrote: > Mark Sapiro <[EMAIL PROTECTED]> wrote: >> It looks to me like a Postfix configuration problem, i.e. Mailman is >> sending the mail as it should and Postfix is not accepting it because >> it doesn't like the sender <[EMAIL PROTECTED]>. > > Shouldn't that be <[EMAIL PROTECTED]> (as per rfc2821, 4.1.3)? > Indeed. Thanks to 3Com and friends, 64.40.10.147, which was once syntactically invalid, is now simply a syntactically correct FQDN which doesn't have a host to be the name of (there is no 147 top level domain). To be a IP literal, the IP indeed needs to be inside a bracket pair (as it long has...well before 3Com caused domain names to be much harder to recognize than they should be). Postfix is configured "correctly" by some definition of correct. The sending entity needs to get it right. If mailman is generating the <[EMAIL PROTECTED]>, Mailman is incorrect. --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=show&file=faq01.027.htp
Re: [Mailman-Users] Major admin problems
On Mar 20, 2005, at 03:17, Michael Anderson wrote: 1. Regular mail is not being delivered. Are you sure the qrunner is being invoked by cron every minute? Are there no clues in the logs/* files? Or in your mail server's logs? Are the messages still in the qfiles/ directory? The systems admin who is NOT a unix expert thinks the drive is seriously corrupted. So, I need to pull off the subscriber list and rebuild the drive. If you save the contents of the ~mailman/lists directory you will be able to recreate your lists using them. (You will also want to backup your ~mailman/archives directories (if you find out why the files have gone missing) and things like any customizations you've made in mm_cfg.py.) Can anyone help me? I am in the process of moving everyone over to digest mode so that I can send them all a message explaining the problem.. Is there a way to do that easily? Right now I am going through all the screens in the Membership Management area clicking digest on every name. Its taking forever.. Is there an easier, more global way? If you have shell access, you can use ~mailman/bin/withlist to set everyone to digest mode: 1. Create ~mailman/bin/alldigest.py containing: ### alldigest.py def alldigest(m): for member in m.GetMembers(): print member m.SetUserDigest(member, 1) m.Save() ### alldigest.py 2. Run it with the 'withlist' framework on your list ./withlist -l -r alldigest yourlistname If you don't have shell access, you can write a script that acts like a (fast) web browser. Some Mailman 2.1.x-oriented examples are at http://starship.python.net/crew/jwt/mailman/#throughtheweb It would be better to solve the real problem. And/or upgrade to 2.1.x. But if you do choose to proceed with the "set everyone to digest mode" method, backup the list first so that when the problem is eventually solved, you will have a record of who really wanted digest mode. -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html -- 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=show&file=faq01.027.htp
