Re: [Mailman-Users] Messages shunted with TypeError: decodingUnicode is not supported
Many thanks for the patch, Mark, your patch did indeed allow the message to go through. Ist it the case that the u'...' ones all have at least one upper case character in the local part and the rest don't? No, none of the u'...' addresses have uppercase characters. The only messages with uppercase characters are those without the u'...' format. Thanks again! Josh -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
I'm sorry to turn up in your support forum again, Mark. I've fought hard here to try to avoid that. The truth is it was our struggle with trying to configure my old server for mailman back in June and July that proved to be the straw that broke the camel's back with my old dedicated server hosting service. In early July I asked them about getting an updated server and software but the price they quoted was so darn high I decided to bail out on them and ended up choosing a hosting company that provided much more server for the $ plus the latest version of Debian Etch (rather than the 5 year old version of RedHat I was running) for the same price I'd been paying to my old hosting service. The BIG difference was I had to take full admin responsibility for my server setup and configuration; but I figured what the hell, I'm already doing 80% of that job anyway with very little support coming from my old host. So, when my old server came up for renewal at the end of July, I went month-to-month on my lease with them and bought the new server to take its place. I struggled through server setup and the migration of all my existing sites from the old server in August and September. At the end of September with just 3 sites left to move I grabbed the last 3 sites, made my final backups, and pulled the plug on the old server on the weekend before it would have renewed for another month... jumping out the window (from what turned out to be the 12th floor) with my final backups under my arm. :-) During October, I struggled to get the server set up to support mailman for multiple accounts. That entailed installing and testing it for the current client and setting up the server to support virtual domain hosting under Apache2, postfix and mailman so that we can eventually support mailman for multiple domains on this server. Until you mentioned suEXEC in your message yesterday, I'd nearly forgotten that part of our June-July nightmare. When I checked this morning, I found that when Apache2 was installed on this server it's standard installation process did include suEXEC. However, under Debian's Apache2 setup, it's easy to disable suEXEC and restart Apache. As far as I know, nothing else on the server was relying on the presence of suEXEC and it certainly wasn't my intent to install that Apache feature to begin with. So, suEXEC has now been disabled. Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? Or should I just put take a large dose of cyanide and go take a long nap instead? Thanks! -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 3:21 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the archive process running? TGPlatt, WebMaster wrote: Could this be a group/owner-ship issue? Yes. It took me a while, but I finally connected you with our exchanges from last June/July :) It hadn't occurred to me to look for mailman's error log. Plus I had no idea where it was. I've seen it mentioned but I'd seen nothing in the docs that said where to find it. But with a bit of looking, I found it in /usr/local/mailman/logs/error The error log that was saved when we made our final September 28 backup on the old server was last updated 9/25. The more I look the more this looks like an ownership issue to me. It may be I screwed up somewhere back in July. In our current mailman directory structure a smattering of files throughout the mailman directory tree seem to be owned by root / mailman now; whereas in the old backup everything seems to have been owned by mailman / mailman or www-data (Debian's default Apache user) / mailman. On 9/28, the error log was owned by mailman / mailman. Indeed everything except mischief, subscribed and vet were owned by mailman / mailman back then. Those three files were different and were owned by www-data / mailman. Today in our running copy of mailman, all logs are owned by mailman/mailman except error which is owned by root / mailman and mischief, vet and subscribed which are owned by www-data / mailman. There were undoubtedly problems on the old server because of SUExec issues which I told you at the time was incompatible with Mailman's security model since Mailman's CGI wrappers can't be SETGID under SUExec and that's the whole point of the wrappers in the first place. So ownership and permissions within Mailman have to be such that the SUExec user can read and write. But the qrunner processes also have to be able to read and write and they will run as the mailman user:group. Normally the owner doesn't matter because everything runs as group mailman, but that may not be the case here. The reason I think this is an ownership issue is because when I look at the July - September error log I see lots of errors like this: Jul 09 07:29:22 2008
[Mailman-Users] help diagnosing problem
Hi, I'm running mailman 2.1.9 under Ubuntu, and for some reason it seems to somehow be getting stuck once in a while. Almost every day I have to kick it to get it going by restarting the process. Although it seems all the qrunner processes are still there, the qfiles seem stuck and until I restart mailman, the queue does not get processed. I have a couple large lists, to the point that when the queue gets stuck, I can come in the morning and see there are almost 20,000 messages in the qfiles/out directory. I've been running these lists for a few years now, and they were running fine under mailman in another server, but now I've moved them to a new server, and somehow this is happening. I see that in logs/error there are a lot of errors related to unparseable message, for example: Oct 29 07:46:00 2008 (4208) Uncaught runner exception: multipart message with no defined boundary Oct 29 07:46:00 2008 (4208) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/lib/mailman/Mailman/Queue/Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/lib/mailman/pythonlib/email/__init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/lib/mailman/pythonlib/email/Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/lib/mailman/pythonlib/email/Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/lib/mailman/pythonlib/email/Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/lib/mailman/pythonlib/email/Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/lib/mailman/pythonlib/email/Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/lib/mailman/pythonlib/email/Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/lib/mailman/pythonlib/email/Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/lib/mailman/pythonlib/email/Parser.py, line 247, in _parsebody 'multipart message with no defined boundary') BoundaryError: multipart message with no defined boundary Oct 29 07:46:00 2008 (4208) Ignoring unparseable message: 1225156297.669034+58c184ed96a18e9fdad8c658fde5815c31440c01 But anyway, these lists ran without a hitch in the other server with an older version of mailman. Is there something I can look at to help debug this problem? Right now it looks like I have to resort to a cron entry to restart mailman once a day, probably.. :-( Thanks for any help Ricardo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] help diagnosing problem
Ricardo Kleemann wrote: I'm running mailman 2.1.9 under Ubuntu, and for some reason it seems to somehow be getting stuck once in a while. Almost every day I have to kick it to get it going by restarting the process. Although it seems all the qrunner processes are still there, the qfiles seem stuck and until I restart mailman, the queue does not get processed. Which queues are not processed? All or just out/? I have a couple large lists, to the point that when the queue gets stuck, I can come in the morning and see there are almost 20,000 messages in the qfiles/out directory. I've been running these lists for a few years now, and they were running fine under mailman in another server, but now I've moved them to a new server, and somehow this is happening. I see that in logs/error there are a lot of errors related to unparseable message, for example: snip Oct 29 07:46:00 2008 (4208) Ignoring unparseable message: 1225156297.669034+58c184ed96a18e9fdad8c658fde5815c31440c01 This is malformed spam sent to a list and ignored. It is not related to your problem. But anyway, these lists ran without a hitch in the other server with an older version of mailman. Is there something I can look at to help debug this problem? Right now it looks like I have to resort to a cron entry to restart mailman once a day, probably.. :-( I'm guessing it's only the out queue that gets stuck. If so, it is probably because of some glitch in SMTP delivery to your MTA that is causing the SMTP library routines to hang waiting for an SMTP response that never comes. Look in Mailman's smtp-failure log for clues and see the FAQ at http://wiki.list.org/x/-IA9. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Ubuntu version number
How can I tell what actual version of Mailman I have. I am using mailman on an Ubuntu server and the Ubuntu version number is not in the same general format as the mailman version numbers. Bob Lydiate -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mailman archiver not archiving
I've set up postfix / dovecot / mailman on my server and it works well, except that no messages to mailman lists are archived. The server hosts several domains, though mailman serves only one of the domains. Mail is delivered to mailing list subscribers as expected, but the messages are never added to the mbox archive file. Mailman logs show no errors. I'm using Fedora 9, mailman 2.1.9, python 2.5.1, postfix 2.5.1, all installed from standard f9 RPMs. Archiving is enabled. The aliases for the mailman lists are set up correctly. Regular users have mail delivered in Maildir format. Does this affect mailman? Any suggestions for things to check? Thanks! /james -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Moving Lists
Hello All, I am a newbie to the Mailman ListServer, so go easy... I have a new server running our new Mailman Lists. I also have an older system containing Mailman lists that I want to migrate to the new server. Is this possible? If so... how is it done? Any help is appreciated. -Jeff It does not require many words to speak the truth. - Chief Joseph, Great Nez Perce Indian Chief -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Correct Syntax For SUBSCRIBE Email Command
Hello, Sorry for the stupid question but the documentation shows no examples and I am getting tired of playing 20 guesses with Mailman and always loosing. How do I make the following work? - subscribe address= John Q Public [EMAIL PROTECTED] YIELDS: The results of your email command are provided below. Attached is your original message. - Results: Bad digest specifier: John - Done. According to the Help password and digest are optional yet it seems to want digest. Are commands case sensitive? Are extra spaces a problem and if so where? I want to include a name to go along with the email address. The web interface seems to be content with the above address format. Unfortunately, the user doing the subscribing will not be an administrator and will not have access to the web interface. Thanks, Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Mailman on multiple domains
Hello all, Question about using mailman in a virtual domain scenario. I currently have Postfix on a RHLE server with mailman installed working for a single domain. I am configuring Postfix for virtual domains, using the Virtual Mailbox Domain setup instead of alias domains since I'm assuming I am not going to have local user accounts for the virtual domains. I'm getting stuck in the virtual recipient maps section. I am not sure how I should setup my maps. Postfix wants me to map an email address to a virtual mailbox, but since mailman has multiple email addresses, do I need a mailbox for each email address? Thanks in advance! Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman on multiple domains
I did some more research and looked at the Mailman Install info (should have done that before posting, sorry). Looks like I need to be using virtual alias domains instead of virtual mailbox domains. I will work with this config. Thanks! Scott -Original Message- From: Scott Race Sent: Tuesday, October 28, 2008 11:15 AM To: mailman-users@python.org Subject: Mailman on multiple domains Hello all, Question about using mailman in a virtual domain scenario. I currently have Postfix on a RHLE server with mailman installed working for a single domain. I am configuring Postfix for virtual domains, using the Virtual Mailbox Domain setup instead of alias domains since I'm assuming I am not going to have local user accounts for the virtual domains. I'm getting stuck in the virtual recipient maps section. I am not sure how I should setup my maps. Postfix wants me to map an email address to a virtual mailbox, but since mailman has multiple email addresses, do I need a mailbox for each email address? Thanks in advance! Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Mailman on multiple domains
I have Postfix and Mailman running on a RHLE server. Mailman and Postfix work fine for a single domain setup. I have now setup my postfix configuration setup to accept mail for multiple domains. I did so editing main.cf to include the new domain I want to receive mail for, created a local user account for the user, and created a virtual_alias_maps file which tells the email to the second domain to forward to the new user account I setup. So I have mailman running on a new VirtualHost, I can create a list from the web interface, I can join lists and all emails from the system look ok (having the second domain name). When posting, I get the following: Your message did not reach some or all of the intended recipients. Subject: Test Post Sent: 10/28/2008 1:11 PM The following recipient(s) could not be reached: [EMAIL PROTECTED] on 10/28/2008 1:11 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=jda:SERVER This must have something to do with my virtual_alias_maps file, which currently has nothing in it except a map from the second domain to a local user (which I just did as a test). I'm sure I'm missing something here? Thanks Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman on multiple domains
As a follow-up, I don't seem to have the virtual-mailman file on my server anywhere as stated in the documentation From: Scott Race Sent: Tuesday, October 28, 2008 1:18 PM To: mailman-users@python.org Subject: Mailman on multiple domains I have Postfix and Mailman running on a RHLE server. Mailman and Postfix work fine for a single domain setup. I have now setup my postfix configuration setup to accept mail for multiple domains. I did so editing main.cf to include the new domain I want to receive mail for, created a local user account for the user, and created a virtual_alias_maps file which tells the email to the second domain to forward to the new user account I setup. So I have mailman running on a new VirtualHost, I can create a list from the web interface, I can join lists and all emails from the system look ok (having the second domain name). When posting, I get the following: Your message did not reach some or all of the intended recipients. Subject: Test Post Sent: 10/28/2008 1:11 PM The following recipient(s) could not be reached: [EMAIL PROTECTED] on 10/28/2008 1:11 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=jda:SERVER This must have something to do with my virtual_alias_maps file, which currently has nothing in it except a map from the second domain to a local user (which I just did as a test). I'm sure I'm missing something here? Thanks Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Ubuntu version number
Bob Lydiate wrote: How can I tell what actual version of Mailman I have. I am using mailman on an Ubuntu server and the Ubuntu version number is not in the same general format as the mailman version numbers. That sounds like an Ubuntu question that should be asked on the Ubuntu mailing lists. Version number formats I've seen in the past have been like 2.1.5-1, where the portion before the dash would be the baseline code from us that they started with, and the number after the dash would indicate how many of their minor revisions they've made to the code after they forked. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman archiver not archiving
James Chapman wrote: Any suggestions for things to check? The FAQ? Try searching for troubleshooting or no mail goes out to members, etc -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
I'm sorry to turn up in your support forum again, Mark. I've fought hard here to try to avoid that. The truth is it was our struggle with trying to configure my old server for mailman back in June and July that proved to be the straw that broke the camel's back with my old dedicated server hosting service. In early July I asked them about getting an updated server and software but the price they quoted was so darn high I decided to bail out on them and ended up choosing a hosting company that provided much more server for the $ plus the latest version of Debian Etch (rather than the 5 year old version of RedHat I was running) for the same price I'd been paying to my old hosting service. The BIG difference was I had to take full admin responsibility for my server setup and configuration; but I figured what the hell, I'm already doing 80% of that job anyway with very little support coming from my old host. So, when my old server came up for renewal at the end of July, I went month-to-month on my lease with them and bought the new server to take its place. I struggled through server setup and the migration of all my existing sites from the old server in August and September. At the end of September with just 3 sites left to move I grabbed the last 3 sites, made my final backups, and pulled the plug on the old server on the weekend before it would have renewed for another month... jumping out the window (from what turned out to be the 12th floor) with my final backups under my arm. :-) During October, I struggled to get the server set up to support mailman for multiple accounts. That entailed installing and testing it for the current client and setting up the server to support virtual domain hosting under Apache2, postfix and mailman so that we can eventually support mailman for multiple domains on this server. Until you mentioned suEXEC in your message yesterday, I'd nearly forgotten that part of our June-July nightmare. When I checked this morning, I found that when Apache2 was installed on this server it's standard installation process did include suEXEC. However, under Debian's Apache2 setup, it's easy to disable suEXEC and restart Apache. As far as I know, nothing else on the server was relying on the presence of suEXEC and it certainly wasn't my intent to install that Apache feature to begin with. So, suEXEC has now been disabled. Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? Shouldn't all (or most of) these files be owned by mailman / mailman? Is that also true in the /archives/private/mylist directory? What about over in the /home/mylist/www directory? Who should own the mailman directory there? I have run bin/check_perms several times but it doesn't complain about any problems. Thanks! Or should I just put take a large dose of cyanide and go take a long nap instead? Thanks! -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 3:21 PM TGPlatt, WebMaster wrote: Could this be a group/owner-ship issue? Yes. It took me a while, but I finally connected you with our exchanges from last June/July :) snip --- There were undoubtedly problems on the old server because of SUExec issues which I told you at the time was incompatible with Mailman's security model since Mailman's CGI wrappers can't be SETGID under SUExec and that's the whole point of the wrappers in the first place. So ownership and permissions within Mailman have to be such that the SUExec user can read and write. But the qrunner processes also have to be able to read and write and they will run as the mailman user:group. Normally the owner doesn't matter because everything runs as group mailman, but that may not be the case here. snip and when I check the files in that directory, they're owned by root as a member of the group mailman. That should be OK because ArchRunner should be running as group mailman and the files should be group writable. snip when I look at the qfiles/shunt directory in the 9/28 backup, the oldest file there seems to be from 09-20-2008. So it looks to me like it was only keeping those shunt files 5 or 6 days before discarding them. If you are running Mailman 2.1.11, there is a cron that runs daily and by default it discards anything in qfiles/bad and qfiles/shunt older than 7 days. From Defaults.py # The length of time after which a qfiles/bad or qfiles/shunt file is # considered to be stale. Set to zero to disable culling of qfiles/bad and # qfiles/shunt entries. BAD_SHUNT_STALE_AFTER = days(7) # The pathname of a directory (searchable and writable by the Mailman cron # user) to which the culled qfiles/bad and qfiles/shunt entries will be # moved. Set to None to simply delete the culled entries. BAD_SHUNT_ARCHIVE_DIRECTORY = None snip So you still have permissions issues. You could start with bin/check_perms which
[Mailman-Users] Web link configurations?
I have modified the mm_cfg.py file with the correct DEFAULT_URL_HOST, but the web links keep defaulting to the hostname of the server instead of the CNAME (alias) of the site as defined in the mm_cfg. Where else might mailman be getting the settings from that I haven't checked yet? Thanks, DAVID -- David A. Lane, KG4GIY EC/RO Prince William County ARES(R)/RACES +1.703.628.3868 http://www.pwcares.org/ IM/Skype: kg4giy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving Lists
Jeff Bernier wrote: I have a new server running our new Mailman Lists. I also have an older system containing Mailman lists that I want to migrate to the new server. Is this possible? If so... how is it done? The Mailman FAQ Wizard at http://wiki.list.org/display/DOC/Frequently+Asked+Questions has a wealth of information. In particular, there is one entry entitled How do I move a list to a different server-Mailman installation, which is located at http://wiki.list.org/x/2oA9. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Web link configurations?
David Lane wrote: I have modified the mm_cfg.py file with the correct DEFAULT_URL_HOST, but the web links keep defaulting to the hostname of the server instead of the CNAME (alias) of the site as defined in the mm_cfg. Where else might mailman be getting the settings from that I haven't checked yet? Keep in mind that a lot of software will re-write hostnames into their canonical form. Most MTAs do this by default (based on a certain reading of the RFCs), and I would not be at all surprised to find that web browsers and web servers would do the same. So, the lesson is that before you start blaming anything else, you might want to try removing the CNAME alias entirely, and set up a plain A record for that name. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Ubuntu version number
Bob Lydiate [EMAIL PROTECTED] wrote: How can I tell what actual version of Mailman I have. I am using mailman on an Ubuntu server and the Ubuntu version number is not in the same general format as the mailman version numbers. Did you install the Ubuntu/Debian package? If so, then you have a mixture of versions. When I looked at 2.1.9, I reviewed all of the Debian patches. Most were undocumented, so I had no idea what they did. And I could not determine the base version number. IIRC, one patch seemed to be based on 2.1.4 code. Of three security patches, two matched the SourceForge source, and one did not. There is also a patch that erroneously deletes a library that is sometimes needed. It was at this time that I decided that I had no idea what source I was running, and I was not assured of getting assistance from this Mailman-users group. So I decided to build my own Ubuntu package from the SourceForge source. The only patch I kept was one that placed libraries in the proper directories for Ubuntu. Short answer - look at the changes file or the patch directory. My test Mailman virtual machine is down now for patching, so I cannot give you the exact directories and paths. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] membership disabled message
Hi, One of my lists is the newsletter type, where one person is in charge of doing subs and unsubs. For this list in particular I don't really care, at all, about sending this disabled message to the users. In the list config, I set bounce_you_are_disabled_warnings to 0 yet I still see mailman sending out these messages. how can I completely disable this feature? Thanks Ricardo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Ubuntu version number
Bob Lydiate wrote: How can I tell what actual version of Mailman I have. I am using mailman on an Ubuntu server and the Ubuntu version number is not in the same general format as the mailman version numbers. You can look in Mailman's data/last_mailman_version This will contain something like 0x2010bf0 which parses as 2 |01 | 0b| f |0 major | minor | micro | level| serial = 2.1.11 final for the level, a = alpha, b = beta, c = releace candidate and f = final -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Correct Syntax For SUBSCRIBE Email Command
Steve Lund wrote: Sorry for the stupid question but the documentation shows no examples and I am getting tired of playing 20 guesses with Mailman and always loosing. How do I make the following work? - subscribe address= John Q Public [EMAIL PROTECTED] You can't. Your syntax is wrong. It parses into 3 arguments: address= John Q Public [EMAIL PROTECTED] but that's not the issue. If it worked, you would need subscribe 'address= John Q Public [EMAIL PROTECTED]' but that won't work because this form doesn't expect a real name. You need subscribe [EMAIL PROTECTED] Or if you need the real name, send the email From: John Q Public [EMAIL PROTECTED] with just subscribe as the command or send it to the -subscribe address. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] help diagnosing problem
Ricardo Kleemann wrote: Ok, I do see that there are a few errors for malformed remote addresses, but would this cause mailman to stop processing? Looking through smtp-failure I see only a couple of these errors in an hour timeframe, nothing that would cause mailman to get stuck. The errors you see are symtoms of problems between Mailman and the MTA. You won't actually see anything in the smtp-failure log about the hang itself. It seems very slow in handling the large outqueue, even though I have a high power server and very fast internet connection. I don't see python taking up much of the cpu, it is processing the out queue, but it would seem to me, very slowly. Because most of the time is Mailman just waiting for an SMTP response. If you have Python 2.4 or later, see the FAQ at http://wiki.list.org/x/-IA9 for a way to get copious debugging info from the Python smtplib. Also search the FAQ for 'performance'. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] membership disabled message
Ricardo Kleemann wrote: One of my lists is the newsletter type, where one person is in charge of doing subs and unsubs. For this list in particular I don't really care, at all, about sending this disabled message to the users. In the list config, I set bounce_you_are_disabled_warnings to 0 yet I still see mailman sending out these messages. how can I completely disable this feature? What you have done will cause any newly bouncing members to be immediately unsubscribed when their score reaches the threshold. Those members who were already disabled when you changed bounce_you_are_disabled_warnings to 0, will continue to get notices until they have received the old number of notices because when a member is disabled, we store the number of remaining notices for that member and then decrement it with each notice until it reaches zero. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman on multiple domains
Scott Race wrote: So I have mailman running on a new VirtualHost, I can create a list from the web interface, I can join lists and all emails from the system look ok (having the second domain name). When posting, I get the following: Your message did not reach some or all of the intended recipients. Subject: Test Post Sent: 10/28/2008 1:11 PM The following recipient(s) could not be reached: [EMAIL PROTECTED] on 10/28/2008 1:11 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=jda:SERVER This must have something to do with my virtual_alias_maps file, which currently has nothing in it except a map from the second domain to a local user (which I just did as a test). I'm sure I'm missing something here? That message and text did not come from Postfix. I think this is an Exchange issue that is not allowing the mail to even get as far as Postfix on the Mailman machine. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman on multiple domains
Scott Racewrote: As a follow-up, I don't seem to have the virtual-mailman file on my server anywhere as stated in the documentation Is the virtual domain in POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.virtual.domain'] in mm_cfg.py. Is the host_name of the list = the.virtual.domain Have you run Mailman's bin/genaliases since setting MTA= 'Postfix' and POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.virtual.domain'] in mm_cfg.py? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
TGPlatt, WebMaster wrote: Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? Shouldn't all (or most of) these files be owned by mailman / mailman? Is that also true in the /archives/private/mylist directory? What about over in the /home/mylist/www directory? Who should own the mailman directory there? I have run bin/check_perms several times but it doesn't complain about any problems. check_perms should complain about ownership and permission problems. Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. In general everything from /usr/local/mailman on down should be group mailman (owner doesn't matter) and directories need to be g+rws and files g+rw. See the post at http://mail.python.org/pipermail/mailman-users/2008-October/063748.html. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
It looks to me like check_perms has a hole in it, Mark. If you take a close look at the error I've been getting repeatedly since early July (see below), you'll see it consistently occurs on the index.html table in the /usr/local/mailman/archives/private/mylist directory. Here are the permissions on that file: 12 -rw-r--r-- 1 mailman mailman 11452 Oct 20 07:01 index.html Please note that the permissions on that file are 644 and not 664. I just ran check_perms on this account. It reported No Problems Found. Yet when Archrunner runs and tries to open that file to replace it, it reports a permissions error for that file. In short, check_perms reports those 644 permissions are just fine while you're telling me they should be 664 and ARCHrunner complains they're NOT fine. This suggests to me check_perms isn't doing its job very well. Am I wrong about this? Here's the error ARCHrunner has been reporting repeatedly since early July... Oct 28 10:09:30 2008 (2589) Uncaught runner exception: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/mylist/index.html' Oct 28 10:09:30 2008 (2589) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/local/mailman/Mailman/Archiver/Archiver.py, line 217, in ArchiveMa il h.close() File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 324, in close self.write_TOC() File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 1097, in write_T OC toc = open(os.path.join(self.basedir, 'index.html'), 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/mylist/index.html' What am I missing here? -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 5:50 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the archive process running? TGPlatt, WebMaster wrote: Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? Shouldn't all (or most of) these files be owned by mailman / mailman? Is that also true in the /archives/private/mylist directory? What about over in the /home/mylist/www directory? Who should own the mailman directory there? I have run bin/check_perms several times but it doesn't complain about any problems. check_perms should complain about ownership and permission problems. Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. In general everything from /usr/local/mailman on down should be group mailman (owner doesn't matter) and directories need to be g+rws and files g+rw. See the post at http://mail.python.org/pipermail/mailman-users/2008-October/063748.html. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
You said: Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. But mailman's home directory (where all its programs, scripts, archives and discussion lists are stored) IS /usr/local/mailman and according to my Mailman/Defaults.py, both var_prefix and prefix are also /user/local/mailman PREFIX = '/usr/local/mailman' VAR_PREFIX = '/usr/local/mailman' How does that change things? -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 5:50 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the archive process running? TGPlatt, WebMaster wrote: Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? Shouldn't all (or most of) these files be owned by mailman / mailman? Is that also true in the /archives/private/mylist directory? What about over in the /home/mylist/www directory? Who should own the mailman directory there? I have run bin/check_perms several times but it doesn't complain about any problems. check_perms should complain about ownership and permission problems. Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. In general everything from /usr/local/mailman on down should be group mailman (owner doesn't matter) and directories need to be g+rws and files g+rw. See the post at http://mail.python.org/pipermail/mailman-users/2008-October/063748.html. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
TGPlatt, WebMaster wrote: Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. But mailman's home directory (where all its programs, scripts, archives and discussion lists are stored) IS /usr/local/mailman and according to my Mailman/Defaults.py, both var_prefix and prefix are also /user/local/mailman PREFIX = '/usr/local/mailman' VAR_PREFIX = '/usr/local/mailman' How does that change things? When you said: Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? it seemed to me you were talking about two separate directories, /usr/local/mailman and UserAccount/mailman. Whether or not these are separate directories or the same directory, the ownership and permissions on /usr/local/mailman are the only ones that matter. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
TGPlatt, WebMaster wrote: It looks to me like check_perms has a hole in it, Mark. If you take a close look at the error I've been getting repeatedly since early July (see below), you'll see it consistently occurs on the index.html table in the /usr/local/mailman/archives/private/mylist directory. Here are the permissions on that file: 12 -rw-r--r-- 1 mailman mailman 11452 Oct 20 07:01 index.html Please note that the permissions on that file are 644 and not 664. I just ran check_perms on this account. It reported No Problems Found. Yet when Archrunner runs and tries to open that file to replace it, it reports a permissions error for that file. In short, check_perms reports those 644 permissions are just fine while you're telling me they should be 664 and ARCHrunner complains they're NOT fine. This suggests to me check_perms isn't doing its job very well. This appears to be a problem with check_perms. You are correct that it isn't doing its job very well. There are a lot of files it doesn't check, and at least some of those should be checked. I'll look into fixing that. Thanks for pointing it out. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Changing a user's email address
Suppose I have a user that changes his email address and I don't want to wait for that user to confirm the address change? How do I change the address of any user simply as the list admin with no involvement of the list member? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Changing a user's email address
Dennis Putnam wrote: Suppose I have a user that changes his email address and I don't want to wait for that user to confirm the address change? How do I change the address of any user simply as the list admin with no involvement of the list member? Thanks. If you have command line access, use bin/clone_member. If not, this is an as yet unimplemented feature request. The only way to currently do it as a list admin is to add the new address, set all its member options the same as the old address and remove the old address, but this changes the member's password so it isn't completely satisfactory. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
I've probably just misunderstood something here. When you helped me with my setup in July, you had me create a mailman directory in the user's web space and we used that directory somehow. I've forgotten the exact reason we did that now but I vaguely recall it had something to do with working around my old Redhat 7.2 and Apache 1.2 server's suEXEC setup to gain access to the mailman programs. The user's web account still has that mailman directory present in it. It hadn't occurred to me yet that it might not need to be there at all now. To help jog your memory, its setup looks like this: myserver:/home/mylist/www# ls -als mailman total 12 4 drwxr-xr-x 3 mylist mylist 4096 Oct 20 07:22 . 4 drwxr-xr-x 12 mylist mylist 4096 Oct 29 17:46 .. 4 drwxrwsr-x 2598 mylist 4096 Oct 28 06:53 mail myserver:/home/mylist/www# ls -als mailman/mail total 48 4 drwxrwsr-x 2598 mylist 4096 Oct 28 06:53 . 4 drwxr-xr-x 3 mylist mylist 4096 Oct 20 07:22 .. 40 -rwxr-xr-x 1 598 mylist 39801 Jun 29 18:41 mailman So, when I asked about ownership and permissions and mentioned the UserAccount/mailman directory, that's the directory I was referring to. Sorry if I confused you. :-( Should I just remove that spare mailman directory from the user's space now? -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 8:56 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the archive process running? TGPlatt, WebMaster wrote: Assuming mailman's home directory is NOT /usr/local/mailman and assuming that prefix, and var_prefix are /usr/local/mailman, mailman's home directory is irrelevant. But mailman's home directory (where all its programs, scripts, archives and discussion lists are stored) IS /usr/local/mailman and according to my Mailman/Defaults.py, both var_prefix and prefix are also /user/local/mailman PREFIX = '/usr/local/mailman' VAR_PREFIX = '/usr/local/mailman' How does that change things? When you said: Now can we talk about the proper ownership of all the mailman files both IN /usr/local/mailman directory structure and in the UserAccount/mailman directory as well? it seemed to me you were talking about two separate directories, /usr/local/mailman and UserAccount/mailman. Whether or not these are separate directories or the same directory, the ownership and permissions on /usr/local/mailman are the only ones that matter. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archive process running?
LOL!! Bear in mind my guru friend that what's apparent to someone with your years of experience and wisdom isn't the least bit obvious to a mailman newcomers like me. Naïve as it may be, we tend to assume that when the program says it checked permissions and found no problems we're not likely to encounter permission issues with mailman's own automated processes later. I know that's a silly assumption to make, but we'll tend to make it anyway. ;-) That's why I deliberately avoided seeking your help while I struggled and did extensive testing and research for DAYS trying to figure out exactly how to configure Apache, Postfix and Mailman with virtual alias domains so that I might at least have a prayer someday of being able to support more than one mailman discussion list on my server. As a result of that struggle, I may not know everything there IS to know, but at least understand the basic concepts now. I'm engaged in a similar struggle now in trying to understand mailman ownership and permissions. I'm not sure I understand how ownership and permissions play out in mailman. So, I'm forced to proceed with absolute faith that YOU know what you're doing, sir. For my part, I feel like a blind man who is flying a wide-body jet filled with screaming passengers into Atlanta at rush hour for the first time. And YOU and the mailman tools are my ONLY guides. So, since the check_perms tool doesn't work flawlessly, I'm relying on you to tell me how to do it right, oh Guru! B-) Thanks for being so patient and understanding. -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 9:18 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the archive process running? TGPlatt, WebMaster wrote: It looks to me like check_perms has a hole in it, Mark. If you take a close look at the error I've been getting repeatedly since early July (see below), you'll see it consistently occurs on the index.html table in the /usr/local/mailman/archives/private/mylist directory. Here are the permissions on that file: 12 -rw-r--r-- 1 mailman mailman 11452 Oct 20 07:01 index.html Please note that the permissions on that file are 644 and not 664. I just ran check_perms on this account. It reported No Problems Found. Yet when Archrunner runs and tries to open that file to replace it, it reports a permissions error for that file. In short, check_perms reports those 644 permissions are just fine while you're telling me they should be 664 and ARCHrunner complains they're NOT fine. This suggests to me check_perms isn't doing its job very well. This appears to be a problem with check_perms. You are correct that it isn't doing its job very well. There are a lot of files it doesn't check, and at least some of those should be checked. I'll look into fixing that. Thanks for pointing it out. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
