[Mailman-Users] Feature reqeust for wiki.list.org - short URLs
Hello world, first of all, the Mailman wiki at http://wiki.list.org/ is really very helpful. I've come to find it's structure very clean and easy to understand. Especially the FAQ part is very, very helpful and saved me lots of time when trying to troubleshoot a problem. But - there is one thing about the length of URLs. Let's consider for example (long line incoming): http://wiki.list.org/display/DOC/4.16+How+do+I+prevent+duplicate+copies+of+email+coming+to+the+list If I click on Tools - Info, the wiki presents me the shorter URL: http://wiki.list.org/x/eoA9 Do you think it's possible to modify the wiki code as to present this shorter URL on every page so that one could copy the short link without having to call Tools - Info? Cheers Stefan -- 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] Messages shunted with TypeError: decodingUnicodeis not supported
Try applying the attached Decorate.patch.txt patch to Mailman/Handlers/Decorate.py and restart mailman. Then try the post and report what you find in Mailman's 'debug' log. Thanks again, Mark. Here's what shows up in the debug log (email address anonymized to protect the innocent; it was an unremarkable yahoo.com account). $ cat debug Oct 28 05:14:39 2008 (22325) msg_footer type: type 'str' footer type: type 'unicode' footer: ___ You are subscribed to this mailing list as [EMAIL PROTECTED] To edit your subscription options or to unsubscribe, visit: http://mailman.example.com/mailman/options/moxiemail/address%40example.com lcset: us-ascii All best, 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?
First, I was wrong here. I was so horrified at the thought of having lost all those old messages that I got the date wrong. It's actually worse than I remembered. The last archive update appears to have happened in early July... not early August. My last backup from the old server was September 28. It took 3 weeks for me to get mailman working again on the new host in multi-domain (virtual host) mode. So there are 3 months worth of archive updates that appear to be lost. I looked close at our 9/28 tar-ball backup from the old server and there seems to be nothing in the qfiles/archive directory at all. Indeed, there's nothing in qfiles/bad, bounces, command, in, news, out, retry or virgin either. Shunt has a few pck files but they all begin on 10/21 which is when mailman started running again on the new server. For the record, I see no evidence the cron for archive updates is running now on the new server either. In fact from your comments, I'd say the pck files in qfiles/shunt strongly suggest that it's NOT running or at least not running correctly. Here's what I see when I look at the current mailman archive/private/listname.mbox directory 4 drwxrwsr-x 2 ourlistmailman4096 2008-10-28 06:34 . 4 drwxrws--- 8 nobody mailman4096 2008-07-10 06:53 .. 0 lrwxrwxrwx 1 root mailman 41 2008-10-28 06:34 arc - /www/ourlist/newtest/mailman archives/ 5624 -rw-r--r-- 1 root mailman 5743206 2008-07-07 06:22 ourlist.mbox Note the date on the ourlist.mbox file. That's the last time the archive process ran successfully. Something is obviously wrong here; but I'm not sure exactly what. Can you advise me, Mark? Thanks. -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 5:51 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] What happened to my archive? Why isn't the archiveprocess running? TGPlatt, WebMaster wrote: I seem to be missing two full months worth of archives. From what I can tell looking at my backups, it appears that the last time the archive process actually ran on our old server was in early August. Then for some reason it stopped funning and thee have been no archive updates since then. I suspect those lost messages aren't really lost at all but are merely caught in some sort of internal blockage in mailman. What I'm trying to figure out here is how to clear the clogged drain pipe and get the archive working again. There are a few possibilities: 1) ArchiveRunner died on the old server in early August. In this case, the messages would be on the old server in the qfiles/arch/ directory. If that is the case, you could just move the contents of that directory to the corresponding directory on the new server and that should do it. 2) Some error was shunting the archived messages in which case they may be in qfiles/shunt/ and they may or may not be in the individual archives/private/listname.mbox/listname.mbox files. If the messages are in qfiles/shunt/, you could just move them and rin bin/unshunt, but you need to be careful as not all the files in qfiles/shunt/ may be messages you want. You can look at these entries with bin/show_qfiles or bin/dumpdb. If the messages are in the listname.mbox files, the easiest thing is probably to rebuild the archives with bin/arch --wipe. When I first installed the backup from the old server to the new one and then checked the list's configuration parameters, I saw some parameters on the Archiving options page that provided for rebuilding the archive. But now those options seem to have disappeared now too. I don't know what you say, but there's nothing in the web Archiving Options page about rebuilding archives. -- 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?
Follow-up to last message. Wasn't sure exactly how to examine the contents of the ourlist.mbox file in /usr/local/mailman/archives/private/ourlist.mbox SO, I opened it with emacs just to see what it contained. The last message in that file is one I posted on July 7th. The prospects of recovering all those missing messages are looking dimmer and dimmer... Sigh! :-( -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 5:51 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] What happened to my archive? Why isn't the archiveprocess running? TGPlatt, WebMaster wrote: I seem to be missing two full months worth of archives. From what I can tell looking at my backups, it appears that the last time the archive process actually ran on our old server was in early August. Then for some reason it stopped funning and thee have been no archive updates since then. I suspect those lost messages aren't really lost at all but are merely caught in some sort of internal blockage in mailman. What I'm trying to figure out here is how to clear the clogged drain pipe and get the archive working again. There are a few possibilities: 1) ArchiveRunner died on the old server in early August. In this case, the messages would be on the old server in the qfiles/arch/ directory. If that is the case, you could just move the contents of that directory to the corresponding directory on the new server and that should do it. 2) Some error was shunting the archived messages in which case they may be in qfiles/shunt/ and they may or may not be in the individual archives/private/listname.mbox/listname.mbox files. If the messages are in qfiles/shunt/, you could just move them and rin bin/unshunt, but you need to be careful as not all the files in qfiles/shunt/ may be messages you want. You can look at these entries with bin/show_qfiles or bin/dumpdb. If the messages are in the listname.mbox files, the easiest thing is probably to rebuild the archives with bin/arch --wipe. When I first installed the backup from the old server to the new one and then checked the list's configuration parameters, I saw some parameters on the Archiving options page that provided for rebuilding the archive. But now those options seem to have disappeared now too. I don't know what you say, but there's nothing in the web Archiving Options page about rebuilding archives. -- 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] Mailman installation with more then 16000 lists
Hello everyone, It appears we hit the 32k-inodes-per-directory limit in ext2fs today, so mailman can't create any new lists. We could of course move the lists to an XFS filesystem, but I was wondering if there is a way to not have mailman create 2 entries in the lists directory for every mailing list (maybe by grouping them in subdirectories or so). Does anyone have an idea? Thanks in advance! -- Thijs Braem Onderwijstechnoloog Onderwijsvernieuwing OnderwijsServiceCentrum Vrije Universiteit Brussel Tel : +32.2629.1249 E-mail: [EMAIL PROTECTED] http://osc.vub.ac.be/ -- If you believe in freedom of speech, you believe in freedom of speech for views you don't like. Goebbels was in favor of freedom of speech for views he liked. So was Stalin. If you're in favor of freedom of speech, that means you're in favor of freedom of speech precisely for views you despise. -- Noam Chomsky -- 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] problem with mailman and postfix
Hi all! I have a problem. When i send a email to my mailing list, i always got this error: *Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from col0-omc2-s9.col0.hotmail.com[65.55.34.83] Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from col0-omc2-s9.col0.hotmail.com[65.55.34.83]: 554 5.7.1 [EMAIL PROTECTED]: Relay access denied; from= [EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= col0-omc2-s9.col0.hotmail.com *How i can repair this? Here is my postfix config: # # ispCP ω (OMEGA) a Virtual Hosting Control System # # @copyright2001-2006 by moleSoftware GmbH # @copyright2006-2008 by ispCP | http://isp-control.net # @versionSVN: $ID$ # @linkhttp://isp-control.net # @authorispCP Team # # @license # This program is free software; you can redistribute it and/or modify it under # the terms of the MPL General Public License as published by the Free Software # Foundation; either version 1.1 of the License, or (at your option) any later # version. # You should have received a copy of the MPL Mozilla Public License along with # this program; if not, write to the Open Source Initiative (OSI) # http://opensource.org | [EMAIL PROTECTED] # # Postfix directory settings; These are critical for normal Postfix MTA functionallity command_directory= /usr/sbin daemon_directory = /usr/lib/postfix # Some common configuration parameters mynetworks_style = host myhostname = kim.v-info.info mydomain = $myhostname smtpd_banner = $myhostname ESMTP ispCP 1.0.0 RC6 OMEGA Managed setgid_group = postdrop # Receiving messages parameters mydestination = $myhostname, $mydomain append_dot_mydomain = no append_at_myorigin = yes local_transport = local virtual_transport= virtual transport_maps = hash:/etc/postfix/ispcp/transport alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases # Delivering local messages parameters mail_spool_directory = /var/mail # Mailboxquota # = 0 for unlimited # = 104857600 for 100 MB mailbox_size_limit = 0 mailbox_command = procmail -a $EXTENSION # Message size limit # = 0 for unlimited # = 104857600 for 100 MB message_size_limit = 0 biff = no recipient_delimiter = + local_destination_recipient_limit = 1 local_recipient_maps = unix:passwd.byname $alias_maps # ispCP Autoresponder parameters ispcp-arpl_destination_recipient_limit = 1 # Delivering virtual messages parameters virtual_mailbox_base = /var/mail/virtual virtual_mailbox_limit= 0 virtual_mailbox_domains = hash:/etc/postfix/ispcp/domains virtual_mailbox_maps = hash:/etc/postfix/ispcp/mailboxes virtual_alias_maps = hash:/etc/postfix/ispcp/aliases, hash:/var/lib/mailman/data/virtual-mailman virtual_minimum_uid = 1004 virtual_uid_maps = static:1004 virtual_gid_maps = static:8 # SASL paramters smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = broken_sasl_auth_clients = yes smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname smtpd_sender_restrictions= reject_non_fqdn_sender, reject_unknown_sender_domain, permit_mynetworks, permit_sasl_authenticated smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:12525, check_policy_service inet:127.0.0.1:6, permit smtpd_data_restrictions = reject_multi_recipient_bounce, reject_unauth_pipelining # TLS parameters; activate, if avaible/used #smtpd_use_tls = yes #smtpd_tls_loglevel = 2 #smtpd_tls_cert_file = /etc/postfix/cert.pem #smtpd_tls_key_file = /etc/postfix/privkey.pem #smtpd_tls_auth_only = no #smtpd_tls_received_header = yes # AMaViS parameters; activate, if available/used #content_filter = amavis:[127.0.0.1]:10024 # Quota support; activate, if available/used #virtual_create_maildirsize
Re: [Mailman-Users] Spam to mailmain list oddity
On Mon, Oct 27, 2008 at 02:10:40PM -0700, Mark Sapiro wrote: My question is why is mail to mailmain@ seemingly getting delivered to [EMAIL PROTECTED] My first guess, assuming you've verified the above by actually sending your own message to [EMAIL PROTECTED], is that your MTA aliases or whatever are piping mail sent to [EMAIL PROTECTED] to /path/to/mail/mailman owner users Nice guess. And it's worse than that. And this also explains why the List-* headers are not added to the email as well. /etc/aliases includes: mailman: users-owner@list domain It's not even hitting mailman. Postfix is used on that machine and it has two alias files: alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases so it's matching in /etc/aliases first. Why that's in /etc/aliase I'm not sure. Have to track that down. Thanks for pointing me in the right direction. -- Bill Moseley [EMAIL PROTECTED] Sent from my iMutt -- 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] Messages shunted with TypeError: decoding Unicode is not supported
Josh Clark wrote: Try applying the attached Decorate.patch.txt patch to Mailman/Handlers/Decorate.py and restart mailman. Then try the post and report what you find in Mailman's 'debug' log. Thanks again, Mark. Here's what shows up in the debug log (email address anonymized to protect the innocent; it was an unremarkable yahoo.com account). $ cat debug Oct 28 05:14:39 2008 (22325) msg_footer type: type 'str' footer type: type 'unicode' footer: ___ You are subscribed to this mailing list as [EMAIL PROTECTED] To edit your subscription options or to unsubscribe, visit: http://mailman.example.com/mailman/options/moxiemail/address%40example.com lcset: us-ascii That narrows it down a bit. What is happening is one of the strings being interpolated into the footer is unicode. The footer is msg_footer = ___ You are subscribed to this mailing list as %(user_address)s To edit your subscription options or to unsubscribe, visit: %(user_optionsurl)s and somehow this '[EMAIL PROTECTED]' is unicode rather than a string. Try the following: Remove the patch from Decorate.py as it isn't needed any more. Then do $ bin/withlist moxiemail Loading list moxiemail (unlocked) The variable `m' is the moxiemail MailList instance for mem in m.getMembers(): ... print repr(m.getMemberCPAddress(mem)) ... The first line above represents a prompt and a withlist command. The next lines are output from withlist ending with a ' ' python prompt. You type what follows the prompt and get a '... ' prompt because the 'for' is incomplete. You type the next line indented, and then just CR to the next prompt. This should be followed by a list of '[EMAIL PROTECTED]' and/or u'[EMAIL PROTECTED]' like addresses ending with a ' ' prompt. Type control-D at this prompt to quit. I'm interested in how many of these addresses are u'...', and how they got to be that way. The above will answer the first question. The attached patch to Decorate.py (applied after removing the other one) will work around the problem, but the real question is how the 'case preserved' addresses got to be unicode in the first place. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan --- f:/test-mailman-2.1/Mailman/Handlers/Decorate.py2008-06-11 15:09:34.0 -0700 +++ f:/test-mailman/Mailman/Handlers/Decorate.py2008-10-28 08:53:30.15625 -0700 @@ -98,8 +98,18 @@ # TK: Try to keep the message plain by converting the header/ # footer/oldpayload into unicode and encode with mcset/lcset. # Try to decode qp/base64 also. -uheader = unicode(header, lcset, 'ignore') -ufooter = unicode(footer, lcset, 'ignore') +if isinstance(header, str): +uheader = unicode(header, lcset, 'ignore') +elif isinstance(header, unicode): +uheader = header +else: +assert False, 'Adding msg_header: header not string or unicode' +if isinstance(footer, str): +ufooter = unicode(footer, lcset, 'ignore') +elif isinstance(footer, unicode): +ufooter = footer +else: +assert False, 'Adding msg_footer: footer not string or unicode' try: oldpayload = unicode(msg.get_payload(decode=True), mcset) frontsep = endsep = u'' -- 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] problem with mailman and postfix
William Lebel wrote: I have a problem. When i send a email to my mailing list, i always got this error: *Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from col0-omc2-s9.col0.hotmail.com[65.55.34.83] Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from col0-omc2-s9.col0.hotmail.com[65.55.34.83]: 554 5.7.1 [EMAIL PROTECTED]: Relay access denied; from= [EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= col0-omc2-s9.col0.hotmail.com *How i can repair this? I think virtual_alias_domains = virtual-info.eu in your Postfix config will do it. -- 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] Command output: local: fatal: execvp/usr/local/mailman/mail/mailman: Permission denied )
/etc/aliases is the location of my aliases file and that's where postfix is pointing. I cannot change the owner to the aliases and aliases.db or else I can't run newaliases. I ran ./configure --with-mail-god=nobody and I have default_privs = nobody Any other suggestions? Jewel - Original Message - From: Mark Sapiro [EMAIL PROTECTED] Date: Monday, October 27, 2008 5:32 pm Subject: Re: [Mailman-Users] Command output: local: fatal: execvp/usr/local/mailman/mail/mailman: Permission denied ) To: [EMAIL PROTECTED], mailman-users@python.org [EMAIL PROTECTED] wrote: When I create a new list and put my email address, I do receive a confirmation. I can deliver mail as root also from my server. Once I try and post to the list is when nothing happens, just a bounce back saying the Connection is refused. The only clue I can see if the following in my maillog: Command output: local: fatal: execvp /usr/local/mailman/mail/mailman: Permission denied I read the above error means postfix does not have permissions to accessthe mailman wrappers. Before I post this question to a postfix listserv, I wanted to confirmmy permissions were correct. Here is what I have for /usr/local/mailman/mail/mailman: -rwxrwsr-x 1 mailman mailman 16887 Oct 15 09:10 mailman My aliases.db file is owned by root. I think this is the problem. If you have Mailman/Postfix integration, so that Mailman's aliases are in Mailman's data/aliases and data/aliases.db files, aliases.db needs to be owned by mailman, not root. I am running... Red Hat 5.1 Postfix 2.3.3 Mailman 2.1.11 Also, when I run check_perms - f as root it says no problems found That's a flaw in check_perms. It only checks group on files and directories, not owner, because owner doesn't matter except for this one file. Also, see the FAQ at http://wiki.list.org/x/tYA9 in case you run intoa group mismatch after fixing the owner. -- 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] clue to moderation
Hi friends. With Mailman, is there any clue in a received message header that the original message went through moderation and was approved -- as opposed to being sent unmoderated? Also, I sent this previously through my From address' smtp server, but python.org tagged it as spam, which seems pretty aggressive considering that I am enrolled on the list server. Could not deliver message to the following recipient(s): Failed Recipient: mailman-users@python.org Reason: Remote host said: 553 rejected, message looks like spam. -- The header and top 20 lines of the message follows -- Received: from adsl-75-45-6-67.dsl.scrm01.sbcglobal.net [75.45.6.67] by homepower.com with SMTP; Tue, 28 Oct 2008 10:49:35 -0700 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 28 Oct 2008 10:47:25 -0700 To: mailman-users@python.org From: Michael Welch [EMAIL PROTECTED] Subject: clue to moderation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi friends. With Mailman, is there any clue in a received message header that the original message went through moderation and was approved -- as opposed to being sent unmoderated? -- 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] clue to moderation
Michael Welch With Mailman, is there any clue in a received message header that the original message went through moderation and was approved -- as opposed to being sent unmoderated? There is an X-Mailman-Approved-At: header. Also, I sent this previously through my From address' smtp server, but python.org tagged it as spam, which seems pretty aggressive considering that I am enrolled on the list server. I'm sure the spam filtering at bag.python.org doesn't check list membership. In any case, if you have questions or issues with the spam filters at bag.python.org, I think you'd need to address them to [EMAIL PROTECTED] -- 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] Command output: local: fatal:execvp/usr/local/mailman/mail/mailman: Permission denied )
[EMAIL PROTECTED] wrote: /etc/aliases is the location of my aliases file and that's where postfix is pointing. I cannot change the owner to the aliases and aliases.db or else I can't run newaliases. I ran ./configure --with-mail-god=nobody and I have default_privs = nobody Any other suggestions? Set up Mailman-Postfix integration per http://www.list.org/mailman-install/node13.html. However, I don't understand why you are getting the permissions denied with what you have. Even 'nobody' should be able to execute /usr/local/mailman/mail/mailman. If your aliases are in /etc/aliases.db and that file is owned by root, Postfix should run the pipe as the default_privs user, so it should work as is. Are all the directories in the path /usr/local/mailman/mail/mailman o+x? -- 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] Command output: local: fatal: execvp/usr/local/mailman/mail/mailman: Permission denied )
[EMAIL PROTECTED] wrote, in reply: /etc/aliases is the location of my aliases file and that's where postfix is pointing. I cannot change the owner to the aliases and aliases.db or else I can't run newaliases. I ran ./configure --with-mail-god=nobody and I have default_privs = nobody Any other suggestions? There should be two aliases files - one supplied by the OS (and/or Postfix), and one created by Mailman. You need to define both to Postfix in main.cf in the alias_maps = hash:aliasfile1 hash:aliasfile2 line. Keep the permissions on the system file as they are, so that the newaliases command will work. The permissions on the Mailman-generated aliases file need to match the --with-mail-gid= parameter on the ./configure statement. I just noticed that on my Ubuntu system there is no system aliases file, so I do not have a definition for postmaster, MAILER-DAEMON, and the other common userids. And I do not want to include those definitions in the Mailman-generated aliases file, as a re-generation of that file would proably omit my manual additions. -- 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
Re: [Mailman-Users] Messages shunted with TypeError: decoding Unicode is not supported
Thanks again, Mark, this is all *very* appreciated. I'm interested in how many of these addresses are u'...', and how they got to be that way. Of the 1639 e-mail addresses, 349 are u'...' I don't have any great ideas about what might be out of the ordinary about my installation. I've never made any mods to the Mailman scripts. I *have* used custom html templates (charset=utf-8), but I don't think that this would affect the character encoding on the server side, would it? If you'd like to take a look: http://mailman.globalmoxie.com/mailman/listinfo/moxiemail However, the majority of subscriptions come via a script that I set up to send subscribe commands via email to the list. It accepts an email address in a web form and sends it along as a subscribe command to moxiemail-requests. Here's a sample (with domains changed to example.com): -- Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: by houdini.example.com (Postfix, from userid 536) id 26E3A312869A; Tue, 28 Oct 2008 14:38:07 -0500 (CDT) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: subscribe [EMAIL PROTECTED] Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: [EMAIL PROTECTED] Date: Tue, 28 Oct 2008 14:38:07 -0500 (CDT) subscribe [EMAIL PROTECTED] -- I'm happy to do any tests or troubleshooting that might be helpful to get at the root problem. The attached patch to Decorate.py (applied after removing the other one) will work around the problem. Excellent, thanks! A quick question before I try it: I've now tried to send this message a few times; is it possible that these attempts were successfully mailed to some portion of the list (e.g., some of the non- unicode addresses)? If it's an indicator, the last address that showed up with the bin/withlist commands that you suggested was also the same address that showed up in the message footer for the debug patch that you originally sent (and, I presume, the address that caused the error). (If it's likely that some significant number of people have gotten several copies of the message, I just want to add an apology for the repeats before mailing it again. Either way, I'll give the patch a spin in the next 24 hours.) Thanks again for all of the speedy, detailed help with this. All best, 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] Command output: local: fatal: execvp/usr/local/mailman/mail/mailman: Permission denied )
Here is what main.cf has as far as alias settings: alias_maps = hash:/etc/aliases When I run a locate aliases here are all the places it exists and am not sure what to put: /etc/aliases /etc/aliases.db /etc/alsa/cards/aliases.alisp /etc/alsa/cards/aliases.conf /etc/alternatives/mta-aliasesman /etc/alternatives/mta-newaliases /etc/alternatives/mta-newaliasesman /etc/fonts/conf.avail/30-amt-aliases.conf /etc/fonts/conf.avail/30-urw-aliases.conf /etc/fonts/conf.d/30-aliases-fedora.conf /etc/fonts/conf.d/30-amt-aliases.conf /etc/fonts/conf.d/30-urw-aliases.conf /etc/pango/pangox.aliases /etc/sysconfig/network-scripts/ifup-aliases /home/mailman/mailman-2.1.11/bin/genaliases /home/mailman/mailman-2.1.11/build/bin/genaliases /home/mailman/mailman-2.1.11/misc/JapaneseCodecs-1.4.11/build/lib.linux-i686-2.4/japanese/aliases /home/mailman/mailman-2.1.11/misc/JapaneseCodecs-1.4.11/build/lib.linux-i686-2.4/japanese/aliases/__init__.py /home/mailman/mailman-2.1.11/misc/JapaneseCodecs-1.4.11/japanese/aliases /home/mailman/mailman-2.1.11/misc/JapaneseCodecs-1.4.11/japanese/aliases/__init__.py /home/mailman/mailman-2.1.11/misc/KoreanCodecs-2.0.5/build/lib.linux-i686-2.4/korean/aliases.py /home/mailman/mailman-2.1.11/misc/KoreanCodecs-2.0.5/korean/aliases.py /usr/bin/newaliases /usr/bin/newaliases.postfix /usr/bin/newaliases.sendmail /usr/include/aliases.h /usr/lib/python2.4/encodings/aliases.py /usr/lib/python2.4/encodings/aliases.pyc /usr/lib/python2.4/encodings/aliases.pyo /usr/lib/python2.4/site-packages/japanese/aliases /usr/lib/python2.4/site-packages/japanese/aliases/__init__.py /usr/lib/python2.4/site-packages/japanese/aliases/__init__.pyc /usr/lib/python2.4/site-packages/japanese/aliases/__init__.pyo /usr/lib/python2.4/test/doctest_aliases.py /usr/lib/python2.4/test/doctest_aliases.pyc /usr/lib/python2.4/test/doctest_aliases.pyo /usr/local/mailman/bin/genaliases /usr/local/mailman/pythonlib/japanese/aliases /usr/local/mailman/pythonlib/japanese/aliases/__init__.py /usr/local/mailman/pythonlib/japanese/aliases/__init__.pyc /usr/local/mailman/pythonlib/korean/aliases.py /usr/local/mailman/pythonlib/korean/aliases.pyc /usr/sbin/praliases /usr/share/X11/xkb/keycodes/aliases /usr/share/doc/Deployment_Guide-en-US-5.2/images/neat-aliases.png /usr/share/doc/bash-3.2/startup-files/Bash_aliases /usr/share/doc/bash-3.2/startup-files/apple/aliases /usr/share/hwdata/videoaliases /usr/share/hwdata/videoaliases/apm.xinf /usr/share/hwdata/videoaliases/ark.xinf /usr/share/hwdata/videoaliases/ast.xinf /usr/share/hwdata/videoaliases/ati.xinf /usr/share/hwdata/videoaliases/chips.xinf /usr/share/hwdata/videoaliases/cirrus.xinf /usr/share/hwdata/videoaliases/cyrix.xinf /usr/share/hwdata/videoaliases/glint.xinf /usr/share/hwdata/videoaliases/i128.xinf /usr/share/hwdata/videoaliases/i740.xinf /usr/share/hwdata/videoaliases/i810.xinf /usr/share/hwdata/videoaliases/mga.xinf /usr/share/hwdata/videoaliases/neomagic.xinf /usr/share/hwdata/videoaliases/nsc.xinf /usr/share/hwdata/videoaliases/nv.xinf /usr/share/hwdata/videoaliases/r128.xinf /usr/share/hwdata/videoaliases/radeon.xinf /usr/share/hwdata/videoaliases/radeon_tp.xinf /usr/share/hwdata/videoaliases/s3.xinf /usr/share/hwdata/videoaliases/s3virge.xinf /usr/share/hwdata/videoaliases/savage.xinf /usr/share/hwdata/videoaliases/siliconmotion.xinf /usr/share/hwdata/videoaliases/sis.xinf /usr/share/hwdata/videoaliases/tdfx.xinf /usr/share/hwdata/videoaliases/trident.xinf /usr/share/hwdata/videoaliases/tseng.xinf /usr/share/hwdata/videoaliases/vga.xinf /usr/share/hwdata/videoaliases/via.xinf /usr/share/hwdata/videoaliases/vmware.xinf /usr/share/hwdata/videoaliases/voodoo.xinf /usr/share/man/man1/newaliases.1.gz /usr/share/man/man1/newaliases.postfix.1.gz /usr/share/man/man1/newaliases.sendmail.1.gz /usr/share/man/man5/aliases.5.gz /usr/share/man/man5/aliases.postfix.5.gz /usr/share/man/man5/aliases.sendmail.5.gz /usr/share/man/man8/praliases.8.gz /usr/share/mime/aliases /usr/share/system-config-network/help/network-aliases.html /usr/share/system-config-network/help/figs/neat-aliases.png /usr/share/vim/vim70/ftplugin/mailaliases.vim /usr/share/vim/vim70/syntax/mailaliases.vim Jewel - Original Message - From: [EMAIL PROTECTED] (Barry Finkel) Date: Tuesday, October 28, 2008 2:43 pm Subject: Re: [Mailman-Users] Command output: local: fatal: execvp/usr/local/mailman/mail/mailman: Permission denied ) To: Mailman-Users@python.org [EMAIL PROTECTED] wrote, in reply: /etc/aliases is the location of my aliases file and that's where postfixis pointing. I cannot change the owner to the aliases and aliases.db or else I can't run newaliases. I ran ./configure --with-mail-god=nobody and I have default_privs = nobody Any other suggestions? There should be two aliases files - one supplied by the OS (and/or Postfix), and one created by Mailman. You need to define both to Postfix in main.cf in the alias_maps = hash:aliasfile1 hash:aliasfile2 line. Keep the
Re: [Mailman-Users] Messages shunted with TypeError: decodingUnicode is not supported
Josh Clark wrote: Thanks again, Mark, this is all *very* appreciated. I'm interested in how many of these addresses are u'...', and how they got to be that way. Of the 1639 e-mail addresses, 349 are u'...' I don't have any great ideas about what might be out of the ordinary about my installation. 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? I've never made any mods to the Mailman scripts. I *have* used custom html templates (charset=utf-8), but I don't think that this would affect the character encoding on the server side, would it? This is not an encoding issue. It's complicated, but unicode is an abstract representation of characters. Unicode entities are encoded into strings of characters (or bytes in the case of some encodings that represent a character as multiple bytes) using some character encoding like us-ascii or utf-8 or iso-8859-1, etc., and strings can be decoded into unicode. The issue here is not one of the character encoding of the email address. It's that some of the email addresses (or at least the 'case preserved' addresses) are stored as unicode objects instead of strings. If you'd like to take a look: http://mailman.globalmoxie.com/mailman/listinfo/moxiemail However, the majority of subscriptions come via a script that I set up to send subscribe commands via email to the list. It accepts an email address in a web form and sends it along as a subscribe command to moxiemail-requests. Here's a sample (with domains changed to example.com): -- Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: by houdini.example.com (Postfix, from userid 536) id 26E3A312869A; Tue, 28 Oct 2008 14:38:07 -0500 (CDT) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: subscribe [EMAIL PROTECTED] Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: [EMAIL PROTECTED] Date: Tue, 28 Oct 2008 14:38:07 -0500 (CDT) subscribe [EMAIL PROTECTED] -- I'm happy to do any tests or troubleshooting that might be helpful to get at the root problem. Thanks. I'll try to think of what to do. One thing, if you trust me to respect the confidentiality of your list membership, you can send me off-list a copy of lists/moxiemail/config.pck. The attached patch to Decorate.py (applied after removing the other one) will work around the problem. Excellent, thanks! A quick question before I try it: I've now tried to send this message a few times; is it possible that these attempts were successfully mailed to some portion of the list (e.g., some of the non- unicode addresses)? If it's an indicator, the last address that showed up with the bin/withlist commands that you suggested was also the same address that showed up in the message footer for the debug patch that you originally sent (and, I presume, the address that caused the error). (If it's likely that some significant number of people have gotten several copies of the message, I just want to add an apology for the repeats before mailing it again. Either way, I'll give the patch a spin in the next 24 hours.) When we had the debug patch, there appeared to be only one entry in the debug log. If that mail had been successfully delivered, the address that caused the failure would have been preceeded by debug log entries for the successful ones. In any case, each failure resulted in a .pck file in the shunt queue. Those files should still be there. If you dump them with bin/dumpdb, you will see the message as the first object in the file and the metadata as the second object. The metadata should contain an 'undelivered' list containing all those who didn't get that message. -- 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] Command output: local: fatal:execvp/usr/local/mailman/mail/mailman: Permission denied )
[EMAIL PROTECTED] wrote: Here is what main.cf has as far as alias settings: alias_maps = hash:/etc/aliases When I run a locate aliases here are all the places it exists and am not sure what to put: snip What Barry is talking about may or may not be exactly what is described in the installation manual at http://www.list.org/mailman-install/node13.html, but he is suggesting that you have your Mailman aliases separate from the system aliases. If you follow the manual, Mailman will maintain the aliases automatically in it's data/ directory. -- 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: 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 (10592) Archive file access failure: /usr/local/mailman/archives/private/ourlist.mbox/ourlist.mbox [Errno 13] Permission denied: '/usr/local/mailman/archives/private/ourlist.mbox/ourlist.mbox' Jul 09 07:29:22 2008 (10592) Uncaught runner exception: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/ourlist .mbox/ourlist.mbox' .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 shoud be group writable. snip Sep 25 21:09:31 2008 (16599) SHUNTING: 1222394969.723012+6122e5f84bb97875a24698a159961936bed8802b Sadly, 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 Here are the first and last error in the current error file: Oct 18 10:43:54 2008 mailmanctl(25124): Site list is missing: mailman Oct 18 10:43:54 2008 (25124) Site list is missing: mailman Oct 18 18:38:42 2008 (14433) admin.py access for non-existent list: ourlist Oct 18 18:39:34 2008 (14458) admin.py access for non-existent list: ourlist Oct 18 20:34:08 2008 (19034) admin.py access for non-existent list: ourlist Oct 20 08:58:31 2008 (9822) admin.py access for non-existent list: ourlist Oct 21 22:33:46 2008 (1431) Uncaught runner exception: [Errno 13] Permission den ied: '/usr/local/mailman/archives/private/ourlist/index.html' Oct 21 22:33:46 2008 (1431) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) ... Oct 28 10:09:30 2008 (2589) Uncaught runner exception: [Errno 13] Permission den ied: '/usr/local/mailman/archives/private/ourlist/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
