[Mailman-Users] Message of large size, only the owner of the list may authorize
Is there any easy way to get Mailman messages of large size, only the owner of the list may authorize? And only the smallest message moderator can approve them? I'm really getting tired of dealing with those very large messages that are released by the moderator. -- Fábio -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Message of large size, only the owner of the list may authorize
At Mon, 1 Sep 2014 15:32:04 -0300 Fabio Eckhardt fabioeckha...@universo.univates.br wrote: âIs there any easy way to get Mailman messages of large size, only the owner of the list may authorize? And only the smallest message moderator can approve them? I'm really getting tired of dealing with those very large messages that are released by the moderator.â There isn't really a 'privilege separation' at that level. The solution is to talk to the moderator about not releasing very large messages and/or communication with the people posting very large messages or even both. -- Robert Heller -- 978-544-6933 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Message of large size, only the owner of the list may authorize
Fabio Eckhardt writes: Is there any easy way to get Mailman messages of large size, only the owner of the list may authorize? And only the smallest message moderator can approve them? I'm really getting tired of dealing with those very large messages that are released by the moderator. If you know what the MIME type(s) or filename extension(s) of the offending attachments are, you can have Mailman remove them in the Content Filtering screen. If you really want some but not all large messages to pass, I think you should get a better moderator, the list owner if necessary. Consider: the list owner is going to have to check regularly anyway. Unless your list gets an awful lot of spam, checking once a day only takes a few minutes, less than dealing with those very large messages that the moderator should never have released. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman is being a processor sponge.... very slow delivery...
Thanks So much Stephen, I just wanted make sure I got this in writing. And document what I had to do to fix the loop you found (more savy folks may have done it faster) I tried to use a text editor, but of course it did not (could not lock the file) Tried to create the change_owner script and use withlist, as advised be Mark Shapiro, but would not run Change_owner module not loaded... but that is what I was telling it to load. So I got a wild hair. I stopped mailman service. I could then go into the mailman list UI. I changed the owner to a physical account. Restarted mailman.. Qrunner was still pegged at 99% Stopped it again. Went into the UI again (had to wait a minute for the qrunner to spin down) went to tend to moderated items Checked discard all messages marked defer Restarted Mailman is no longer absorbent Thanks Again! Morgan -Original Message- From: Stephen J. Turnbull [mailto:step...@xemacs.org] Sent: Tuesday, September 02, 2014 7:43 AM To: Ecklund, Morgan Subject: RE: [Mailman-Users] Mailman is being a processor sponge very slow delivery... Ecklund, Morgan writes: I am pretty sure it has been hacked. It looks normal to me. Can you look at the the dumpdb of the mailman list. relay.comanche.denmark.eu\nfrom: Just seems out of place. No, it's just a very very old default that hasn't been changed. Back in the late 1990s (!!!) the headers indicated by 'bounce_matching_headers': \n# Lines that *start* with a '#' are comments.\nto: fri...@public.com\nmessage-id: relay.comanche.denmark.eu\nfrom: l...@listme.com\nfrom: .*@uplinkpro.com\n, ie, # Lines that *start* with a '#' are comments. to: fri...@public.com message-id: relay.comanche.denmark.eu from: l...@listme.com from: .*@uplinkpro.com were famous for reliably indicating spam. The example regexps haven't been changed since then, that's all. Aha! This variable 'owner': [ 'mail...@list.education.state.vt.us', 'list-ad...@education.state.vt.us'], is probably your immediate problem. It's OK for a list's owner email to be another list, but it should not be itself. It's very likely to cause a loop where a post causes an error, which cause an error message to go to owner, which is the list, but that causes another error, and this repeats ad infinitum as fast as your CPU and disks can handle it. It's almost as likely to loop if mailman@ is the owner of @list-admin and vice-versa, so don't do that either. At least one of your lists needs to have all its owner addresses be regular mailboxes. The way I set it up at XEmacs.org is that all lists (including mail...@xemacs.org) have owner xemacs-servi...@xemacs.org (which is also the real webmaster etc), except that xemacs-services itself is owned by me and a couple of other volunteers. The owner list for that list is maintained by hand. Yes, you'd think that it would be easy to recognize such a mail loop and Mailman would just stop looping, and indeed humans can. But it turns out to be really hard to do automatically, since by definition when an error message is generated to owner the system is in some bizarre state. Everything else looks fine to me. If you take mailman@ out of the owners' address list, it should stop the loop, and take a big load off the CPU and disks. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] .psv files in /var/spool/mailman/in 2.1.9
On 08/19/2014 02:27 PM, Will Yardley wrote: I found some .psv files in /var/spool/mailman/in/ (RHEL 5 Mailman package; 2.1.9). That seems to be too early for the stuff mentioned here (and I don't see those options in Defaults.py) https://mail.python.org/pipermail/mailman-users/2009-June/066395.html Correct. Mailman 2.1.9 doesn't write .psv files ayt all and those versions that do only put them (in the RHEL package) in /var/spool/mailman/bad/. So where those files came form, I can't say. Is it safe to remove old .psv files in this directory directly via find / cron? If you just rm /var/spool/mailman/in/*.psv one time, that should get rid of them and there should be no new ones, but for curiousity, you might run Mailman's bin/show_qfiles /var/spool/mailman/in/*.psv first to see what's in them, although this may just throw the same exceptions that caused them to be preserved in the first place. In any case, yes, it is safe to remove them as Mailman never looks at them. Note: if new ones appear, see the FAQ at http://wiki.list.org/x/OIDD and ask RedHat. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] List suddenly stopped adding footers.
Kevin T. Likes writes: I have a user-managed list that suddenly stopped adding the footer to messages. It appears that after the time footers stopped being added, I started seeing links for scrubbed attachments to messages. The footer is set in the Non-digest Settings screen. It's theoretically possible that scrubbing attachments could interfere with adding the footer, or perhaps for some reason it is being added outside of the MIME structure and your mail client doesn't display it (this is proper behavior for the client, but given the complexity of MIME I am reluctant to call it a bug in Mailman). If your client has a show original function to show the message without any formatting, you can check for this condition by using show original and scrolling to the bottom. Scrubbing is configured in the Content Filtering screen. You can scrub by MIME type or by filename extension. There is a standard list of things to scrub (.com, .bat, .exe, ...) because of the high probability that such attachments are malicious Check for changes in those settings. What does the user-manager say? If the user-manager isn't being helpful, I would hesitate to trust them with list management in the first place. YMMV, of course. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moderator Passwords
At 08:37 PM 9/1/2014, Stephen J. Turnbull wrote: David Andrews writes: Then it never seems to work for them -- I end up changing password several times until it eventually seems to take. It's not a matter of taking. If you type the same password twice, and get a page saying password is set, the password has already been recorded. The password database is internal to Mailman, and the system has been in use for nearly two decades with few problem reports (except that it is *too* easy to use, and consequently insecure), so we are very confident that it works as designed. Well I must sheepishly admit it was my error. I apologize for taking everybody's time. I was giving the Moderator the wrong URL to get into his list. Dave David Andrews and long white cane Harry. E-Mail: dandr...@visi.com or david.andr...@nfbnet.org -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moderator Passwords
David Andrews writes: I apologize for taking everybody's time. Apology graciously accepted, but really, none needed. Password management is at best annoying, and to do it *really* well, hard. Mailman is a complex product. I'm glad that the assurance that it shouldn't be *that* hard was enough for you to find and fix the issue yourself! Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moderated list, letting some users be unmoderated, and with emails addressed to multiple recipients.
On 08/25/2014 12:12 PM, Steve wrote: I'm a moderator on a GNU Mailman list running version 2.1.13. http://www.gnu.org/software/mailman/index.html The list moderated, all posts come to me for approval. I have a few very trustworthy and regular posters that I have set as unmoderated to save myself some work. The problem is that they send their emails to multiple lists/recipients and when they do I am still forced to approve their posts. Why are the posts held. Is it because of too many recipients? Is there an option in the GUI front end I can set on these users to let their posts straight through regardless? See Privacy options... - Recipient filters - max_num_recipients -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
