[Mailman-Users] Problem creating mailing lists via web interface in 2.1.11
It works just fine if I log in as root and use newlist, but if I try to create a new list via the web admin interface, two things happen. First, I get an error, whose text I do not have in front of me (I know, I know, first rule of error reporting, report the exact error, but you probably won't need it when I finish my explanation), and second, the aliases file is not updated, so if a subscriber tries to send a message to the list, they receive an auto-reply telling them user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? Is this a bug or a feature, or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? Thanks in advance. -- 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] Problem creating mailing lists via web interface in 2.1.11
The MTA is postfix. The file in question is /var/lib/mailman/data/aliases which, according to what I've read, is created from aliases.db. The interesting thing is, virtual-mailman *is* updated correctly from virtual-mailman.db while aliases is not. Mailman was installed long before I got here, but I'm assuming it was installed via the standard package installer when Ubuntu was originally built a few years ago. I also recognize I'm not running the latest Ubuntu or Mailman. Here's the perms on those four files: -rw-rw 1 root list 6725 2012-03-28 19:07 aliases -rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db -rw-rw 1 root list 5830 2012-03-28 19:07 virtual-mailman -rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db On Thu, 29 Mar 2012 01:52:45 +0900, you wrote: On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote: user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? What aliases file? Exim, for example, doesn't need one at all. There are many MTAs, there are many different ways to configure them to deliver to lists. Is this a bug or a feature, It's a missing feature in your MTA. :-) As I wrote, there are MTAs that can be configured to automatically deliver to mailing lists (eg, Exim is told to look for a $LIST.cfg file, and if that is found, it delivers to | mailman post $LIST or something like that). or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? We likely can help you, but you'll need to tell us exactly what MTA you use, and how it's currently configured. If you are using a OS-distro-provided Mailman, tell us what distro and the full version number of the Mailman package. If you built from source, tell us that. -- 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] Problem creating mailing lists via webinterface in2.1.11
It would *never* be in my best interest not to give you all the info. The problem is, I don't know exactly what info you need or want, and what would be superfluous. Let's see if I can provide more below. Anything I've omitted, just ask and it shall be yours for the knowing. On Wed, 28 Mar 2012 12:28:27 -0700, you wrote: Mark Sapiro wrote: Steve Matzura wrote: and second, the aliases file is not updated, so if a subscriber tries to send a message to the list, they receive an auto-reply telling them user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? Is this a bug or a feature, or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? If bin/newlist updates the aliases, web create should too, so clearly this has something to do with the error. If the list is created and the only problem is that aliases aren't updated, it could be a permissions issue. Is Mailman's cgi-bin/create wrapper group 'mailman' and SETGID and does group 'mailman' have write permission on the aliases? In case it went by and you didn't see it, here are the perms on those four files in /var/lib/mailman/data: -rw-rw 1 root list 6725 2012-03-28 19:07 aliases -rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db -rw-rw 1 root list 5830 2012-03-28 19:07 virtual-mailman -rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db Also, the user unknown in virtual mailbox table error indicates the list domain is a virtual domain. If the issue is that Mailman's data/aliases is updated, but data/virtual-mailman is not, the problem is that the email host_name for the list is not in POSTFIX_STYLE_VIRTUAL_DOMAINS. For a web create, the host_name is determined by taking the web host from the URL used to go to the create page and looking it up in the VIRTUAL_HOSTS dictionary That would be www.theglobalvoice.info with the additional mailman suffix string, of course. I tried putting add_virtualhost in mm_cfg.py, but all that did was generate an error saying I'd found a bug! Obviously that was the wrong thing to do, so I removed it, and now we're back to the unknown virtual host error on the web create form. (basically your add_virtualhost entries) and getting the host name from there. But, as Stephen suggests, don't make us guess. Give us all the information. -- 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] Problem creating mailing lists via webinterface in 2.1.11
On Wed, 28 Mar 2012 12:46:48 -0700, you wrote: You need to 'chmod 660 /var/lib/mailman/data/virtual-mailman.db' It must be writable by the 'list group or it can't be updated by the web server running the create CGI. I did that and am still receiving the unknown virtual host error when creating the list from the Web interface. -- 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] Problem creating mailing lists via webinterface in2.1.11
On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote: On Wed, 28 Mar 2012, Steve Matzura wrote: It would *never* be in my best interest not to give you all the info. The problem is, I don't know exactly what info you need or want, and what would be superfluous. Let's see if I can provide more below. Anything I've omitted, just ask and it shall be yours for the knowing. How about the error message you get when you try to create a list via the web interface. The one that you assumed we would somehow all know without you telling us (having never had an error when creating a list or if I did, not in recent years, I haven't the slightest clue what sort of error message you might have recieved). It seems rather likely that the error you received dealt with alias creation which you seem to want to think of as a second unrelated problem. Error already reported in a previous message, but here's the Reader's Digest version. After going through the process of creating a new list via the Web interface, the error message unknown virtual host is given, and no mailing list is created. I'd strongly suggest you start over and provide all relevant information in one post so we don't have to go through several messages to find the information you've dribbled out to us in multiple messages. What's relevant? As previously stated, if I knew all the info to provide, I would have done so in the first place. I've since provided everything I know about what's going on when I try to create a list. The real problem here is, I know just enough about Mailman to be dangerous, so before I get dangerous and break something even further than it's already broken, I ask questions. If I provide insufficient information for you to help solve my problem, it's totally and completely unintentional. The expression I don't know what I don't know comes to mind. -- 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] Problem creating mailing lists via webinterface in2.1.11
I've obviously bunged this up badly. Now here it is, all correct and properly assigned to each half of the problem: When creating the list ad...@theglobalvoice.info, unknown virtual host is the error, but some way, somehow, the list gets partially created. If I send a message to that partially created list, Mailman sends back a message of undeliverability with this error text: Remote host said: 550 5.1.1 ad...@theglobalvoice.info: Recipient address rejected: User unknown in virtual mailbox table I looked in postfix.cf and discovered the virtual host name is really patronus.theglobalvoice.info, which may have something to do with why the Web create doesn't work, but 'newlist' does. On Wed, 28 Mar 2012 18:19:29 -0500, you wrote: On Mar 28, 2012, at 4:40 PM, Steve Matzura wrote: On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote: How about the error message you get when you try to create a list via the web interface. The one that you assumed we would somehow all know without you telling us (having never had an error when creating a list or if I did, not in recent years, I haven't the slightest clue what sort of error message you might have recieved). It seems rather likely that the error you received dealt with alias creation which you seem to want to think of as a second unrelated problem. Error already reported in a previous message, but here's the Reader's Digest version. After going through the process of creating a new list via the Web interface, the error message unknown virtual host is given, and no mailing list is created. Just to show you how confused this became, I thought unknown virtual host was the error being returned to someone trying to post. I do not recall you ever saying that was the error the web interface was returning. -- 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] Problem creating mailing lists via webinterface in2.1.11
On Wed, 28 Mar 2012 19:37:42 -0700, you wrote:
Did I forget to check or report on anything?
Well, you never answered the questions I asked at
http://mail.python.org/pipermail/mailman-users/2012-March/073113.html
so we don't know what was wrong there, but presumably, you don't care
as you reversed whatever you did and it's working now.
Actually, I didn't reverse anything. You asked:
So what add_virtualhost() did you put in mm_cfg.py?
I actually tried, and backed out, two things before coming for help to
this list, both of which made things worse! I tried
add_virtualhost('www.theglobalvoice.info', 'www.theglobalvoice.info'),
and the same line without the www.. Adding this line gave me the
You hit a bug message in the Web create UI, which is why I backed it
out and set things back the way they'd been.
Regarding:
What is in Mailman's error log corresponding to the we hit a bug?
I don't know because I don't know enough about Mailman to have even
had a chance to look. There's one thing about all of this you don't
know because I haven't mentioned it, and it goes back to when I said I
don't even know what I don't know. While I've been tasked to keeping
theglobalvoice.info running, my only credentials for doing so are that
I'm reasonably good at learning quickly--I am not a *ux system or site
administrator of any stripe. Ask me lots of questions about VAX/Alpha
VMS and I can talk your ear off, as that's what I've spent the last 30
years doing professionally. Show me a *ux system prompt and the first
thing I know to do is man {something}, and if that doesn't solve
whatever is wrong, I start Googling until I find something to at least
try. I'd gotten to that point and figured out it probably had
something to do with add_virtualhost, but not understanding (until
now) exactly what that directive does, I was floundering. Apparently
my predecessor, someone actually far more qualified to do this job
than I, either didn't know about the proper use of add_virtualhost, or
was happy enough with using the command-line `newlist' to create new
mailing lists, because there are eight of them already on the system
running successfully. The site owner told me that she always knew
there was a problem with the Web UI, but the previous techie guy had a
workaround for it--namely, using `newlist' as root. I, being the type
who doesn't like loose ends or unsolved mysteries, stuck my neck out
and said I'd fix it ... and you know the rest.
--
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] Install from repository, or build from source?
I am a site admin for a system built on Debian version 7 (Wheezy). The current available mailman package distribution version is 2.1.15 but I want to use 2.1.18-1, which means, unless I miss my guess, it's got to be built from source. If this isn't so, I'd greatly appreciate knowing where and how to obtain the installable package. I've tried including the version number, etc., in apt-get, but as of right now,k no go. Thanks in advance. -- 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] Moving Configurations and Lists to a New Server
Thanks to Steve Turnbull's help and some intelligent manual-reading, I have successfully built and installed version 2.1.18-1 on a Debian 7 (Wheezy) system. check_perms reports no problems, `version' reports the right version number, I'm ready for the next step, which is to move an entire configuration and mail spool from an old Debian 5+Mailman 2.1.11 server. I imagine the spool (/var) files can just be tar'd and moved en masse. But what about mailman configuration files--mailing list info, that sort of thing? What should be moved, what should be re-created, etc.? -- 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] Moving Configurations and Lists to a New Server
This reply mechanism is driving me a little weird--the reply function sends the messages to their individual authors, not the list. I hope I'm not breeching etiquette by redirecting my reply to the list. Thanks, Mark, for your cogent and complete reply. The short answer and good thing about all of this is, the new system is supposed to be an as-near-100% replica as is possible of the old system, just everything re-installed and new, just keeping the old data. The new system already has the same identity and nameserver info as the old, the idea being to move data and other applications (which is already underway) and then switch the DNS records after the new environment has been thoroughly tested. I'll check the wiki's you mentioned and report on progress when done. On Thu, 05 Jun 2014 08:09:52 -0700, you wrote: On 06/05/2014 04:27 AM, Steve Matzura wrote: I'm ready for the next step, which is to move an entire configuration and mail spool from an old Debian 5+Mailman 2.1.11 server. I imagine the spool (/var) files can just be tar'd and moved en masse. Yes and no. You do not want to move the locks/, logs/ or qfiles/ directories and spam/ is probably non-existent or empty. It's probably not necessary to move anything from data/ but that reqwuires some thought. But what about mailman configuration files--mailing list info, that sort of thing? What should be moved, what should be re-created, etc.? See the FAQ at http://wiki.list.org/x/2oA9 You do want to move the lists/ directory in its entirety except maybe the lists/mailman/ site list if you have already set that up on the new server. That moves list configs, membership, etc. If host/domain names are changing, you will need to run fix_url; see the FAQ at http://wiki.list.org/x/mIA9. You also maybe need to run bin/genaliases if your MTA uses mailman generated aliases and you didn't move them from data/ Archives can be an issue. You can move the entire archives/private/ directory and that should be OK, but people sometimes run into permissions issues following that. It is best not to move archives/public/, but if you do, make sure that you end up moving the symlinks and not their targets. archives/public/ contains only symlinks into archives/private and these will be created as appropriate by Mailman as lists are accessed. If host/domain names are changing, The cleanest process is to move only the archives/private/LISTNAME.mbox/LISTNAME.mbox files and rebuild the HTML archive with bin/arch for each list, but there are downsides to this. If some lists have scrub_nondigest = Yes, the scrubbed attachments will be lost in this process, and if there are unescaped From lines in messages that will cause problems too (see bin/cleanarch). -- 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] Moving Configurations and Lists to a New Server
On Thu, 05 Jun 2014 12:13:30 -0500, you wrote: On Thu, 2014-06-05 at 12:43 -0400, Steve Matzura wrote: This reply mechanism is driving me a little weird--the reply function sends the messages to their individual authors, not the list. I hope I'm not breeching etiquette by redirecting my reply to the list. Not at all! Most mail user agents can detect a list post and will offer a choice of whether to reply to the list or the original poster. Yours apparently can't do this. If the reply to all options is available the list address will be included and you can just delete the original poster address. OH no, it can do that all right, but it's a little odd in how it does it. Instead of putting both addresses in the To field, it puts the author in To and the mailing list in CC. I just use the regular reply and change the address, pointing that reply back here. It's a kluge, but it's what I got :-). -- 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] Unknown Virtual Host question
I'm setting up a new Mailman implementation on a new machine that's a virtual copy of a running production machine. I'm expecting problems because I'm trying to use the same domain name in two places, and I absolutely understand that's not going to work, but the bottom line is, the faster I get the new machine up and functional, the faster the old one will just go away and not bother me any more (LOL). So, on the new machine, I'm trying to create email lists via the Web interface at my new machine's IP address. When I log in with the Mailman administrator account and password and attempt to create a new list, I get the message unknown virtual host at x.x.x.x where 'x.x.x.x' is the IP address of the new machine. Is this caused by the fact that my A-record points to the old machine, or because my new machine is trying to validate against the old one somehow? If I were to stop Mailman on the old system temporarily and swing my A-record over to the new machine, would this solve the problem long enough for me to get lists created? If so, then I might as well just do the deed for real, and get the old machine out of the equation completely. What's best to do here? -- 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] We're sorry, we hit a bug!
Well, on a new implementation, I'm getting the same thing in 2.18-1. What'd you do to fix it on your end? On Tue, 1 Jul 2014 17:33:19 +0200, you wrote: Mark Sapiro m...@msapiro.net wrote: The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Thanks Mark, the page is showing that the log location was not writeable, must be the bug. Resetting the LOG_DIR to default saved me. Apologies for the noise. -- 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] 18-1 Bug with Empty error logfile
I just brought up a new 2.1.18-1 installation and am geting the we're sorry but we encountered a bug page on theadmin interface. /var/log/mail/error is 0-length. Should I turn stealth mode off to get more info possibly? -- 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] 18-1 Bug with Empty error logfile
Yes!Found and fixed three permissions errors. Then I logged in as asministrator and turned up another perms error, but this time it was logged to /var/log/mail/error so I was able to find and fix it. /etc/mailman/adm.pw was +644 owner=root group=roott. check_perms changed it to group=mailman as it should be. All good now, and of course, many thanks. It's always the little things. On Sat, 10 Jan 2015 10:04:43 -0800, you wrote: On 01/10/2015 07:01 AM, Steve Matzura wrote: I just brought up a new 2.1.18-1 installation and am geting the we're sorry but we encountered a bug page on theadmin interface. /var/log/mail/error is 0-length. Should I turn stealth mode off to get more info possibly? First, try running Mailman's bin/check_perms -f as root and see if it fixes permissions on the log directory/files. Once permissions are fixed, your bug may go away. If not and if there is still no error log entry, try turning off stealth mode. -- 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] Trying to get mail working
I have charge of a very mixed system--current OS (Fedora 20--OK 21's out but I just haven't upgraded yet), current (or nearly so) Mailman (2.1.18-1), Postfix 2.10 with a configuration file sfrom something a lot older which I've run through the upgrade-configuration procedure, and old Dovecot (1.0.15). Is there anything I can do to test each of these components individually, then add a second component and test the three pairs, then all three together? I am nobody's definitioin of an expert in any of these three components, so am having a lot of trouble making them work together, so I thought maybe there might be some test procedure that might straighten me out. Thanks in advance. -- 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] Trying to get mail working
On Wed, 13 May 2015 23:19:45 +0900, Steve Turnbull wrote: Dovecot and Mailman should be mostly independent of each other, while both depend crucially on Postfix. The first thing to do is to find the log files for each application, and test that mail works for all combinations of inside and outside the system (and often outside has to be divided into your domain and the rest of the Internet), to and from. If Dovecot isn't working, you still should be able to see mail flowing in the Postfix logs, and possibly learn something about its status using the mailq tool. Next work on being able to read and perhaps submit mail via Dovecot. Finally, do the Mailman configuration. Thanks. That sounds like an excellent starting point. Testing Dovecot or Mailman in the absence of a working Postfix is going to be hard for you, I guess. It's not impossible, but it requires some knowledge of internals of each program, and a fair amount of confidence with Unix tools like pipes and netcat. Much easier to learn to read Postfix's logs to determine when the problem is with one of the (non- ;-) cooperating applications, and when it's Postfix. Tools are not a problem, but program internals? Nah, not I, said the sys admin (LOL). At least I know now what the focal point is of the three. It would help if you describe the symptoms, although perhaps the best thing we can do is direct you to a Postfix or Dovecot channel. No symptoms to report, as I've not begun testing in a serious and methodical way ... until now, because I was clueless as to where to begin. I'll work with the above and reply with more details as they are revealed if things don't work. -- 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] Permissions error
Mark: On Thu, 02 Jul 2015 17:07:21 -0700, you wrote: The smpt log is now clean. Newest message is ten minutes older than the current date and time. I suspect running check_perms fixed everything. Does a 'subscribe' email get delivered to Mailman? That could have been a permissions issue, but it's usually something else. Still problems there, but there are other things I'm working on that are probably related. Will report on those later this a.m. -- 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] Permissions error
On Thu, 02 Jul 2015 16:46:00 -0700, you wrote:
On 07/02/2015 09:23 AM, Steve Matzura wrote:
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log. What's in the 'smtp-failure' log?
This sequence occurs every fifteen minutes:
Jul 03 09:57:21 2015 (1308) All recipients refused:
{'kelly@{mydomain.com}': (450, '4.1.1 kelly@{mydomain.com}:
Recipient address rejected: User unknown in virtual mailbox table')},
msgid: mailman.53.1435726803.13146.mailman@{mydomain.com}
Jul 03 09:57:21 2015 (1308) delivery to kelly@{mydomain.com} failed
with code 450: 4.1.1 kelly@{mydomain.com}: Recipient address
rejected: User unknown in virtual mailbox table
Jul 03 09:57:25 2015 (1308) All recipients refused:
{'lynn@{mydomain.com}': (450, '4.1.1 lynn@{mydomain.com}: Recipient
address rejected: User unknown in virtual mailbox table')}, msgid:
mailman.98.1435726804.13146.mailman@{mydomain.com}
Jul 03 09:57:25 2015 (1308) delivery to lynn@{mydomain.com} failed
with code 450: 4.1.1 lynn@{mydomain.com}: Recipient address
rejected: User unknown in virtual mailbox table
--
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] Permissions error
I have a new Mailman implementation connected to Postfix which is in
turn connected to Dovecot. These two components are working correctly,
as I have mailboxes set up with them and have created a test Mailman
mailing list and received confirmation that it has in fact been
created. Now I'm attempting to subscribe a test user in the normal
way, by sending an email to {list-name}-subscr...@mydomain.com. I have
not received a subscription confirmation, but the following
information from /var/log/mailman/error shows a problem:
Jul 02 14:15:01 2015 gate_news(18693): Traceback (most recent call
last):
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/cron/gate_news, line 293, in module
Jul 02 14:15:01 2015 gate_news(18693): main()
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/cron/gate_news, line 268, in main
Jul 02 14:15:01 2015 gate_news(18693): lock.lock(timeout=0.5)
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/Mailman/LockFile.py, line 243, in lock
Jul 02 14:15:01 2015 gate_news(18693): self.__write()
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/Mailman/LockFile.py, line 422, in __write
Jul 02 14:15:01 2015 gate_news(18693): fp = open(self.__tmpfname,
'w')
Jul 02 14:15:01 2015 gate_news(18693): IOError : [Errno 13]
Permission denied:
'/var/lock/mailman/gate_news.lock.{my-system-name}.{MyDomain.com}.18693.0'
Here are the directory permissions:
drwxrwsr-x 2 root mailman 80 Jul 2 13:57 mailman
lrwxrwxrwx 1 root root 11 Sep 14 2012 lock - ../run/lock
I also receive messages like these about every fifteen minutes in
/var/log/mailman/bounce:
Jul 02 14:42:12 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1736,
message-id=mailman.53.1435726803.13146.mailman@{my-domain.com}, 1
failures
Jul 02 14:42:16 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1733,
message-id=mailman.98.1435726804.13146.mailman@{my-domain.com}, 1
failures
Thanks in advance for any assistance. I suspect it's something I've
overlooked.
--
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] Unable to access Mailman Web interface
If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
following:
Bug in Mailman version 2.1.18-1
Bug in Mailman version 2.1.18-1
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 that's supposed to be /var/log/mailman/error, the only thing in
there is what I posted in my previous message. Maybe the two are
related?
--
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] Nightly Messages Show Problems
This should have gone to the list instead of where it went. On Sat, 04 Jul 2015 07:45:07 -0700, Mark Shapiro m...@msapiro.net wrote: These occur because you have installed a crontab which has been formatted as a system crontab and intended to be installed in a place like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron. Interesting. I followed the directions at http://www.gnu.org/software/mailman/mailman-install/node41.html which say: If your version of crontab supports the -u option, you must be root to do this next step. Add $prefix/cron/crontab.in as a crontab entry by executing these commands: % cd $prefix/cron % crontab -u mailman crontab.in System crontabs have an extra field between the days/times and the command which is the user to run as. In this case, that user (mailman) is interpreted as part of the command because the crontab is installed for a user. Should I remove the mailman ones and install it as root instead? The four are all permissions issues. Since check_perms thinks the permissions are OK, the issue could be that the user as which the crons are running is not in the 'mailman' group, or it could be a SELinux or other policy manager issue. mailman is not a group in root's passwd record. Sounds like the crontab.in needs editing to remove the mailman username from it? It seems there are at least two mailman crontabs. One is a user crontab in /var/spool/cron/mailman (or maybe /var/spool/cron/crontabs/mailman or ??) that is not formatted as a user crontab and is responsible for the /bin/sh: mailman: command not found messages. The other is probably in /etc/cron.d/mailman and is the one giving the permission exceptions. What are the contents of these crontabs? You only want one of these. Which may be important if there are SELinux issues, but otherwise, it doesn't matter as long as the one is correct. The two in /etc/cron.d and /var/spool/cron are identical. Here's the contents with the comment lines removed: MAILTO=s...@noisynotes.com 0 8 * * * mailman /usr/lib/mailman/cron/checkdbs 0 9 * * * mailman /usr/lib/mailman/cron/disabled 0 12 * * * mailman /usr/lib/mailman/cron/senddigests 0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip 30 4 * * * mailman /usr/lib/mailman/cron/cull_bad_shunt -- 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] Unable to access Mailman Web interface
On Sat, 04 Jul 2015 07:22:43 -0700, Mark wrote: Mailman has two main configuration paths, $prefix for immutable code, etc. and $var_prefix for mutable data. By default, $var_prefix = $prefix, but in your case, you or the packager whose package you installed configured mailman with $prefix=/usr/lib/mailman and $var_prefix=/var/lib/mailman. This is not unusual. I referred to $prefix rather than $var_prefix in a prior reply only because that was the term you used. Because that's the only one I knew of. Blame Red Hat for this one. :-) I installed the package as-was from their repository. In fact, if I didn't read up on it, I'd never know what $prefix is or is meant to be, as it's neither a defined global environment variable nor symbol. No matter, that one's cleared up. Also, please post to this list from your subscribed address Oversight. -- 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] Unable to access Mailman Web interface
On Sat, 04 Jul 2015 08:54:44 -0700, Mark Sapiro m...@msapiro.net wrote: The RedHat/Centos package is even more complex. See the FAQ at http://wiki.list.org/x/8486953. Thanks. Noted and saved for future reference. -- 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] Nightly Messages Show Problems
On Sat, 04 Jul 2015 09:11:54 -0700, you wrote: On 07/04/2015 08:27 AM, Steve Matzura wrote: On Sat, 04 Jul 2015 07:45:07 -0700, Mark Sapiro m...@msapiro.net wrote: These occur because you have installed a crontab which has been formatted as a system crontab and intended to be installed in a place like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron. Interesting. I followed the directions at http://www.gnu.org/software/mailman/mailman-install/node41.html which say: This is just one of many reasons for the advice in the FAQ at http://wiki.list.org/x/12812344. Packagers do various things that don't always align with what we recommend. In short, If you install from source, follow our docs; if you install a package, follow the packager's docs. In your case, the RedHat package has modified Mailman's crontab.in to be a system crontab and already installed it in /etc/cron.d/. Thus it was wrong to follow our manual and try to install it ads the Mailman user's crontab. Right. And it was wrong of RH not to tell me that up front, or if it does, it didn't jump up and tell me. Sometimes there's just so much to read and digest, and much of it has to be done after the fact. I'll comb their docs and if it's not present, will let you know so somehow it can be included somewhere. To correct this, just do sudo crontab -u mailman -r Done. Disabling SELinix may help, but you may not want to do that. Otherwise, you'd need to address this via SELinux policies, and I don't know what would need to be changed. This is interesting because the motivation for RedHat's file location changes to be FHS compliant was at least in part to make their Mailman package work well with SELinux. Then calling on my fine command of all things Linux (NOT), I'll leave it alone. -- 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] Permissions error
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
On 07/02/2015 07:56 AM, Steve Matzura wrote:
I have a new Mailman implementation connected to Postfix which is in
turn connected to Dovecot. These two components are working correctly,
as I have mailboxes set up with them and have created a test Mailman
mailing list and received confirmation that it has in fact been
created. Now I'm attempting to subscribe a test user in the normal
way, by sending an email to {list-name}-subscr...@mydomain.com. I have
not received a subscription confirmation, but the following
information from /var/log/mailman/error shows a problem:
Jul 02 14:15:01 2015 gate_news(18693): Traceback (most recent call
last):
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/cron/gate_news, line 293, in module
Jul 02 14:15:01 2015 gate_news(18693): main()
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/cron/gate_news, line 268, in main
Jul 02 14:15:01 2015 gate_news(18693): lock.lock(timeout=0.5)
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/Mailman/LockFile.py, line 243, in lock
Jul 02 14:15:01 2015 gate_news(18693): self.__write()
Jul 02 14:15:01 2015 gate_news(18693): File
/usr/lib/mailman/Mailman/LockFile.py, line 422, in __write
Jul 02 14:15:01 2015 gate_news(18693): fp = open(self.__tmpfname,
'w')
Jul 02 14:15:01 2015 gate_news(18693): IOError : [Errno 13]
Permission denied:
'/var/lock/mailman/gate_news.lock.{my-system-name}.{MyDomain.com}.18693.0'
Here are the directory permissions:
drwxrwsr-x 2 root mailman 80 Jul 2 13:57 mailman
lrwxrwxrwx 1 root root 11 Sep 14 2012 lock - ../run/lock
gate_news runs every 5 minutes. do you see this error every 5 minutes?
Have you run Mailman's bin/check_perms?
I just ran check_perms to fix another problem, and it appears the two
*were* related, as this one's now gone as well.
In any case, issues with gate_news only affect gating from usenet of
those lists that have Mail-News gateways - gateway_to_mail = Yes.
Mine don't, or shouldn't. If they do, I'll turn that off immediately.
I also receive messages like these about every fifteen minutes in
/var/log/mailman/bounce:
Jul 02 14:42:12 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1736,
message-id=mailman.53.1435726803.13146.mailman@{my-domain.com}, 1
failures
Jul 02 14:42:16 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1733,
message-id=mailman.98.1435726804.13146.mailman@{my-domain.com}, 1
failures
Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log. What's in the 'smtp-failure' log?
The smpt log is now clean. Newest message is ten minutes older than
the current date and time. I suspect running check_perms fixed
everything.
--
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] Permissions error
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log. What's in the 'smtp-failure' log?
Jul 02 16:12:13 2015 (1308)
mailman.53.1435726803.13146.mailman@{my-domain.com} smtp to mailman
for 1 recips, completed in 4.225 seconds
Jul 02 16:12:17 2015 (1308)
mailman.98.1435726804.13146.mailman@{my-domain.com} smtp to mailman
for 1 recips, completed in 4.159 seconds
I get this about every fifteen minutes.
There is one additional wrinkle here. I have two systems, one
production, one test. They are near duplicates of each other except
for age of software--production's old, test is near-current. Haven't
installed MM 2.1.20 yet. It would be all right if the messages to
mailman@{my-domain.com} went to the wrong machine, but they don't seem
to be going anywhere.
--
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] Unable to access Mailman Web interface
On Thu, 02 Jul 2015 08:24:12 -0700, you wrote:
On 07/02/2015 07:56 AM, Steve Matzura wrote:
If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
following:
Bug in Mailman version 2.1.18-1
Bug in Mailman version 2.1.18-1
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 that's supposed to be /var/log/mailman/error, the only thing in
there is what I posted in my previous message. Maybe the two are
related?
Run check_perms.
Did that. 898 problems found! I hope I didn't break Postfix. Luckily I
logged before and after in case I have to revert.
After check_perms fixed all problems, I re-ran it and got this:
Warning: Private archive directory is other-executable (o+x).
This could allow other users on your system to read private
archives.
If you're on a shared multiuser system, you should consult
the installation manual on how to fix this.
No problems found
Which section should I be reading?
--
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] Learning to use withlist
What's the best section of the standard documentation or the wiki to consult in order to learn how to correctly use withlist? -- 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] Unable to access Mailman Web interface
On Thu, 02 Jul 2015 16:39:36 -0700, you wrote: After check_perms fixed all problems, I re-ran it and got this: Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. No problems found Which section should I be reading? http://www.list.org/mailman-install/node9.html, but the question is this. Are there users who can log in to a shell or sftp or whatever who should not have any access to private list archives? If the answer is no, o+x on /path/to/mailman/archives/private is not a problem. If the answer is yes, set it o-x and change its owner to the web server uid. If you set it o-x and don't change the owner, public archive access won't work. Understood. Since this is really a new installation (I didn't copy archives from the old system because they're not really of any use), $prefix/archives doesn't exist yet. I'll keep the above in mind and implement it when list traffic commences on this installation. -- 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] Nightly Messages Show Problems
I guess things are getting better with my new mailman implementation,
as I received nine messages overnight I've never gotten before. four
are Errno 13 permission denied, five only contain one line:
/bin/sh: mailman: command not found
The subject fields of these five all begin with the same text telling
me they're from Mailman at my node, etc. The rest of the subject field
for each message was this:
/usr/lib/mailman/cron/cull_bad_shunt
/usr/lib/mailman/cron/checkdbs
/usr/lib/mailman/cron/disabled
/usr/lib/mailman/cron/senddigests
/usr/lib/mailman/cron/nightly_gzip
Here are the four Errno13 messages:
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/nightly_gzip
From: (Cron Daemon) mailman@{mydomain.com}
Date: Sat, 4 Jul 2015 03:27:02 + (UTC)
Traceback (most recent call last):
File /usr/lib/mailman/cron/nightly_gzip, line 158, in module
main()
File /usr/lib/mailman/cron/nightly_gzip, line 114, in main
mlist = MailList.MailList(name, lock=0)
File /usr/lib/mailman/Mailman/MailList.py, line 130, in __init__
self.Load()
File /usr/lib/mailman/Mailman/MailList.py, line 655, in Load
dict, e = self.__load(file)
File /usr/lib/mailman/Mailman/MailList.py, line 620, in __load
fp = open(dbfile)
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
From: (Cron Daemon) mailman@{mydomain.com}
Date: Sat, 4 Jul 2015 08:00:02 + (UTC)
Traceback (most recent call last):
File /usr/lib/mailman/cron/checkdbs, line 211, in module
main()
File /usr/lib/mailman/cron/checkdbs, line 87, in main
mlist = MailList.MailList(name)
File /usr/lib/mailman/Mailman/MailList.py, line 128, in __init__
self.Lock()
File /usr/lib/mailman/Mailman/MailList.py, line 161, in Lock
self.__lock.lock(timeout)
File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock
self.__write()
File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write
fp = open(self.__tmpfname, 'w')
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.Mydomain.com}.3681.0'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/disabled
From: (Cron Daemon) mailman@{mydomain.com}
Date: Sat, 4 Jul 2015 09:00:02 + (UTC)
Traceback (most recent call last):
File /usr/lib/mailman/cron/disabled, line 227, in module
main()
File /usr/lib/mailman/cron/disabled, line 150, in main
mlist = MailList.MailList(listname)
File /usr/lib/mailman/Mailman/MailList.py, line 128, in __init__
self.Lock()
File /usr/lib/mailman/Mailman/MailList.py, line 161, in Lock
self.__lock.lock(timeout)
File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock
self.__write()
File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write
fp = open(self.__tmpfname, 'w')
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.4471.0'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/senddigests
From: (Cron Daemon) mailman@{mydomain.com}
Date: Sat, 4 Jul 2015 12:00:02 + (UTC)
Traceback (most recent call last):
File /usr/lib/mailman/cron/senddigests, line 106, in module
main()
File /usr/lib/mailman/cron/senddigests, line 84, in main
mlist = MailList.MailList(listname, lock=0)
File /usr/lib/mailman/Mailman/MailList.py, line 130, in __init__
self.Load()
File /usr/lib/mailman/Mailman/MailList.py, line 655, in Load
dict, e = self.__load(file)
File /usr/lib/mailman/Mailman/MailList.py, line 620, in __load
fp = open(dbfile)
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'
Thinking a run of check_perms might help, I did so and got (then
fixed) this one error, which I reran with -f to fix:
/usr/lib/mailman/Mailman/mm_cfg.pyc bad group (has: root, expected
mailman) (fixing)
Not wanting to overload the list with diagnostics, hope this is
sufficient to start. More info on request of course.
--
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] Unable to access Mailman Web interface
On Fri, 03 Jul 2015 06:50:58 -0700, you wrote: $prefix/archives and the private/ and public/ sub-directories thereof are created on installation, and if Mailman is running there must be a 'mailman' site list and thus $prefix/archives/private/mailman/ and $prefix/archives/private/mailman.mbox/ subdirectories whether or not they contain any actual archives. Further, If $prefix/archives/private didn't exist, check_perms would have thrown a OSError: [Errno 2] No such file or directory: exception instead of reporting it was o+x. Interesting: My $prefix is /usr/lib/mailman. However, there is a /var/lib/mailman as that's where archives is. It's owned and grouped properly, and it does have the 1-bit set in the 'other' portion of its permissions mask. I can definitely fix that. But why does this all appear in /var/lib/mailman and not /usr/lib/mailman? -- 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] Learning to use withlist
On Fri, 03 Jul 2015 06:38:49 -0700, you wrote: If you mean what can you do interactively after invoking withlist on a list and have a '' prompt, see https://wiki.python.org/moin/BeginnersGuide#Learning_Python for the Python part. For the Mailman specific stuff, You need to understand what list attributes, functions and methods are available and not of this is documented in a single place, you really have to read the source. Oh boy. Not good. Here's what I'm after finding: I want to find something I can use to look at a list's properties in order to possibly determine what is wrong with my setup that's generating the smtp-failure messages and generally inhibiting or prohibiting mail from passing through lists. -- 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] Nightly Messages Show Problems
On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro m...@msapiro.net wrote: In your case, the RedHat package has modified Mailman's crontab.in to be a system crontab and already installed it in /etc/cron.d/. It did, but the file is virtually empty (only three or four comment lines warning not to edit it and that its contents is managed by /usr/lib/mailman/cron/crontab.in). I have restarted mm thinking the contents of crontab.in would be copied to /etc/cron.d/mailman like it was when it lived in /var/spool/cron. Should this be done manually? -- 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] No luck on the overnights
I'm now thinking none of the overnight cron jobs are running. I set digest mode to a couple lists, posted to them, then modified the digest job's run time from 12:00 every day to a minute or two from current time, waited ten minutes, and got nothing in response. Then I did the same for the monthly password reminder job. Same thing--no response. I'm thinking the best way to find out what's going on is to log into the mailman account interactively and manually run one of the cron commands to find out what happens. Any other suggestions most welcome. Probably whatever's wrong with one job is wrong with them all. -- 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] mailpasswd failure
With some excellent help, all my Mailman problems up to today have been solved. and my mailing lists have been behaving normally. Since it's a new month, mailpasswd ran earlier this morning. The email of the cron job reported a permissions error on one of the config.pck files for one of the lists. Investigation proved the offender was owned by root, not mailman. Interesting that check_perms didn't think this was a problem. I found several others that were like this and, figuring the one reported in the cron email was only the tip of the iceberg, I changed the others as well and forced the cron job to run again. As a result, I got the following: Traceback (most recent call last): File /usr/local/mailman/cron/mailpasswds, line 243, in module main() File /usr/local/mailman/cron/mailpasswds, line 237, in main 'verp': mm_cfg.VERP_PASSWORD_REMINDERS, File /usr/local/mailman/Mailman/Message.py, line 313, in send self._enqueue(mlist, **_kws) File /usr/local/mailman/Mailman/Message.py, line 325, in _enqueue **_kws) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 136, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/qfiles/virgin/1438435501.992054+ccd0ca1df3e432f3edbc589c470ce7b47276cc9d.pck.tmp' As you can tell, this is a hand-built installation of Mailman, which may or may not have something to do with this. check_perms reports no problems found. The directory /usr/local/mailman/qfiles/virgin, which is currently empty, is owned by root and is a member of the mailman group. Its protection mask is 770. Looking through the mm documentation isn't doing it for me at this point. Everything on the new system looks like it matches everything on the old system with regard to protection masks and ownerships. What else should I be checking? -- 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] Permissions error on all Mailman overnights
On Sat, 08 Aug 2015 18:47:29 -0700, Mark Sapiro m...@msapiro.net wrote: On 08/08/2015 06:22 PM, Steve Matzura wrote: On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked: What does groups mailman report? It should be 'mailman : mailman'. If so, and the crons are getting permission problems, check if SELinux is enabled and if so, try disabling it. It's mailman : mailman postfix, and SELinux is disabled according to getenforce. But it was mailman : postfix. Larry Turnbull fixed it by adding the 'mailman' group. No errors on the overnights, Things appear to be working correctly. I'm trying to run the password reminder job now, /var/log/messages shows it started twenty-three minutes ago, I haven't received any mail messages for password reminders on any of the lists on this system, so for all I know it may still be running and I'll just have to wait. If and when it finishes, I'll report. -- 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] Permissions error on all Mailman overnights
On Sun, 09 Aug 2015 08:44:56 -0700, Mark wrote: On 08/09/2015 08:25 AM, Steve Matzura wrote: No errors on the overnights, Things appear to be working correctly. I'm trying to run the password reminder job now, /var/log/messages shows it started twenty-three minutes ago, I haven't received any mail messages for password reminders on any of the lists on this system, so for all I know it may still be running and I'll just have to wait. If and when it finishes, I'll report. It shouldn't take that long. What is the exact command you issued (or did you run it by modifying Mailman's crontab)? What if anything does ps -fwwC python | grep mailpasswds I changed the crontab to a few minutes later than current time on today's day of the month, and I did try the process show command and it showed nothing running. The command in the crontab is: /usr/bin/python -S /usr/local/mailman/cron/mailpasswds report? -- 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] Permissions error on all Mailman overnights
Every night, I get the following error at the bottom of a mail message
to my mailman list telling me that checkdbs, digest and disabled
failed:
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-number}.0'
This also happened on the one and only password reminder message that
went out over a week ago, which no one received.
{some-number} is presumably the process ID of the job's process.
Here are descriptions of the locks directory on the old and new
systems--i.e., the one that works, and the one with the job failures.
The old system is Debian 4, from 2009, which has not received any
software upgrades since 2010. 'list' is the name of the Mailman user
and group. The locks directory, /var/lib/mailman/locks, is defined
thus:
lrwxrwxrwx 1 root root 18 2009-05-01 02:31 locks - ../../lock/mailman
drwxrwxrwt 4 root root 4096 2015-08-08 02:56 lock
drwxrwsr-x 2 root list 4096 2015-08-08 12:00 mailman
On the new Fedora 20 system with hand-built Mailman up to date,
'mailman' is its username and group, and the locks directory,
/usr/local/mailman/locks, is defined thus:
drwxrwsr-x 2 root mailman 4096 Aug 8 14:37 locks
The new system's permissions don't define the locks directory as
temporary, although at this very moment there are files in
it--master-qrunner, and master-qrunner.{my-FQDN}.{some-number}, both
of which have *tomorrow's* dates on them. ???
I'm thinking the locks directory may be at fault here, and if it is,
what was done wrong when Mailman was built or configured? This is
important not just because the mail system is not running correctly at
this time, but because I will be installing a second instance of
Mailman to support a new domain I'll be hosting, so I'm thinking
whatever I did wrong the first time will happen again, unless I
prevent it.
As always, thanks in advance for assistance.
--
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] Permissions error on all Mailman overnights
On Sat, 08 Aug 2015 09:19:27 -0700, Mark Sapiro m...@msapiro.net
wrote:
On 08/08/2015 08:12 AM, Steve Matzura wrote:
Every night, I get the following error at the bottom of a mail message
to my mailman list telling me that checkdbs, digest and disabled
failed:
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-number}.0'
So cron/checkdbs cant create a lock.
How are these crons running? Are they run form a user crontab
(/var/spool/cron/mailman ?) or a system crontab (/etc/cron.d/mailman ?)?
The former.
Your locks directory is fine. The master qrunner can create its locks
and the running Mailman and presumably the web CGIs can lock and unlock
lists which is done repeatedly. Your only issue seems to be with crons.
This must be either an issue with the user:group running the crons or a
security policy (SELinux or ?) issue.
No SELinux. getenforce says Disabled.
--
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] Permissions error on all Mailman overnights
On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked: What does groups mailman report? It should be 'mailman : mailman'. If so, and the crons are getting permission problems, check if SELinux is enabled and if so, try disabling it. It's mailman : mailman postfix, and SELinux is disabled according to getenforce. -- 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] Wrong perms?(fwd) Cron mailman@patronus /usr/lib/mailman/cron/nightly_gzip
After solving my cron confusions, I get these messages daily:
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/disabled
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'
When I looked for this file, it wasn't even there.
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/senddigests
...
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'
This file is owned by root and is in the mailman group.
check_perms reports no problems found.
--
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] Wrong perms?(fwd) Cron mailman@patronus /usr/lib/mailman/cron/nightly_gzip
On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:
On 07/09/2015 06:48 AM, Steve Matzura wrote:
After solving my cron confusions, I get these messages daily:
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/disabled
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'
When I looked for this file, it wasn't even there.
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/senddigests
...
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'
This file is owned by root and is in the mailman group.
check_perms reports no problems found.
In that case, these are almost certainly SELinux issues. Google things like
selinux logging
redhat disable selinux
redhat disable selinux without reboot
for information.
I checked to see if SELinux is even enabled on this system. It isn't.
getenforce says disabled.
--
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] Nightly Messages Show Problems
On Mon, 06 Jul 2015 19:17:23 -0700, you wrote: RedHat's /etc/init.d/mailman copies the cron/crontab.in to /etc/cron.d/mailman. So if you start Mailman via 'service mailman start', the crontab in crontab.in will be installed. At least that's the way I *think* it works. Ask RedHat or look at the init.d script to be sure. I thought so, to, but believe it or not, there is no such script in init.d. In fact, of all the packages I have installed, and there aren't more than half a dozen, only two have startup scripts in /etc/init.d. On to Red Hat support. -- 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] Nightly Messages Show Problems
On Tue, 07 Jul 2015 07:11:40 -0400, Mark wrote: RedHat's /etc/init.d/mailman copies the cron/crontab.in to /etc/cron.d/mailman. So if you start Mailman via 'service mailman start', the crontab in crontab.in will be installed. It's done in the Mailman service definition, which means the crontab copy is done only when the service is started via systemctl. If pre-mailmanctl processing is desired, the only way to make that happen is via systemctl. -- 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] cron log looks odd
I get Mailman job logs that look like this:
Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python
-S /usr/local/mailman/cron/checkdbs^M)
Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python
-S /usr/local/mailman/cron/disabled^M)
Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD
(/usr/bin/python -S /usr/local/mailman/cron/senddigests^M)
Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python
-S /usr/local/mailman/cron/mailpasswds^M)
Where does the '^M' come from, and is it bad that it's there?
--
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] cron log looks odd
On Tue, 1 Sep 2015 10:24:24 -0700, you wrote:
>On 09/01/2015 10:00 AM, Steve Matzura wrote:
>> I get Mailman job logs that look like this:
>>
>> Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python
>> -S /usr/local/mailman/cron/checkdbs^M)
>> Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python
>> -S /usr/local/mailman/cron/disabled^M)
>> Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD
>> (/usr/bin/python -S /usr/local/mailman/cron/senddigests^M)
>> Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python
>> -S /usr/local/mailman/cron/mailpasswds^M)
>>
>> Where does the '^M' come from, and is it bad that it's there?
>
>
>It's a . Your Mailman crontab file is a MS-Dos format file with
> line endings instead of *nix format with line endings.
>
>If your crons run OK, it's not a real problem, but if it were me, I'd
>fix the crontab file.
I'll do that. I thought it might be something like that, but I guess I
was expecting "\n", not "^M". Will fix it now. Thanks.
--
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 may contain ... administrivia?
Well now I've seen everything. Why would Mailman send a return message to a subscriber to a mailing list that says their message couldn't be posted to the mailing list because "message may contain administrivia"? -- 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 may contain ... administrivia?
Guilty as charged. On several counts. Oy!
On Thu, 01 Oct 2015 08:56:57 +0200, you wrote:
>In a message of Thu, 01 Oct 2015 01:35:02 -0400, Steve Matzura writes:
>>Well now I've seen everything. Why would Mailman send a return message
>>to a subscriber to a mailing list that says their message couldn't be
>>posted to the mailing list because "message may contain
>>administrivia".
>
>If your subject contains just one of these words, or this word
>followed by a reasonable number of arguments, or if the content
>of your message is again, one line, one of these words, or one of them
>followed by a reasonable number of arguments, then your message can
>be held.
>
>ADMINDATA = {
># admin keyword: (minimum #args, maximum #args)
>'confirm': (1, 1),
>'help':(0, 0),
>'info':(0, 0),
>'lists': (0, 0),
>'options': (0, 0),
>'password':(2, 2),
>'remove': (0, 0),
>'set': (3, 3),
>'subscribe': (0, 3),
>'unsubscribe': (0, 1),
>'who': (0, 0),
>}
>
>
>You can turn this off. Under general options, look for
>(Administrivia filter) Check postings and intercept ones that seem to be
>administrative requests?
>
>I mostly turn mine off, as I haven't found it very useful. It would be
>a good idea if your list was plagued by people trying to be sophisticated
>in using the list commands and mailing the list rather than list-request.
>This sort of thing happens to me about once every 5 years, over the
>management of a large number of lists. It is more common for me to get
>mail on lists Subject: I don't understand this error
>
>Help
>
>
>I am curious -- does mailman 3 have this feature?
>
>Laura
>
--
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
