Re: [Mailman-Users] Lists stop working
On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote: Did you ever find a solution to this issue? I realize that this is a really old posting: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=Niklas.Nikitin at xxx http://mail.python.org/mailman/listinfo/mailman-users , size=502, class=0, nrcpts=1, msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx http://mail.python.org/mailman/listinfo/mailman-users , proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=nicke-test at xxx http://mail.python.org/mailman/listinfo/mailman-users (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailman's logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. but I've run into a very similar problem with two mailing lists that are managed using the current release of Mailman. The first symptom was that messages sent to the mailing lists were not distributed to the list, and did not show up in the list archive. After my ISP reinstalled Mailman, messages to the list started to show up in the list archive again. But the messages were still not distributed to members of the list. We found that if we add a new user, then a message to the list *is* delivered to that new user, but still not to any of the existing users. If the *new* user posts a message, that message appears in the list archive and the message is delivered to the entire mailing list. There doesn't seem to be a way to dump and reload the mailing list that preserves all per-list-member configuration options, so if possible, we'd like to avoid that workaround. Especially if it only works temporarily. Any insight / help / pointers appreciated. I had an oddity which may/maynot have some relevance.. We subscribed someone to a list with a specific email address. They confirmed the subscription using web interface. Subsequently mails from that member were received in the way you described and were passed to mailman but did not get posted to the list. I suggest you examine the headers of incoming mails,as they are intially received, and outgoing mails to those subscribers who are not receiving the mails.. There could be some changes being made to the headers either by the subscribers server or your own that is causing mails to be not delivered. david -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: Did you ever find a solution to this issue? I realize that this is a really old posting: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=Niklas.Nikitin at xxx http://mail.python.org/mailman/listinfo/mailman-users , size=502, class=0, nrcpts=1, msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx http://mail.python.org/mailman/listinfo/mailman-users , proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=nicke-test at xxx http://mail.python.org/mailman/listinfo/mailman-users (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailman's logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. but I've run into a very similar problem with two mailing lists that are managed using the current release of Mailman. The first symptom was that messages sent to the mailing lists were not distributed to the list, and did not show up in the list archive. After my ISP reinstalled Mailman, messages to the list started to show up in the list archive again. But the messages were still not distributed to members of the list. We found that if we add a new user, then a message to the list *is* delivered to that new user, but still not to any of the existing users. If the *new* user posts a message, that message appears in the list archive and the message is delivered to the entire mailing list. There doesn't seem to be a way to dump and reload the mailing list that preserves all per-list-member configuration options, so if possible, we'd like to avoid that workaround. Especially if it only works temporarily. Any insight / help / pointers appreciated. today I have a similar (or the same?) problem. Running Mailman V2.1.9. Symptoms in my case: a new member (added with the command line utility add_members) is subscribed properly, the associated mail address gets a welcome message (so far so good), but mail to the mailing list arrives at Mailman, but is not distributed to the new user. I tried adding a second user, but the same problem. I have checked a number of things from the FAQ to diagnose the problem but I see nothing unusual. No traces in the logs directory. And I'm sure Mailman has accepted the mail for further processing (I can see from the mail logs). How can I trace these messages in Mailman? I looked in the qfiles/ subdirectories, but no files there... Is there any logging/debugging that can be turned on to see what steps Mailman takes to a) process the mail, (b) expand the mailing list and c) deliver the mail to the mail server. SMTP settings are default. Or is there any utility to quickly see what messages are in the Mailman queue for processing? /rolf -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Rolf E. Sonneveld writes: today I have a similar (or the same?) problem. Running Mailman V2.1.9. Symptoms in my case: a new member (added with the command line utility add_members) is subscribed properly, the associated mail address gets a welcome message (so far so good), but mail to the mailing list arrives at Mailman, but is not distributed to the new user. I tried adding a second user, but the same problem. Have posts ever been delivered to any user? If not, the most likely Mailman-related problem is that due to your settings, the posts are being held. Have you checked the moderation interface? More likely IMO is that Mailman never received the posts because of failure to start Mailman's qrunners properly, or misconfiguration of the MTA. I have checked a number of things from the FAQ to diagnose the problem but I see nothing unusual. No traces in the logs directory. And I'm sure Mailman has accepted the mail for further processing (I can see from the mail logs). On the contrary, if Mailman isn't writing to its logs and there's nothing in the qfiles directories, it seems very likely that Mailman has never received the messages. Are there entries in logs/qrunner showing that all qrunners are working? Mine says: Oct 18 17:14:29 2006 (15648) ArchRunner qrunner started. Oct 18 17:14:30 2006 (15649) BounceRunner qrunner started. Oct 18 17:14:33 2006 (15650) CommandRunner qrunner started. Oct 18 17:14:35 2006 (15653) NewsRunner qrunner started. Oct 18 17:14:35 2006 (15655) VirginRunner qrunner started. Oct 18 17:14:35 2006 (15651) IncomingRunner qrunner started. Oct 18 17:14:35 2006 (15654) OutgoingRunner qrunner started. Oct 18 17:14:36 2006 (15656) RetryRunner qrunner started. Does ps show that they are still running? Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Are there really no logs at all? If there are logs, what do they say? How can I trace these messages in Mailman? I looked in the qfiles/ subdirectories, but no files there... Have you checked your MTA's queue? Based on your statements that there is nothing in the logs and nothing in the queues, I have to believe they're never getting to Mailman at all. Is there any logging/debugging that can be turned on No; the logs described plus the qfiles contain all the information that you should need for problems related to the delivery pipeline. Or is there any utility to quickly see what messages are in the Mailman queue for processing? To see what's there, I just use ls -R /var/lib/mailman/qfiles (YMMV depending on where Mailman is installed). To examine the qfiles themselves, use cd /var/lib/mailman; bin/show_qfiles qfiles/in/* (again, the cd directory will vary according to your installation). -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Quick question about spam filtering
Lately, our Mailman lists have been getting more self-addressed junk messages -- that is, [EMAIL PROTECTED] gets spam that is spoofing [EMAIL PROTECTED] as the sender. In the spam filtering interface, what would be the easiest regex combination to ensure that, as an example, [EMAIL PROTECTED] would automatically discard any self-addressed messages in this manner? One of the related complications seems to be that the sender (From) name identity is always different -- but the @ address is always the same, of course. This is probably really easy, but I'm still a regular expression novice. Thanks, Jason _ Jason LaMar Director of Information Services Ohio Wesleyan University | Delaware, OH 43015 IP Tel: 740-368-3131 | AIM/Yahoo IM: jasonrlamar Fax: 740-368-3272 | Web: http://www.owu.edu/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] certificates for subscribers..application to provide and check???
Hi Before starting to build it I am wondering if anyone knows of a port that will do what I require. I am reluctant (and too lazy chuckles) to want to reinvent the wheel!!! I want to offer maillist users a certificate, signed by us, that they will be asked to use to certify their identity when posting to the list. I want them to apply and obtain the certificate using the the maillist web site and for us to keep the records in a mysql database. I would also like to incorporate certificate checking as part of the process of validating incoming mails presented for posting to a list. For some lists, where we have a means of being able to be sure of user identity and a security need, I want to reject uncertified mails. In other cases I simply want to add a warning in the first line of the Body when the mail is uncertified. Thanks in advance david -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Stephen J. Turnbull wrote: Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. In spite of the minor corrections above, Stephen's advice is excellent. To elaborate on Rolf's question about how Mailman processes a post. Assuming a standard configuration where the MTA delivers to the mail/mailman wrapper. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. 2) IncomingRunner picks up the queue entry from qfiles/in and passes it through a pipeline of handlers (GLOBAL_PIPELINE - defined in Defaults.py, possibly modified in mm_cfg.py - unless the list defines a pipeline attribute to override it). The initial handlers check header_filter_rules, look for an Approved: header and possibly generate an autoresponse. The next set of handlers checks for moderation and other holds and does content filtering, emergency moderation and topic flagging. Any of these handlers can raise exceptions to request IncomingRunner to discard, reject or hold the message at that point. Discards and holds are logged in the vette log. Rejects are not logged, but result in a reject message to the poster. Any other exceptions cause the message to be moved to qfiles/shunt and the exception is logged in the error log. The next set of handlers determines the recipient addresses and possibly removes and/or modifies some message headers. Then handlers add the message to lists/listname/digest.mbox if the list is digestable (and possibly trigger a digest on size), add the message to qfiles/archive for processing by ArchRunner, possibly add the message to qfiles/news for processing by NewsRunner, update the list's last_post_time, send an acknowledgement to the poster if requested, and add the message to qfiles/out for processing by OutgoingRunner. 3) ArchRunner picks up the queue entry from qfiles/archive and adds it the the list's archive. 4)NewsRunner picks up the queue entry from qfiles/news and delivers it to Usenet. 5)OutgoingRunner picks up the queue entry from qfiles/out and calls SMTPDirect to deliver it to the outgoing MTA via SMTP. SMTPDirect logs posts to the post log and logs a bit more detail to the smtp log. Any SMTP failures are logged to the smtp-failure log and treated as bounces or queued for retry as appropriate. 6) Any unanticipated exceptions in any of the runners cause the message to be moved to qfiles/shunt and the exception to be logged in the error log. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Server migration problems
Aaron Crosman wrote: The archives problem persists. You gave me the right place to look here as well. The archives are all owned by list (group list), but the private archives have restricted access that blocks other users from getting in: ls of /var/lib/mailman/archives: drwxrws--- 200 list list 8.0K 2007-04-25 14:26 private drwxrwsr-x 2 list list 4.0K 2007-04-25 14:23 public I think this is OS dependent, but in most cases, permissions on archives/private need to be 'drwxrws--x'. It is the o+x that is critical for public archive access. archives/public/listname is a symlink to archives/private/listname, and archives/private/listname is world readable, but it still can't be accessed by others, at least in most *nix flavors, unless archives/private/ is world searchable. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Server migration problems
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 10:31 PM To: Aaron Crosman; mailman-users@python.org Subject: Re: [Mailman-Users] Server migration problems - Original Message --- Subject: [Mailman-Users] Server migration problems From: Aaron Crosman [EMAIL PROTECTED] Date: Thu, 26 Apr 2007 14:22:19 -0400 To: mailman-users@python.org I know this comes up all the time, but having carefully reviewed the FAQ and archives, I still haven't been able to solve my problem. I'm working on migrating my mailman setup from an old SuSE server to a new Debian (4.0) server. For the most part everything has gone smoothly, but the existing lists have a couple of problems I can't find the cause. I moved the lists, archive, and data directories from the old server, and ran update, check_perms and check_db on all the lists. If I run list_lists, mailman sees all the lists just fine, but when just the web interface I don't see anything. I naturally assumed that had somehow become private during the move, so I exported the configuration of one of them, and saw advertised = True and while I know in python it shouldn't matter, I went ahead and updated it to be advertised = 1, no difference. If I browse to the list's admin interface directly it seems to work. This certainly seems like FAQ 4.62 to me http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp. Have you run fix_url? I'm also having trouble getting into the archives. The files are there, and the sym-links are correct but the permissions seem to be wrong. And what are they? And what's in the web server's error log? I'm assuming I'm having a problem similar to the advertising (that mm seems to be over-tightening permissions somewhat), but I can't find the root cause. Any suggestions on where to look? Look at the permissions and whether the web server is allowed to follow symlinks, and if all that is OK, it might be a SeLinux or other kind of security polict issue. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Thanks, you were right on about the domain problem. I looked right passed it, since the server will end up at the same domain, but currently I'm accessing by IP address (I hosts file update on my local machine solved that problem). The archives problem persists. You gave me the right place to look here as well. The archives are all owned by list (group list), but the private archives have restricted access that blocks other users from getting in: ls of /var/lib/mailman/archives: drwxrws--- 200 list list 8.0K 2007-04-25 14:26 private drwxrwsr-x 2 list list 4.0K 2007-04-25 14:23 public A sample from the private directory is: drwxrwsr-x 4 list list 4.0K 2007-04-25 14:18 itd_test Apache's error log: [Fri Apr 27 11:42:14 2007] [error] [client 172.17.201.205] Symbolic link not allowed or link target not accessible: /var/lib/mailman/archives/public/itd_test, referer: http://server.org/mailman/listinfo/itd_test I can't browse the file system (in bash) to those directories. I did double check the links in public as root, and they do work just fine, so I'm at a permissions problem. What should the perms here be? Or am I missing something else? Aaron -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Quick question about spam filtering
Jason LaMar In the spam filtering interface, what would be the easiest regex combination to ensure that, as an example, [EMAIL PROTECTED] would automatically discard any self-addressed messages in this manner? In header_filter_rules, put the following regexp. ^from:[EMAIL PROTECTED] This will match a header beginning with From: (these regexps are matched case insensitively) followed by anything followed by the whitespace delimited email address. See http://docs.python.org/lib/re-syntax.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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] multiple list in the To: field
I have 12 school list that at times I need to post the same message to ALL the list but the server rejects it thinking its spam. Is there an option that I can turn off or is there a way to send to 12 mailman list all at once? Thank you! -Tam -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Mark Sapiro writes: Stephen J. Turnbull wrote: When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. Ah, OK ... the 1 recips logs I'm seeing are mass signups and perhaps bounce checks. Sorry for the inaccuracy. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Quick question about spam filtering
Mark Sapiro writes: In header_filter_rules, put the following regexp. ^from:[EMAIL PROTECTED] Isn't that going to lose on (1) Bogus Name [EMAIL PROTECTED] and on (2) ... [EMAIL PROTECTED] ? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] maiman, problem with greek characters
X-Faculty of Social Sciences-MailScanner-Information: Please contact the ISP for more information X-Faculty of Social Sciences-MailScanner: Found to be clean X-Faculty of Social Sciences-MailScanner-From: [EMAIL PROTECTED] X-Spam-Status: No Hi, I have installed the latest version of mailman in a mail server running postfix. The problem is with emails that contain greek characters. If the encoding is iso-8859-7 or windows-1253, all the body text is encoded as base64. The result of it is that the recipients cannot read the received emails. In case a user sends an email with multipart/mixed encoding everything is ok. I've added a new line in Defauls.py containing the iso-8859-7 but it does not work. Does anyone have a better idea? Thanks in advance, Alexandros -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Server migration problems
Hi All-- On 4/27/07, Aaron Crosman [EMAIL PROTECTED] wrote: Apache's error log: [Fri Apr 27 11:42:14 2007] [error] [client 172.17.201.205] Symbolic link not allowed or link target not accessible: /var/lib/mailman/archives/public/itd_test, referer: http://server.org/mailman/listinfo/itd_test I can't browse the file system (in bash) to those directories. I did double check the links in public as root, and they do work just fine, so I'm at a permissions problem. What should the perms here be? Or am I missing something else? Unless I'm missing something, this is an Apache configuration problem. It both has to know about the mailman directories and be allowed to follow symbolic links. Permissions have to be correct yes, but if Apache can't follow links then the permissions are moot. Include this directive in your httpd.conf file: Options FollowSymLinks You must provide it for any directory you need to put symlinks in. For example: Alias /icons/ /usr/share/apache2/icons/ Directory /usr/share/apache2/icons Options FollowSymLinks blah blah blah ... /Directory Of course, the directories listed in httpd.conf are dependent on your *nix, as is the location (and name) of the httpd.conf file. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] multiple list in the To: field
Tamakh wrote: I have 12 school list that at times I need to post the same message to ALL the list but the server rejects it thinking its spam. Rejects or Holds? Is there an option that I can turn off or is there a way to send to 12 mailman list all at once? Set Privacy options-Recipient filters-max_num_recipients to a number 12 or to 0 for no limit. Or create an umbrella list with the 12 lists as members and post to the umbrella. Search the FAQ wizard http://www.python.org/cgi-bin/faqw-mm.py for umbrella. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] certificates for subscribers..application to provide and check???
On 4/27/07, David Southwell wrote: For some lists, where we have a means of being able to be sure of user identity and a security need, I want to reject uncertified mails. In other cases I simply want to add a warning in the first line of the Body when the mail is uncertified. Everything you've talked about is completely outside the realm of Mailman. The certificate database creation/management system (with web user interface), the certificate database checking system (within the MTA), etc I'm not sure that there's anything that we can do to help you with any of these things. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] maiman, problem with greek characters
On 4/27/07, [EMAIL PROTECTED] wrote: I have installed the latest version of mailman in a mail server running postfix. The problem is with emails that contain greek characters. If the encoding is iso-8859-7 or windows-1253, all the body text is encoded as base64. The result of it is that the recipients cannot read the received emails. This is not a Mailman problem. This is caused by either your mail client generating base64, or the message being converted when it hits the MTA. Get the client or the MTA fixed, and Mailman should handle the result just fine. In case a user sends an email with multipart/mixed encoding everything is ok. So what's the problem with having them send multipart/mixed? Keep in mind that your content-transfer-encoding is completely orthogonal to the charset, and both of which are completely orthogonal to the MIME bodypart type. A client or intermediary MTA could change just one of these three things, and some recipients would deal with that change just fine, while others would freak out. Theoretically, all clients should be fine with all possible values in each of these three categories, and they should handle it properly. In practice, most of them are extremely fragile in their handling of these things, and even just looking at them cross-eyed can make them barf and die horribly. Welcome to the wonderful world of MIME. I've added a new line in Defauls.py containing the iso-8859-7 but it does not work. Don't edit Defaults.py. That file will get overwritten in an upgrade. Edit mm_cfg.py instead. Also make sure that you restart Mailman after changes to mm_cfg.py. Note that many changes to mm_cfg.py will only affect lists created after the change is made, and won't have any impact on any existing lists. So, you may need to delete and re-create your list(s) after making changes to mm_cfg.py. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Quick question about spam filtering
Stephen J. Turnbull wrote: Mark Sapiro writes: In header_filter_rules, put the following regexp. ^from:[EMAIL PROTECTED] Isn't that going to lose on (1) Bogus Name [EMAIL PROTECTED] Yes. I totally overlooked . It needs to be ^from:.*[\s[EMAIL PROTECTED]] and on (2) ... [EMAIL PROTECTED] ? No. \s will match end of line (\n or \r). -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Placing a copyright notice in list messages.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? - -- - - |/\/\ /\/\ /\/\ Webster Ridge Farm |http://WebsterRidge.com | |\oo/ \--/ \--/ Brandon and Mary Sussman | (603)648-2595 | |=\/= =\/= =\/= 1482 Pleasant St.| N 43.32558 W 71.70835 | | Sleep Well... Webster, NH, 03303-7613 |19TBJ800015 | - - |Lamb, Poultry, Eggs, Quilts and Web Sites |Think Locally, Buy Locally! | - - -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iQEVAwUBRjJC7NN2DJl/zagkAQLILAf/QH3O9RorXp6qka/VO9fdKWez6ZMbnJqP 0T7+RZ4M5479EUK6Lj5msDWilK6r33wxHRXTnioo3nKfc+o9XJeeqwPQSEpJeLvu Zb8DAOZolbXqryjzP3EmzCBOnsSuXEEtu+BYPG4QnO2PIIN3Mck0vUcwttFEqLhM wRgzF0a1COWBoTHvN3EB4QmzFgW4lwnwKv/fvtKyTXBoAXqRiaSo3HjkaMmlpGFH X9A2TCu+k9Ni/M4BymzSwtS8KU5xMZT3igYgRvZhPhmzF7/efFQdM36JTStCuwuQ IIjtFH4JxISQ525WraoFW+qvG15yfNqvnrzGOEJTCQ5XmgxexhCQBA== =TUox -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] maiman, problem with greek characters
Brad Knowles wrote: On 4/27/07, [EMAIL PROTECTED] wrote: I have installed the latest version of mailman in a mail server running postfix. The problem is with emails that contain greek characters. If the encoding is iso-8859-7 or windows-1253, all the body text is encoded as base64. The result of it is that the recipients cannot read the received emails. This is not a Mailman problem. This is caused by either your mail client generating base64, or the message being converted when it hits the MTA. Actually, it is Mailman (or Python if you prefer). When various processes (scrubbing attachments and/or adding msg_header and/or msg_footer) set the message payload with character set iso-8859-7, the Python email library encodes the payload as base64. Get the client or the MTA fixed, and Mailman should handle the result just fine. Yes! base64 is a standard MIME encoding which the recipient's MUAs should recognize. Why do the recipients have difficulty reading a base64 encoded message? In case a user sends an email with multipart/mixed encoding everything is ok. I notice your list post was sent with Content-Type: text/plain;charset=multipart/mixed This is completely bogus. There is no such character set as multipart/mixed. I don't know if your SquirrelMail MUA did this on its own or you somehow told it to, but it's wrong. The reason this may work to avoid base64 is that Mailman/Python doesn't recognize this charset and treats it as unknown resulting in the messages Content-Transfer-Encoding: being 8bit instead of base64. snipped good advice from Brad I've added a new line in Defauls.py containing the iso-8859-7 but it does not work. Don't edit Defaults.py. That file will get overwritten in an upgrade. Edit mm_cfg.py instead. Absolutely. But, what exactly did you add? Adding arbitrary things that aren't already defined won't do anything because Mailman won't reference them. Adding a new language to the LC_DESCRIPTIONS list via an add_language line without adding all the translated messages and templates for that language will just create a mess. Changing the characterset associated with a language won't affect this issue, because the character set in this case is the character set of the message body, not the character set of the list language. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Placing a copyright notice in list messages.
Brandon Sussman wrote: Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? Not really. You could put the notice in msg_header or msg_footer, but even if the list is personalized, the sender is not one of the available substitutions for these (It could be added by modifying the code in Mailman/Handlers/Decorate.py). Even if you modified the code on Decorate.py to enable a substitution for the sender in the header and footer, it wouldn't appear in the digest version of the message. I think I would do this with a generic sort of header/footer along the lines of posts to this list are copyright by the poster... and mesages in this digest are copyright by the individual posters If you reall want a notice with the poster explicitly named in the notice, I suggest a custom handler (see ) that would add the notice to the message body (or as a separate part as done by Decorate.py for message bodies that can't easily be added to). This way, the notice would also appear in each message in the digest (unless it was a separate part and scrubbed). However, is this even a good idea at all. What if I post something which includes significant material quoted from someone elses post and I don't preserve the copyright from that post. Or I do preserve the copyrights from the quoted material, but the attributions aren't clear. I foresee a post with material from several authors and multiple copyright notices with no clear identification of what is copyright by whom. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] SMS/text messaging
I have some users interested in setting up lists to send out text messages to phones/PDAs. We have figured out that the confirmation messages for subscription do not work on these devices. We figured out that the approve method of subscription works, but the email it sends to let the user know their subscription is waiting is rather long. Has anyone tweaked Mailman to work with these devices? I don't see any patches out there for it. -- Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Placing a copyright notice in list messages.
Mark Sapiro sent the message below at 12:20 4/27/2007: Brandon Sussman wrote: Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? snip However, is this even a good idea at all. What if I post something which includes significant material quoted from someone elses post and I don't preserve the copyright from that post. Or I do preserve the copyrights from the quoted material, but the attributions aren't clear. I foresee a post with material from several authors and multiple copyright notices with no clear identification of what is copyright by whom. End original message. - I've got to agree with Mark, I think it very quickly becomes problematic to do this. It's very common for attributions to get mixed up or be ambiguous in replies, especially in long discussion threads. If somebody is truly concerned about their own copyright protection, that person should be making such a disclaimer on their own as part of their post and such a disclaimer should take a form something like: Except where otherwise indicated, all material in this post is copyright current year poster's name, all rights reserved. The problem with this is that the poster using it must be extremely careful to ensure that all quoted material is indicated unambiguously as being not under the copyright notice. It's fraught with all sorts of legal implications if it is not done correctly. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Placing a copyright notice in list messages.
Mark Sapiro wrote: If you reall want a notice with the poster explicitly named in the notice, I suggest a custom handler (see ) that would add the notice to the message body ... Ooops. That should be If you really want a notice with the poster explicitly named in the notice, I suggest a custom handler (see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.067.htp) that would add the notice to the message body ... -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] SMS/text messaging
On 4/27/07, Anne Ramey wrote: I have some users interested in setting up lists to send out text messages to phones/PDAs. We have figured out that the confirmation messages for subscription do not work on these devices. We figured out that the approve method of subscription works, but the email it sends to let the user know their subscription is waiting is rather long. Has anyone tweaked Mailman to work with these devices? I don't see any patches out there for it. Mailman does Internet e-mail. Are these phones/PDAs doing Internet e-mail? If so, then the mail clients shouldn't have any problems with the messages Mailman is sending out -- I know I don't have any such problems on my Palm Treo 680. Heck, in an emergency I can even handle the web-based moderation queue for Mailman-hosted mailing lists on my Treo -- that's one advantage of a simple web user interface. Now, if these phones/PDAs are doing SMS messages that have been gatewayed from Internet e-mail, then you're talking about a problem with the gateway system, and there may not be a whole lot we can do to help you. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Number of message limits by web hosting services
Many of the web hosting services that offer mailman place a limit on the number of messages/hour that a given domain can deliver. This is presumably done to avoid saturating their servers. If you exceed the limit, they just ignore some of the recipients. Two hosts that we use have 300 and 500 as their limits. We have several largish email lists with several hundred addresses, one of which has ~400. If several people send to one or more of these lists in a given hour or one person sends to several lists at once, some of the recipients don't get the mail intended for them. These hosts recommend using PHPlist instead which has a feature that can control the timing of the messages so as to not exceed the list, but PHPlist doesn't work for members of the list sending mail since it is really designed to be a Newsletter distribution mechanism. Is there any feature (I found nothing in the documentation) in Mailman that would help out here, or are there people on this email list who have found encountered and solved this problem? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Hello, Mark, Mark Sapiro wrote: Stephen J. Turnbull wrote: Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. OK, thus only after the message has been delivered to at least one subscriber (or the first MTA in the chain of delivery to at least one subscriber). When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. In my case there were no entries in smtp nor in smtp-failure. In spite of the minor corrections above, Stephen's advice is excellent. To elaborate on Rolf's question about how Mailman processes a post. Thanks _very much_ for the detailed explanation of the inner working of Mailman. I really appreciate your detailed description! Assuming a standard configuration where the MTA delivers to the mail/mailman wrapper. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. Now here's the problem, I think. The MTA logs the message as being delivered to Mailman (via the wrapper script $MAILMANDIR/mailman/bin/mailman), so from the MTA's point of view it's done. Now, as the sent message cannot be found under qfiles, and as none of the $MAILMANDIR/logs/* files is modified, it seems as if the message disappeared in a black hole. Is there no way to enable debugging in the wrapper script? It would show the first action of Mailman, I assume. 2) IncomingRunner picks up the queue entry from qfiles/in and passes it through a pipeline of handlers (GLOBAL_PIPELINE - defined in Defaults.py, possibly modified in mm_cfg.py - unless the list defines a pipeline attribute to override it). The initial handlers check header_filter_rules, look for an Approved: header and possibly generate an autoresponse. The next set of handlers checks for moderation and other holds and does content filtering, emergency moderation and topic flagging. Any of these handlers can raise exceptions to request IncomingRunner to discard, reject or hold the message at that point. Discards and holds are logged in the vette log. Rejects are not logged, but result in a reject message to the poster. Any other exceptions cause the message to be moved to qfiles/shunt and the exception is logged in the error log. The next set of handlers determines the recipient addresses and possibly removes and/or modifies some message headers. Then handlers add the message to lists/listname/digest.mbox if the list is digestable (and possibly trigger a digest on size), add the message to qfiles/archive for processing by ArchRunner, possibly add the message to qfiles/news for processing by NewsRunner, update the list's last_post_time, send an acknowledgement to the poster if requested, and add the message to qfiles/out for processing by OutgoingRunner. FYI I made sure that the recipients where no digest users. 3) ArchRunner picks up the queue entry from qfiles/archive and adds it the the list's archive. 4)NewsRunner picks up the queue entry from qfiles/news and delivers it to Usenet. 5)OutgoingRunner picks up the queue entry from qfiles/out and calls SMTPDirect to deliver it to the outgoing MTA via SMTP. SMTPDirect logs posts to the post log and logs a bit more detail to the smtp log. Any SMTP failures are logged to the smtp-failure log and treated as bounces or queued for retry as appropriate. 6) Any unanticipated exceptions in any of the runners cause the message to be moved to qfiles/shunt and the exception to be logged in the error log. /rolf -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Rolf E. Sonneveld wrote: Mark Sapiro wrote: One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. OK, thus only after the message has been delivered to at least one subscriber (or the first MTA in the chain of delivery to at least one subscriber). Yes, the first MTA, namely the one on localhost, port 25 unless overridden by SMTPHOST/SMTPPORT in mm_cfg.py. There is no guarantee this MTA has sent the message further. You need to refer the the MTA's logs for that. In my case there were no entries in smtp nor in smtp-failure. So the message didn't get that far. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. Now here's the problem, I think. The MTA logs the message as being delivered to Mailman (via the wrapper script $MAILMANDIR/mailman/bin/mailman), so from the MTA's point of view it's done. Now, as the sent message cannot be found under qfiles, and as none of the $MAILMANDIR/logs/* files is modified, it seems as if the message disappeared in a black hole. Is there no way to enable debugging in the wrapper script? It would show the first action of Mailman, I assume. There are at least two possibilities here. 1) The post was rejected (not held or discarded). A reject is not logged, but there should be an associated entry in Mailman's smtp log with a mailman generated message-id and 1 recipient for the reject message sent to the poster. 2) The wrapper is for a different Mailman installation with a different qfiles directory and probably no qrunners running and probably different log files too. The wrapper itself (I would expect it to be located at $MAILMANDIR/mail/mailman, not $MAILMANDIR/mailman/bin/mailman) has the path to the scripts/ directory compiled in and doesn't have any debug switches. It will invoke the scripts/post script and presumably this happens OK or it will return a failure status to the MTA which would be logged by the MTA. You can add debugging to the scripts/post script. If you look at this script, you will see that it already detects a missing or invalid list name from the wrapper and writes to stderr which is logged to both the post and error logs. You could add some more output, say by adding the last two lines of inq = get_switchboard(mm_cfg.INQUEUE_DIR) inq.enqueue(sys.stdin.read(), listname=listname, tolist=1, _plaintext=1) print sys.stderr, 'Post for %s queued in %s' \ % (listname, mm_cfg.INQUEUE_DIR) If you don't see this in the post and error logs, you are not looking at the right installation or (third possibility) the right log files. Look in mm_cfg.py/Defaults.py for the definition of LOG_DIR and anything else used in its definition. This can be tricky. LOG_DIR is defined in Defaults.py in terms of VAR_PREFIX. If VAR_PREFIX is redefined in mm_cfg.py, this will not redefine LOG_DIR as LOG_DIR was already defined in Defaults.py in terms of the Defaults.py definition of VAR_PREFIX. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
-- On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote: -- Did you ever find a solution to this issue? -- -- I realize that this is a really old posting: -- --I send an eMail to one of the lists, I can see in my /var/log/maillog; -- -- Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: -- from=Niklas.Nikitin at xxx -- http://mail.python.org/mailman/listinfo/mailman-users , -- size=502, class=0, nrcpts=1, -- msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx -- http://mail.python.org/mailman/listinfo/mailman-users , -- proto=ESMTP, daemon=MTA, -- relay=cassini.xxx [193.10.220.37] -- -- Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: -- to=|/usr/local/mailman/mail/mailman post nicke-test, -- ctladdr=nicke-test at xxx -- http://mail.python.org/mailman/listinfo/mailman-users -- (8/0), delay=00:00:00, xdelay=00:00:00, -- mailer=prog, pri=30704, dsn=2.0.0, stat=Sent -- --that the server is receiving the eMail and is forwarding it to -- Mailman. But in Mailman's logs I will not find any information -- that it has received the eMail and no eMail is sent to the members -- on the list. If I dump all members of the list to a file, remove -- the list, create the list again and add all members, the list is -- working again for a while, and then it repeats again. -- -- but I've run into a very similar problem with two mailing lists that are -- managed using the current release of Mailman. -- -- The first symptom was that messages sent to the mailing lists were not -- distributed to the list, and did not show up in the list archive. -- -- After my ISP reinstalled Mailman, messages to the list started to show -- up in the list archive again. But the messages were still not distributed -- to members of the list. -- -- We found that if we add a new user, then a message to the list *is* -- delivered to that new user, but still not to any of the existing users. -- -- If the *new* user posts a message, that message appears in the list -- archive and the message is delivered to the entire mailing list. -- -- There doesn't seem to be a way to dump and reload the mailing list that -- preserves all per-list-member configuration options, so if possible, -- we'd like to avoid that workaround. Especially if it only works -- temporarily. -- -- Any insight / help / pointers appreciated. -- -- I had an oddity which may/maynot have some relevance.. -- -- We subscribed someone to a list with a specific email address. -- They confirmed the subscription using web interface. Subsequently -- mails from that member were received in the way you described and -- were passed to mailman but did not get posted to the list. -- -- I suggest you examine the headers of incoming mails,as they are -- intially received, and outgoing mails to those subscribers who are -- not receiving the mails.. There could be some changes being made to -- the headers either by the subscribers server or your own that is -- causing mails to be not delivered. Thanks for the suggestion, but I don't believe it applies in our case. There are several hundred subscribers on each list, with over 200 different mail domains (hence many different servers). A message from a newly added subscriber is accepted, logged in the archive, and distributed to all the members of the mailing list. A message from a existing subscriber is accepted, logged in the archive, confirming that it was seen and processed (at some level) by Mailman. The message *is* distributed to the newly added members of the mailing list. But it is not distributed to any of the existing members. I do not have direct access to the list server system; I am working through our ISP's support service. Any suggestions for what I can tell them to look for, in Mailman log files or queues or other places, to see why Mailman does not redistribute a message: - from an existing subscriber - to any existing subscriber but (as far as we can tell) is working correctly in all other permutations? Thanks. Beau -- david -- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: Thanks for the suggestion, but I don't believe it applies in our case. There are several hundred subscribers on each list, with over 200 different mail domains (hence many different servers). A message from a newly added subscriber is accepted, logged in the archive, and distributed to all the members of the mailing list. A message from a existing subscriber is accepted, logged in the archive, confirming that it was seen and processed (at some level) by Mailman. The message *is* distributed to the newly added members of the mailing list. But it is not distributed to any of the existing members. This makes no sense in terms of Mailman. Mailman builds the recipient list for a message independently of where it came from except that the sender only will be removed if the sender's 'not metoo' option is selected. I do not have direct access to the list server system; I am working through our ISP's support service. Any suggestions for what I can tell them to look for, in Mailman log files or queues or other places, to see why Mailman does not redistribute a message: - from an existing subscriber - to any existing subscriber but (as far as we can tell) is working correctly in all other permutations? They should look in Mailman's smtp log for entries like Apr 27 16:31:49 2007 (pid) message-id smtp for nnn recips, completed in t.ttt seconds to verify that nnn is the expected number, i.e. the number of regular (non-digest) members with delivery enabled, possibly minus 1 for the poster if the poster has 'not metoo' and possibly minus a very few more if the post has direct To:, Cc:, Resent-To: or Resent-Cc: recipients who are candidate recipients with the 'nodups' option selected. Also look in the smtp-failure log to see if there are any failed recipients of the message. Assuming this is OK, the problem is outbound of mailman. They should check MTA logs to see that the message is received from Mailman It may be received in more that one transaction with anywhere between 1 and several hundred recipients per transaction depending on Mailman settings, but they should add up to the number Mailman reports in the smtp log. Then only the MTA can say what it did with the message(s) after that. If it should turn out that the smtp log verifies that mailman is not sending from 'existing subscribers' to 'existing subscribers', i.e. messages from existing subscribers have a small 'nnn recips' equal to only 'new subscribers', then we can look at adding debugging logging to the handlers that build the recips list. BTW, what do you consider the 'current release' of Mailman? Also, I just had a sudden thought. Do your list(s) have topics defined and if not, did they ever? -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Number of message limits by web hosting services
On 4/27/07, John W Gintell wrote: Is there any feature (I found nothing in the documentation) in Mailman that would help out here, or are there people on this email list who have found encountered and solved this problem? So far as I know, we do not currently have a solution for you. See FAQ 4.51 for the details. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Number of message limits by web hosting services
John W Gintell wrote: Many of the web hosting services that offer mailman place a limit on the number of messages/hour that a given domain can deliver. This is presumably done to avoid saturating their servers. If you exceed the limit, they just ignore some of the recipients. Two hosts that we use have 300 and 500 as their limits. We have several largish email lists with several hundred addresses, one of which has ~400. If several people send to one or more of these lists in a given hour or one person sends to several lists at once, some of the recipients don't get the mail intended for them. Yes, this is a significant problem for the operation of Mailman. These hosts recommend using PHPlist instead which has a feature that can control the timing of the messages so as to not exceed the list, but PHPlist doesn't work for members of the list sending mail since it is really designed to be a Newsletter distribution mechanism. We recommend finding a new host ;-) Is there any feature (I found nothing in the documentation) in Mailman that would help out here, or are there people on this email list who have found encountered and solved this problem? Mailman has no throttling/rate limiting knobs built in. That's not to say you couldn't add one without much difficulty, but it wouldn't help. What will happen is Mailman will delay delivery, posters won't get their post and will repost making the problem worse. Soon Mailman will become so backlogged as to be essentially useless. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
-- BTW, what do you consider the 'current release' of Mailman? Sorry, I should have been specific: X-Mailman-Version: 2.1.9.cp2 which my ISP said was current. I don't know the significance of the .cp2, but 2.1.9 is the latest stable release according to http://sourceforge.net/project/showfiles.php?group_id=103 -- Also, I just had a sudden thought. Do your list(s) have topics defined -- and if not, did they ever? No and no. -- Thanks for the suggestion, but I don't believe it applies in our case. -- There are several hundred subscribers on each list, with over 200 -- different mail domains (hence many different servers). -- -- A message from a newly added subscriber is accepted, logged in the -- archive, and distributed to all the members of the mailing list. I just reconfirmed this, by adding myself again with yet another new address, then sending a message to the list from that new subscriber. The message was logged in the archive and was distributed to all members; I received a copy of the message at my old email address. -- A message from a existing subscriber is accepted, logged in the -- archive, confirming that it was seen and processed (at some level) -- by Mailman. The message *is* distributed to the newly added members -- of the mailing list. But it is not distributed to any of the existing -- members. This I cannot reconfirm at the moment. I sent another message to the list from my old address. The message was logged in the list archive, but does not appear to have been distributed to anyone on the mailing list (new or old). However: the first new user account we added to the list posted one message. That message is in the list archive, and I have the copy of that message that I received via the mailing list at my old address. So, something is going on but I have not yet characterized it completely. -- This makes no sense in terms of Mailman. Mailman builds the recipient -- list for a message independently of where it came from except that the -- sender only will be removed if the sender's 'not metoo' option is -- selected. Side note: the not metoo option is not working for us. I verified that the new accounts that I added do not have the not metoo option set, and the the default setting for the list does not have the not metoo option enable.d (Too many double negatives :-) ) The point being that for our mailing lists, the poster should receive a copy of his own message, but that is not happening. -- I do not have direct access to the list server system; I am working -- through our ISP's support service. Any suggestions for what I can -- tell them to look for, in Mailman log files or queues or other places, -- to see why Mailman does not redistribute a message: -- -- - from an existing subscriber -- - to any existing subscriber -- -- but (as far as we can tell) is working correctly in all other permutations? Thanks very much for the pointers below. I've passed them on to our ISP and I'll follow up to the list once I hear back. Beau -- They should look in Mailman's smtp log for entries like -- -- Apr 27 16:31:49 2007 (pid) message-id smtp for nnn recips, completed -- in t.ttt seconds -- -- to verify that nnn is the expected number, i.e. the number of regular -- (non-digest) members with delivery enabled, possibly minus 1 for the -- poster if the poster has 'not metoo' and possibly minus a very few -- more if the post has direct To:, Cc:, Resent-To: or Resent-Cc: -- recipients who are candidate recipients with the 'nodups' option -- selected. -- -- Also look in the smtp-failure log to see if there are any failed -- recipients of the message. -- -- Assuming this is OK, the problem is outbound of mailman. They should -- check MTA logs to see that the message is received from Mailman It may -- be received in more that one transaction with anywhere between 1 and -- several hundred recipients per transaction depending on Mailman -- settings, but they should add up to the number Mailman reports in the -- smtp log. -- -- Then only the MTA can say what it did with the message(s) after that. -- -- If it should turn out that the smtp log verifies that mailman is not -- sending from 'existing subscribers' to 'existing subscribers', i.e. -- messages from existing subscribers have a small 'nnn recips' equal to -- only 'new subscribers', then we can look at adding debugging logging -- to the handlers that build the recips list. -- -- BTW, what do you consider the 'current release' of Mailman? -- -- Also, I just had a sudden thought. Do your list(s) have topics defined -- and if not, did they ever? -- -- -- -- 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:
Re: [Mailman-Users] Lists stop working
On 4/27/07, [EMAIL PROTECTED] wrote: Sorry, I should have been specific: X-Mailman-Version: 2.1.9.cp2 That's cPanel. See FAQ 6.11. We have no way of verifying what they may have done to the stock Mailman code once they took it and modified it to their purposes. At best, we can try to guess. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: X-Mailman-Version: 2.1.9.cp2 which my ISP said was current. I don't know the significance of the .cp2, but 2.1.9 is the latest stable release according to http://sourceforge.net/project/showfiles.php?group_id=103 As Brad points out this is a cPanel release (specifically the second Cpanel release based on 2.1.9), and Brad refers you to the FAQ on cPanel Mailman. Side note: the not metoo option is not working for us. I verified that the new accounts that I added do not have the not metoo option set, and the the default setting for the list does not have the not metoo option enable.d (Too many double negatives :-) ) The point being that for our mailing lists, the poster should receive a copy of his own message, but that is not happening. This could be a cPanel issue. Also, there is a gmail issue. A user with a gmail account will never receive a copy of her own post because gmail sees it as a duplicate of the outgoing message in the 'sent' folder and discards it. This is a gmail feature. People have complained to gmail, so far AFAIK without any relief or known workaround. As far as cPanel is concerned, as Brad says, we can only guess. They modify Mailman in significant ways, and they don't share those mods with us. Someone once pressed them referring to the GPL and they shared some of their virtual hosting mods, but they have mods in several areas that we have never seen (although we have seen some of the negative consequences). Needless to say, this creates a very bad situation when we try to help cPanel users, since unless the issue is something we specifically recognize, we don't know whether it is a general Mailman issue or a cPanel issue, and if it's the latter we can't get under the hood to do a more detailed diagnosis. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
On 4/27/07, Mark Sapiro wrote: Needless to say, this creates a very bad situation when we try to help cPanel users, since unless the issue is something we specifically recognize, we don't know whether it is a general Mailman issue or a cPanel issue, and if it's the latter we can't get under the hood to do a more detailed diagnosis. I should point out that there are other cPanel users on this list, and they may be able to give you some assistance that we cannot. We'll continue to try to help as best we can, but we're going to be limited in what we can do. Unfortunately, we're dependant on the rest of the cPanel/Mailman community to help pitch in here, because the assistance we can provide is very limited. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] maiman, problem with greek characters
Mark Sapiro writes: Yes! base64 is a standard MIME encoding which the recipient's MUAs should recognize. Why do the recipients have difficulty reading a base64 encoded message? Because they use non-conforming MUAs localized to the environment. These MUAs are typically popular with users and admins because they just work in the common cases encountered by naive users, and don't require admins to use MIME-aware tools to examine messages. We may as well just accept it; even in Japan, which is starting to get its MUA act together after 30 years of self-imposed confusion (there are three commonly used native encodings of the national standard character set, all preferred to Unicode), just yesterday I received a partially unreadable message generated by a portable telephone, using corporate standard characters with code points in a reserved area of the national standard set. Unfortunately, I don't see an everybody happy policy for Mailman. Sure, it's conceptually possible to add a configuration variable that permits 8-bit transfer encodings, but it seems to me that would need to be list- and Content-Type-specific (including charset!) which would be complex. Or we could assume that the originating MUA's transfer encoding was well-chosen, but that would require tracking transfer encodings for each subobject of a message, and deciding on initialization etc. Not worth it in a world that increasingly supports all the MIME standard that Mailman uses, IMO. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Placing a copyright notice in list messages.
On Apr 27, 2007, at 1:37 PM, Brandon Sussman wrote: Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? As others have pointed out, it would probably be a mistake to do that unless you can be absolutely certain that all of those who post to the list want such a copyright statement. There will be cases where it won't be appropriate. I suspect that your intention as a list manager isn't so much as to assert copyright, but to disclaim responsibility. For this you could just add text to the footer saying that the responsibility for the content of a posting belongs to the poster. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Placing a copyright notice in list messages.
Dragon writes: Mark Sapiro sent the message below at 12:20 4/27/2007: Brandon Sussman wrote: Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? However, is this even a good idea at all. I've got to agree with Mark, I think it very quickly becomes problematic to do this. It's very common for attributions to get mixed up or be ambiguous in replies, especially in long discussion threads. That's right. However, the OP may be in a situation where attributions are uncommon, or everybody invariably top-posts. The real issue is that it has absolutely no legal effect establishing copyright in about 140 countries. Copyright is automatic under the Berne Convention and other relevant international treaties, including WIPO. Unless the poster makes explicit assignment of the content, or the post constitutes a work for hire, she owns copyright in all original expression in her post. In some jurisdictions, such as the U.S., additional protection is contingent on registering the work. But a notice is insufficient. However, there is legal risk involved, in that such a notice might indvertantly make a false claim. Suppose the poster forwards another's message? Or quotes enough to be a copyright issue? How about attachments? Then the list has made that false claim on behalf of the poster, which is a real mess, especially for the list admin, who can presumably be sued by both sides. So what we're left with is nannying people to be respectful of others' copyrights, and that can be done with a generic disclaimer: Please remember that all material distributed on this list is copyright by somebody, and get permission from all copyright holders before redistributing in any way. See the FAQ for description of use that does not require permission. If the OP is being nagged by his lawyers, I suppose there are conditions I'm not aware of. But please be very careful. Creating a disclaimer that covers all posts is not possible. Crafting posts that conform to the disclaimer is likely to be nontrivial, and require careful user training, unless the disclaimer is as vague as the one I suggested. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
