[Mailman-Users] Changing the name of a mailing list
If I have a list called n...@domain.com and I want to change it to something else, say names...@domain.com - is there a relatively easy way to do this for someone not versed in the server side of managing the mailman install? Thanks, as always, in advance Brian -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Changing the name of a mailing list
Brian Luria wrote: If I have a list called n...@domain.com and I want to change it to something else, say names...@domain.com - is there a relatively easy way to do this for someone not versed in the server side of managing the mailman install? The various ways to rename a list are described in the FAQ at http://wiki.list.org/x/mYA9. The only way to truly rename the list (i.e. change its name while preserving list membership and all member options) requires renaming several files and directories in Mailman's file structure and possibly modifying the MTAs aliases. This and other methods are described in the FAQ. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Emergency Moderate question
I am running v2.1.13 on Mac OS X Server 10.5.8; all works well, I have many lists running with virtual hosts for several organizations. I noticed a strange behavior recently. One list was set to Emergency Moderate all traffic. For this one list, I (as administrator) did not receive the customary notification of held e-mails until the following day, when the daily reminder message would notify me that the message was still waiting to be approved/denied. Turning off Emergency Moderate restored behavior to normal, and I now receive immediate notification of held posts. All other lists work fine with respect to moderated / held messages, none of them have 'Emergency Moderate' on. I am trying to understand this behavior and was curious if anyone had any thoughts. Thanks, -Rob -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Emergency Moderate question
Rob wrote: I noticed a strange behavior recently. One list was set to Emergency Moderate all traffic. For this one list, I (as administrator) did not receive the customary notification of held e-mails until the following day, when the daily reminder message would notify me that the message was still waiting to be approved/denied. That's how it's designed to work. Emergency moderation is designed to be used to moderate all traffic in emergencies such as to quell flame wars. It is not intended to be used routinely to moderate all posts. Thus, when emergency moderation is on, posts which are not held for some other reason are held for emergency moderation and the owner/moderator is not notified even if admin_immed_notify is yes. Turning off Emergency Moderate restored behavior to normal, and I now receive immediate notification of held posts. Unless there is an Apple mod in the order of the pipeline, you should have received notices of posts held for other than emergency moderation anyway. The only held posts that you would not receive notice for are those specifically held for emergency moderation. All other lists work fine with respect to moderated / held messages, none of them have 'Emergency Moderate' on. I am trying to understand this behavior and was curious if anyone had any thoughts. If you want to routinely hold all posts, the way to do that is to set all member's 'mod' flags on and set new members moderated by default. Under normal circumstannces, emergency moderation should be off. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Emergency Moderate question
On Tue, 01 Feb 2011 21:05:31 -, Rob penng...@mac.com wrote: I am trying to understand this behavior and was curious if anyone had any thoughts. I saw exactly the same behaviour a month or two back, then I read the manual that confirmed this is as intended - to avoid the moderator getting floods of email during emergency moderation. Malcolm. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Emergency Moderate question
On Feb 1, 2011, at 4:28 PM, Mark Sapiro wrote: Rob wrote: I noticed a strange behavior recently. One list was set to Emergency Moderate all traffic. For this one list, I (as administrator) did not receive the customary notification of held e-mails until the following day, when the daily reminder message would notify me that the message was still waiting to be approved/denied. That's how it's designed to work. Emergency moderation is designed to be used to moderate all traffic in emergencies such as to quell flame wars. It is not intended to be used routinely to moderate all posts. Thus, when emergency moderation is on, posts which are not held for some other reason are held for emergency moderation and the owner/moderator is not notified even if admin_immed_notify is yes. Turning off Emergency Moderate restored behavior to normal, and I now receive immediate notification of held posts. Unless there is an Apple mod in the order of the pipeline, you should have received notices of posts held for other than emergency moderation anyway. The only held posts that you would not receive notice for are those specifically held for emergency moderation. All other lists work fine with respect to moderated / held messages, none of them have 'Emergency Moderate' on. I am trying to understand this behavior and was curious if anyone had any thoughts. If you want to routinely hold all posts, the way to do that is to set all member's 'mod' flags on and set new members moderated by default. Under normal circumstannces, emergency moderation should be off. Thanks, that is what I normally do, and is how I have the list set up now. So, if I do use Emergency moderate in the future, would I just check the pending requests page manually to see if posts have arrived? -Rob -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Emergency Moderate question
Rob wrote: So, if I do use Emergency moderate in the future, would I just check the pending requests page manually to see if posts have arrived? If you wanted to know what was waiting moderation before receiving your daily notice, yes. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Administrivia Messages
Beau Barnhart wrote:
We have been asked by mail-abuse.org to make changes to the configuration
to one of our servers. The following this their request...
Actually, the request understates the problem. See below.
-- message from mail-abuse.org --
Currently, when messages arrive at your mail server it runs them through
SpamAssassin, which checks for spam and tags them. Your mail server then
passes this tagged message to mailman.
Because it is to a -request address, mailman knows that these messages
should contain commands. It ignores the fact that SpamAssassin has
already tagged it (Subject: {Definitely Spam?}), and looks through every
line looking for a subscribe, unsubscribe or other command.
Of course, it doesn't find one. So, it builds up a helpful reply, sets
the X-Administrivia header to yes, and appends the original message, and
forwards this to the From: address.
Except that the From: address is forged, so the message, and its spam
payload, get sent to an innocent third party.
And, this would occur even if spamassassin/MailScanner/whatever didn't
tag the subject. In fact, if the message is truly spam with a forged
From:, the likelyhood that the subject contained a valid command
before tagging is small. And even if it did contain a valid command,
there is normally some reply from Mailman to the (forged) sender in
any case.
This backscatter problem is well known, and it is a serious issue.
Mailman 3 will address this to some degree.
Please properly configure your mailing list software to send list
administrivia _only_ to a local administrator, or configure it not to send
to forged From: addresses. In general, there is no need for list
administrivia - it was an artifact of some of the original list
management software. It does not serve a useful purpose today.
Actually we use administrivia in custom scripts and don't want to disable
it. We even have members that still use the request commands.
I've searched the mailman wiki as well as the mailman-users archive and
have not been able to find how to configure the administrivia recipient.
Any help would be appreciated.
There's not much you can do in Mailman 2.1.x, at least as far as
configuration options go. You can disable the administrative
addresses, but you say you don't want to do that. Changing the
disposition of replies or their content requires code modification.
I really should implement a site option to not include original message
content in auto responses. I meant to do it before now, but haven't.
Maybe I can get to it for 2.1.15.
For more on this issue, see the thread before next release: disable
backscatter in default installation beginning at
http://mail.python.org/pipermail/mailman-developers/2008-March/019804.html.
One thing you can do is configure your MTA to not accept likely spam at
SMTP time or simply discard (not reject) it if it was already
accepted, or maybe do this only for Mailman recipient addresses if you
don't want to do it universally. If you use MailScanner, it shouldn't
be too difficult to concoct an appropriate rule set for this.
--
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
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Cannot exec /etc/mail/smrsh: Permission denied
John Espiro wrote: When I send a message to the mailing list I get: sm-mta[16327]: p0SJuInx016321: SYSERR(root): Cannot exec /etc/mail/smrsh: Permission denied Jan 28 19:56:22 sm-mta[16326]: p0SJuInx016321: to=|/usr/lib/mailman/mail/mailman post LISTNAME, ctladdr=ADDRESS (8/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=31689, dsn=4.0.0, stat=Operating system error System: Ubuntu 10.10 Server 64bit I've read through this: http://www.gnu.org/software/mailman/mailman-install/node32.html grep smrsh /etc/mail/sendmail.cf # $Id: smrsh.m4,v 8.14 1999/11/18 05:06:23 ca Exp $ # Mprog, P=/etc/mail/smrsh, F=lsDFM smrsh is in: :/usr/lib/sm.bin In /usr/lib/sm.bin, I ran: ln -s /usr/lib/mailman/mail/mailman mailman In /etc/mail/smrsh, I ran: ln -s /usr/lib/mailman/mail/mailman mailman Still, the problem persists. I am sure this must be a permissions issue, then again, maybe not. Other data: uid=51(smmsp) gid=51(smmsp) groups=51(smmsp),45(sasl) uid=103(smmta) gid=106(smmta) groups=106(smmta),45(sasl) uid=8(mail) gid=8(mail) groups=8(mail) ls -la /etc/mail/smrsh drwsr-sr-x 2 root root 4096 2011-01-28 19:31 . What are the permissions on /usr/lib/mailman/mail/mailman? are all directories world searchable and the file world executable? -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
