[Mailman-Users] List name stripped from subject header - how to prevent/workaround this?
(just realised my last message didn't have a subject... Doh!) Hi there, I've recently configured a mailman mailing list. Among other things, I've been thrown by the fact that any time I mention the name of the list in the subject: of an email, it gets stripped. The public name for the list is FYI, the prefix for the subject line is FYI - and if I write FYI anywhere in the subject line, it's automatically removed. I don't often mention the name of the list, but it'd be good to know what to do if I need to. Thanks, Jacob.// -- 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] (no subject)
Hi there, I've recently configured a mailman mailing list. Among other things, I've been thrown by the fact that any time I mention the name of the list in the subject: of an email, it gets stripped. The public name for the list is FYI, the prefix for the subject line is FYI - and if I write FYI anywhere in the subject line, it's automatically removed. I don't often mention the name of the list, but it'd be good to know what to do if I need to. Thanks, Jacob.// -- 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] List security: approved line got mailed out to list users
Hi. I've got my list configured as an announcement-only list, and the first few mailings I've sent have gone through exactly as planned. I use Approved: password as the first line to approve mailings. I inadvertently sent email to the list from one of my other email addresses, and when the message went out, the Approved: line was there, intact. There was a space above it, if that means anything (the sent email doesn't have that space...) I changed the password - easily done, no security problems there. But I'd still like to know what could have allowed this to happen. Since then, I've set up a test list and tried to replicate the behaviour - thus far no success. Anyone have any suggestions as to what might have happened? Thanks, Jacob Sam-La Rose Executive Editor FYI / Metaroar.com -- 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] Mailman log rotation
The esteemed Mark Sapiro has said: Hank van Cleef wrote: I want to put the Mailman logs into the Solaris logadm.conf file for automatic cron rotation. This moves the old logfiles to logfiles.0 and touches new logfiles. I'm assuming that the qrunners have to be restarted. Anything else? Qrunners don't need to be restarted, just log files reopened /path/to/bin/mailmanctl reopen That should be sufficient. Thanks much, Mark. I used the mailmanctl reopen in the /etc/logadm.conf file (with the full paths to everything---mandatory for cron jobs) and let cron do its thing. This morning, the logs are rotated and writing happily. Hank -- Hank van Cleef ([EMAIL PROTECTED], [EMAIL PROTECTED]) 1986 420SEL A stranger in paradise (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup Seen one, seen them all -- 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] Expiration on moderated requests
I am looking into a way to expire any moderated requests that are older than 2 weeks. Has this been discussed before? -Rob -- 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] Duplicate Subscribe/Unsubscribe Notifications
Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? -- 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] Duplicate Subscribe/Unsubscribe Notifications
On Fri, Jan 26, 2007 at 12:31:49PM -0500, Ki Song wrote: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? What mailman version are you using? I have exactly this problem, and the sysadmins my E-list is running on are running 2.1.5, which people here have deprecated. Alan -- Alan McConnell : http://patriot.net/users/alan There are many good Impeachment sites; one of the best is: www.waifllc.org -- 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] List security: approved line got mailed out to listusers
Jacob Sam-La Rose wrote: I've got my list configured as an announcement-only list, and the first few mailings I've sent have gone through exactly as planned. I use Approved: password as the first line to approve mailings. I inadvertently sent email to the list from one of my other email addresses, and when the message went out, the Approved: line was there, intact. There was a space above it, if that means anything (the sent email doesn't have that space...) What Mailman version is this? Do you have a copy of the message from the list - complete with all headers? If nothing else, if the list is archived, this copy will be in archives/private/listname.mbox/listname.mbox. How did the message get sent to the list? Was it held and manually approved (a clue that something was wrong with Approved:). Was the Approved: line that went to the list in the first text/plain part of the message or was it in a subsequent part, e.g. an HTML alternative part. Approved: body lines must be the first non-blank line in the first text/plain part of the message. If found there, they will be removed. Beginning in Mailman 2.1.7, an attempt is made to remove the approved line from other parts of the message, but it must first be found in the first text/plain part, and this removal from other parts isn't perfect. So, based on what little I have to go on so far, I will guess that the message you sent to the list was multipart/alternative with text/plain and text/html alternative parts and the Approved: line was found in and removed from the text/plain part and the message was accepted, but either because this is Mailman prior to 2.1.7 or because of something unusual about the way the Approved: line appeared in the html part, it wasn't removed from that part and that's where people saw 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://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] Duplicate Subscribe/Unsubscribe Notifications
Quoting Alan McConnell ([EMAIL PROTECTED]): On Fri, Jan 26, 2007 at 12:31:49PM -0500, Ki Song wrote: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? What mailman version are you using? I have exactly this problem, and the sysadmins my E-list is running on are running 2.1.5, which people here have deprecated. I don't think it's anything to do with 2.1.5 - I'm running the same and don't get duplicates. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ Tech Services - We Aim To Please, We Shoot To Kill -- H. Wade Minter, ASR -- 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] Duplicate Subscribe/Unsubscribe Notifications
Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? -- 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] Duplicate Subscribe/Unsubscribe Notifications
Ki Song wrote: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? End original message. - Are you certain of that? It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. If it is indeed being sent twice, I would expect the messages to have different message IDs, the time sent may or may not be different. If the message IDs are the same on both copies, I would strongly suspect you are getting bit by a filter rule and Mailman is doing the right thing. 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] Problems Exim: Child process ofmailman_transporttransport returned 2
[EMAIL PROTECTED] wrote: make clean ./configure --with-mail-gid=root --with-cgi-gid=www-data make install Stop Start MTA and Mailman but sill: Child process of mailman_transport transport returned 2 from command: /usr/= local/mailman/mail/mailman And what does the error message say about 'expected' and 'got' group? group = mail in the mailman-transport in your Exim configuration. Did this as well: Changed the group to mail, stopped and started exim and then Did you also put an appropriate 'user ='? make clean ./configure --with-mail-gid=mail --with-cgi-gid=www-data make install Stop and Start Mailman but still Child process of mailman_transport transport returned 2 from command: /usr/local/mailman/mail/mailman And what did the error message say about 'expected' and 'got' group here? Also, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp. -- 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] Expiration on moderated requests
Rob Jackson wrote: I am looking into a way to expire any moderated requests that are older than 2 weeks. If your Mailman is 2.1.6 or later, set max_days_to_hold to 14. -- 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] Duplicate Subscribe/Unsubscribe Notifications
Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? End original message. - Are you certain of that? It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. If it is indeed being sent twice, I would expect the messages to have different message IDs, the time sent may or may not be different. If the message IDs are the same on both copies, I would strongly suspect you are getting bit by a filter rule and Mailman is doing the right thing. Dragon I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: [EMAIL PROTECTED] Could this be a postfix issue? I don't think so ... because my other, regular messages, are being sent without duplicates. -- 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] Problem with explicit destination
We have a few lists configured to accept all mail addressed to them, mainly as they are email addresses on our website set for people to make inquiries at. We have the lists configured to use explicit destination, and reject anything that is not explicity sent to the list address. However, some mail still gets through. For example, this came in: To: [EMAIL PROTECTED] But we're not alliancecoatings.com Are the spammers forging list headers to allow the message to go through? If so, is there a way around this? We're running Mailman 2.1.5 on Mac OS X 10.4 server. --- Julia Frizzell Systems Administrator/Help Desk Manager The Education Alliance 222 Richmond Street, Suite 300 Providence, Rhode Island 02903-4226 [EMAIL PROTECTED] 401.274.9548 x311 or 800.521.9550 x311 401.421.7650 (fax) http://www.alliance.brown.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] apache22 DocumenRoot
Greetings. I'm relatively new to Apache2 and even newer to Mailman. On FreeBSD 6.1, I installed Apache 2.2 and Mailman from ports. By default, Apache's DocumentRoot is: /usr/local/www/apache22/data Mailman installs into: /usr/local/mailman My question: In the Apache httpd.conf file, what's the appropriate Directory path so users see Mailman? I thought of symlinking /usr/local/mailman under the DocumentRoot, but I'm concerned about security implications of that. What's the best way to set this up? thanks! /wsbs -- 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] Duplicate Subscribe/Unsubscribe Notifications
Ki Song quoted Dragon and wrote: It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: [EMAIL PROTECTED] OK. It is the same message. Did you check the filter rules in your email client as Dragon suggests to be sure that they are not responsible for duplicating the message? Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. -- 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] Duplicate Subscribe/Unsubscribe Notifications
At 3:33 PM -0500 1/26/07, Ki Song wrote: I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Just because the message-ids are exactly the same doesn't mean that this problem wasn't caused by filter rules. Check your queue-ids. That will tell you where the duplication is occurring. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] Problem with explicit destination
Julia Frizzell wrote: However, some mail still gets through. For example, this came in: To: [EMAIL PROTECTED] But we're not alliancecoatings.com What about Cc:? If your list's require_explicit_destination is set to Yes, a post should be held if the list posting address or an address in the list's acceptable_aliases does not appear in a To: or Cc: header of the post. The only thing that would bypass this is an Approved: header with the list's admin or moderator password. If posts are not being held in your case, please provide Mailman version, settings for require_explicit_destination and acceptable_aliases, and the complete headers of the post, and we'll try to figure it out. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] apache22 DocumenRoot
wo_shi_big_stomach wrote: My question: In the Apache httpd.conf file, what's the appropriate Directory path so users see Mailman? See http://www.list.org/mailman-install/node10.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
Re: [Mailman-Users] Problem with explicit destination
Just got one in right now, so let's use this one. I've replaced our @address with @xxx. As far as I can see, there's no cc in here. As i said in my original message, we're running Mailman 2.1.5 on OS X 10.4. We have set require_explicit_destination to Yes and acceptable_aliases is blank. From: [EMAIL PROTECTED] Subject:[Publications] Most popular Date: January 26, 2007 3:52:27 PM EST To: [EMAIL PROTECTED] Received: from ex-gateway1-in.AD.Brown.Edu ([128.148.21.51]) by mail1.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:53:03 -0500 Received: from draco.services.brown.edu ([128.148.106.172]) by ex- gateway1-in.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:52:38 -0500 Received: from list.alliance.brown.edu (list.alliance.brown.edu [128.148.108.6]) by draco.services.brown.edu (Switch-3.1.10/ Switch-3.1.7/) with ESMTP id l0QKqcNZ027652; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from list.alliance.brown.edu (localhost [127.0.0.1]) by list.alliance.brown.edu (Postfix) with ESMTP id 3B13B1AB177; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from cpe-69-203-99-40.nyc.res.rr.com (cpe-69-203-99-40.nyc.res.rr.com [69.203.99.40]) by list.alliance.brown.edu (Postfix) with ESMTP id 1E7581AB153 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 15:52:36 -0500 (EST) Received: from [70.34.194.185] (HELO JKDJPUF) by 69.203.99.40 (CommuniGate Pro SMTP 5.0.11) with SMTP id 40033759 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 15:52:27 -0500 X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-Id: 020501c7418b$e3c1b190 [EMAIL PROTECTED] Mime-Version: 1.0 X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Beenthere:[EMAIL PROTECTED] X-Mailman-Version: 2.1.5 Precedence: list Content-Type: multipart/mixed; boundary1298335293== Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-Brown-Proofpoint: Not Infected X-Proofpoint-Spam-Reason: safe Return-Path:[EMAIL PROTECTED] X-Originalarrivaltime: 26 Jan 2007 20:53:03.0635 (UTC) FILETIME= [F8F40630:01C7418B] On Jan 26, 2007, at 3:53 PM, Mark Sapiro wrote: Julia Frizzell wrote: However, some mail still gets through. For example, this came in: To: [EMAIL PROTECTED] But we're not alliancecoatings.com What about Cc:? If your list's require_explicit_destination is set to Yes, a post should be held if the list posting address or an address in the list's acceptable_aliases does not appear in a To: or Cc: header of the post. The only thing that would bypass this is an Approved: header with the list's admin or moderator password. If posts are not being held in your case, please provide Mailman version, settings for require_explicit_destination and acceptable_aliases, and the complete headers of the post, and we'll try to figure it out. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] Duplicate Subscribe/Unsubscribe Notifications
It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: [EMAIL PROTECTED] OK. It is the same message. Did you check the filter rules in your email client as Dragon suggests to be sure that they are not responsible for duplicating the message? I checked the filter rules. I could not find anything that could possibly duplicate messages. There is only one reference to the messages that are being duplicated (the filter/rule looks for where the message is being SENT to) Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Where could I find these attributes? Is it on the web admin interface, or is it somewhere else? Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. The message-ID from mailman's smtp log shows something interesting. Every message that is duplicated, shows the same message-ID, but it says that it is being sent to 2 recipients. Is that normal? I ask because as far as I know, these subscribe messages are being sent to me, the administrator, and the actual email that is being subscribed/unsubscribed. Is that normal, or would it be two different message-ID's, if only 1 message was being sent to me and 1 message was being sent to the email address that is being subscribed/unsubscribed? -- 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] Duplicate Subscribe/Unsubscribe Notifications
Ki Song wrote: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? End original message. - Are you certain of that? It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. If it is indeed being sent twice, I would expect the messages to have different message IDs, the time sent may or may not be different. If the message IDs are the same on both copies, I would strongly suspect you are getting bit by a filter rule and Mailman is doing the right thing. Dragon I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: [EMAIL PROTECTED] Could this be a postfix issue? I don't think so ... because my other, regular messages, are being sent without duplicates. End original message. - OK, so it is probably NOT mailman causing this. Which is what I said earlier. There is a very slim possibility of it being a configuration issue with Postfix but I doubt it. It's almost certain to be a MUA filter issue instead of an MTA issue. 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] List name stripped from subject header - how toprevent/workaround this?
Jacob Sam-La Rose wrote: I've recently configured a mailman mailing list. Among other things, I've been thrown by the fact that any time I mention the name of the list in the subject: of an email, it gets stripped. The public name for the list is FYI, the prefix for the subject line is FYI - and if I write FYI anywhere in the subject line, it's automatically removed. I don't often mention the name of the list, but it'd be good to know what to do if I need to. Multiple occurrences of subject_prefix in the subject are replaced with just one occurrence at the beginning of the subject to prevent 'build up' in replies. If you configure subject_prefix with brackets (e.g. [FYI]) as is conventionally done for prefixes, unbracketed FYI should not be removed. -- 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] Duplicate Subscribe/Unsubscribe Notifications
Ki Song quoted Mark Sapiro and wrote: Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Where could I find these attributes? Is it on the web admin interface, or is it somewhere else? Web admin, General options. Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. The message-ID from mailman's smtp log shows something interesting. Every message that is duplicated, shows the same message-ID, but it says that it is being sent to 2 recipients. Is that normal? It is normal if the total number of addresses in the 'owner' and 'moderator' lists is two. I ask because as far as I know, these subscribe messages are being sent to me, the administrator, and the actual email that is being subscribed/unsubscribed. Is that normal, or would it be two different message-ID's, if only 1 message was being sent to me and 1 message was being sent to the email address that is being subscribed/unsubscribed? The owner notice and the user notice are different messages with different Message-IDs. Note that some notifications such as held message notifications are sent twice and have two smtp log entries. The first send has one recipient which is the list's -owner address, and this is followed by the resend to the owners and moderators. This is not the case for (un)subscribe notices however. Subscribe and unsubscribe owner notices are sent directly to the owners and moderators without going through the -owner address. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] Duplicate Subscribe/Unsubscribe Notifications
It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: [EMAIL PROTECTED] OK. It is the same message. Did you check the filter rules in your email client as Dragon suggests to be sure that they are not responsible for duplicating the message? I checked the filter rules. I could not find anything that could possibly duplicate messages. There is only one reference to the messages that are being duplicated (the filter/rule looks for where the message is being SENT to) Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Where could I find these attributes? Is it on the web admin interface, or is it somewhere else? Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. The message-ID from mailman's smtp log shows something interesting. Every message that is duplicated, shows the same message-ID, but it says that it is being sent to 2 recipients. Is that normal? I ask because as far as I know, these subscribe messages are being sent to me, the administrator, and the actual email that is being subscribed/unsubscribed. Is that normal, or would it be two different message-ID's, if only 1 message was being sent to me and 1 message was being sent to the email address that is being subscribed/unsubscribed? One thing I do notice is that the administrator and moderator addresses listed in the GENERAL OPTIONS web admin page of each list is the same address ([EMAIL PROTECTED]). Further below, on that same page, there is an option that says, Should the administrator get notices of subscribes and unsubscribes? I have that checked to YES. Could it be that because the administrator and moderator addresses are the same ([EMAIL PROTECTED]) and because the administrator is getting notices of subscribes and unsubscribes, that the message is being sent twice? I'm assuming the moderator gets notices of subscribes/unsubscribes automatically. Let me check. (It may take a while ... because there are a couple hundred/thousand subscribe/unsubscribe messages in queue. -- 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] Duplicate Subscribe/Unsubscribe Notifications
On Fri, Jan 26, 2007 at 02:46:35PM -0600, Brad Knowles wrote: At 3:33 PM -0500 1/26/07, Ki Song wrote: I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Just because the message-ids are exactly the same doesn't mean that this problem wasn't caused by filter rules. The filter list on my E-list seem pretty simple. Check your queue-ids. That will tell you where the duplication is occurring. What are queue-ids? Are they something that a mailman admin can see? I have no access to any log files; they are available only to the sys-admins of my ISP. Alan -- Alan McConnell : http://patriot.net/users/alan There are many good Impeachment sites; one of the best is: www.waifllc.org -- 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] Problem with explicit destination
Julia Frizzell wrote: Just got one in right now, so let's use this one. I've replaced our @address with @xxx. As far as I can see, there's no cc in here. As i said in my original message, we're running Mailman 2.1.5 on OS X 10.4. We have set require_explicit_destination to Yes and acceptable_aliases is blank. If this is the Apple OS X Server Mailman, it may have modifications that make it behave differently from standard Mailman. From: [EMAIL PROTECTED] Subject:[Publications] Most popular Date: January 26, 2007 3:52:27 PM EST To: [EMAIL PROTECTED] Where are you seeing the above headers? This appears to be some MUA's rendering of the message, not the raw message headers. In a raw message, the above headers would not precede the Received: headers. Do you have access to the global mailbox in the list's archive? It is the file archives/private/listname.mbox/listname.mbox. If you don't have direct access to the file, you may have a link to it on the list's archive table of contents page, and even if not, you may be able to access it via a URL like http://example.com/mailman/private/listname.mbox/listname.mbox. What are the headers of this message in that file? Received: from ex-gateway1-in.AD.Brown.Edu ([128.148.21.51]) by mail1.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:53:03 -0500 Received: from draco.services.brown.edu ([128.148.106.172]) by ex- gateway1-in.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:52:38 -0500 Received: from list.alliance.brown.edu (list.alliance.brown.edu [128.148.108.6]) by draco.services.brown.edu (Switch-3.1.10/ Switch-3.1.7/) with ESMTP id l0QKqcNZ027652; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from list.alliance.brown.edu (localhost [127.0.0.1]) by list.alliance.brown.edu (Postfix) with ESMTP id 3B13B1AB177; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from cpe-69-203-99-40.nyc.res.rr.com (cpe-69-203-99-40.nyc.res.rr.com [69.203.99.40]) by list.alliance.brown.edu (Postfix) with ESMTP id 1E7581AB153 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 15:52:36 -0500 (EST) Received: from [70.34.194.185] (HELO JKDJPUF) by 69.203.99.40 (CommuniGate Pro SMTP 5.0.11) with SMTP id 40033759 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 15:52:27 -0500 X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-Id: 020501c7418b$e3c1b190 [EMAIL PROTECTED] Mime-Version: 1.0 X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Beenthere:[EMAIL PROTECTED] X-Mailman-Version: 2.1.5 Precedence: list Content-Type: multipart/mixed; boundary1298335293== Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-Brown-Proofpoint: Not Infected X-Proofpoint-Spam-Reason: safe Return-Path:[EMAIL PROTECTED] X-Originalarrivaltime: 26 Jan 2007 20:53:03.0635 (UTC) FILETIME= [F8F40630:01C7418B] The rest of these headers look like those from a raw message, but since the first few were moved, I can't be sure what else may have been altered. -- 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] Duplicate Subscribe/Unsubscribe Notifications
Ki Song wrote: One thing I do notice is that the administrator and moderator addresses listed in the GENERAL OPTIONS web admin page of each list is the same address ([EMAIL PROTECTED]). Bingo! Further below, on that same page, there is an option that says, Should the administrator get notices of subscribes and unsubscribes? I have that checked to YES. This causes the notice to be sent. This particular notice is sent to both the owners and the moderators. You are listed twice - you get it twice. Some (very few, I don't remember which offhand) notices are sent to owner only. Most are sent to owner and moderator. None are sent to moderator only. Thus it makes no sense to list an address as both owner and moderator and only results in duplicate notices. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.027.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.060.htp for more information. -- 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] Duplicate Subscribe/Unsubscribe Notifications
OK. It is the same message. Did you check the filter rules in your email client as Dragon suggests to be sure that they are not responsible for duplicating the message? I checked the filter rules. I could not find anything that could possibly duplicate messages. There is only one reference to the messages that are being duplicated (the filter/rule looks for where the message is being SENT to) Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Where could I find these attributes? Is it on the web admin interface, or is it somewhere else? Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. The message-ID from mailman's smtp log shows something interesting. Every message that is duplicated, shows the same message-ID, but it says that it is being sent to 2 recipients. Is that normal? I ask because as far as I know, these subscribe messages are being sent to me, the administrator, and the actual email that is being subscribed/unsubscribed. Is that normal, or would it be two different message-ID's, if only 1 message was being sent to me and 1 message was being sent to the email address that is being subscribed/unsubscribed? One thing I do notice is that the administrator and moderator addresses listed in the GENERAL OPTIONS web admin page of each list is the same address ([EMAIL PROTECTED]). Further below, on that same page, there is an option that says, Should the administrator get notices of subscribes and unsubscribes? I have that checked to YES. Could it be that because the administrator and moderator addresses are the same ([EMAIL PROTECTED]) and because the administrator is getting notices of subscribes and unsubscribes, that the message is being sent twice? I'm assuming the moderator gets notices of subscribes/unsubscribes automatically. Let me check. (It may take a while ... because there are a couple hundred/thousand subscribe/unsubscribe messages in queue. That's what it was. -- 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] Group Mismatch Error
Time for this old chestnut again, but with a bit of a twist. Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. Attempted to send a test message to my list. ommand died with status 2: /usr/local/mailman/mail/mailman post netoplist. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re-run configure, providing the command line option `--with-mail-gid=mailman'. Yet... mybox# ll total 38 -rw-r- 1 root mailman 41 Jan 26 13:33 adm.pw -rw-rw 1 mailman mailman 1995 Jan 26 13:36 aliases -rw-rw 1 mailman mailman 16384 Jan 26 13:36 aliases.db -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version -rw-rw 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg Is there something blindingly obvious that I'm missing? -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / [EMAIL PROTECTED] Today's Excuse: Just pick up the phone and give modem connect sounds. Well you said we should get more lines so we don't have voice lines. -- 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] List security: approved line got mailed out to listusers
Thanks for the response, Mark. I'm only just getting used to the concept of community via mailing list (I'm more used to user forums...!) On 26 Jan 2007, at 19:00, Mark Sapiro wrote: Jacob Sam-La Rose wrote: I've got my list configured as an announcement-only list, and the first few mailings I've sent have gone through exactly as planned. I use Approved: password as the first line to approve mailings. I inadvertently sent email to the list from one of my other email addresses, and when the message went out, the Approved: line was there, intact. There was a space above it, if that means anything (the sent email doesn't have that space...) What Mailman version is this? 2.1.9.cp2 Do you have a copy of the message from the list - complete with all headers? If nothing else, if the list is archived, this copy will be in archives/private/listname.mbox/listname.mbox. Headers: Subject:FYI (important): any email to / Jacob this morning... Date: 26 January 2007 11:00:05 GMT To: [EMAIL PROTECTED] Return-Path:[EMAIL PROTECTED] Envelope-To:[EMAIL PROTECTED] Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 Received: from yosafa by mrfriendly.asmallorange.com with local- bsmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOrV-z6-3K for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:03:20 -0500 Received: from hypnotoad.liquidweb.com ([72.52.133.24]:50358) by mrfriendly.asmallorange.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOrU-xz-PZ for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:03:16 -0500 Received: from localhost ([127.0.0.1]:50149 helo=hypnotoad.liquidweb.com) by hypnotoad.liquidweb.com with esmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOoT-00032t-0j; Fri, 26 Jan 2007 06:00:09 -0500 Received: from [81.103.209.178] (port=56306) by hypnotoad.liquidweb.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOoR-00032U-85 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:00:07 -0500 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mrfriendly.asmallorange.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=AWL,HTML_MESSAGE autolearn=ham version=3.1.7 Mime-Version: 1.0 (Apple Message framework v752.2) Message-Id: [EMAIL PROTECTED] X-Mailer: Apple Mail (2.752.2) X-Clamantivirus-Scanner:This mail is clean X-Clamantivirus-Scanner:This mail is clean X-Beenthere:[EMAIL PROTECTED] X-Mailman-Version: 2.1.9.cp2 Precedence: list List-Id:Everything you wanted to know about poetry, but didn't know who to ask... fyi_metaroar.com.metaroar.com List-Unsubscribe: http://metaroar.com/mailman/listinfo/ fyi_metaroar.com, mailto:[EMAIL PROTECTED] List-Archive: http://metaroar.com/pipermail/fyi_metaroar.com List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://metaroar.com/mailman/listinfo/ fyi_metaroar.com, mailto:[EMAIL PROTECTED] Content-Type: multipart/mixed; boundary2746362320716674074== Errors-To: [EMAIL PROTECTED] X-Antiabuse:This header was added to track abuse, please include it with any abuse report X-Antiabuse:Primary Hostname - hypnotoad.liquidweb.com X-Antiabuse:Original Domain - jsamlarose.com X-Antiabuse:Originator/Caller UID/GID - [0 0] / [47 12] X-Antiabuse:Sender Address Domain - metaroar.com X-Source: X-Source-Args: X-Source-Dir: X-Antivirus-Scanner:Clean mail though you should still use an Antivirus Do you need to see the body of the email? How did the message get sent to the list? Was it held and manually approved (a clue that something was wrong with Approved:). Sent as email straight to the list - didn't have to be manually approved - it went straight through. Was the Approved: line that went to the list in the first text/plain part of the message or was it in a subsequent part, e.g. an HTML alternative part. It was in the first text/plain part - though in the sent version I've got of the mail, the Approved: line is the very first line. Once it went through the list, there was a line space at the top of the email, before the Approved: line... Approved: body lines must be the first non-blank line in the first text/plain part of the message. If found there, they will be removed. Beginning in Mailman 2.1.7, an attempt is made to remove the approved line from other parts of the message, but it must first be found in the first text/plain part, and this removal from other parts isn't perfect. So,
Re: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications
At 4:41 PM -0500 1/26/07, Alan McConnell wrote: Check your queue-ids. That will tell you where the duplication is occurring. What are queue-ids? Are they something that a mailman admin can see? I have no access to any log files; they are available only to the sys-admins of my ISP. The queue-ids are typically shown in the contents of the various Received: headers on each message. They would also show up in the system logs for the mail server. These logs may only be accessible to your mail server administrator -- they are outside of Mailman, and unfortunately not even the internal Mailman logs are available via the web. For example, on the message I am responding to, this is a sample of the Received: headers I found: Received: from bag.python.org (bag [127.0.0.1]) by bag.python.org (Postfix) with ESMTP id 943801E4011 for mailman-users@python.org; Fri, 26 Jan 2007 22:42:32 +0100 (CET) Received: from bag (HELO bag.python.org) (127.0.0.1) by bag.python.org with SMTP; 26 Jan 2007 22:42:32 +0100 Received: from jefferson.patriot.net (jefferson.patriot.net [209.249.176.3]) by bag.python.org (Postfix) with ESMTP for mailman-users@python.org; Fri, 26 Jan 2007 22:42:31 +0100 (CET) Received: from patriot.net ([EMAIL PROTECTED] [209.249.180.173]) by jefferson.patriot.net (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l0QLgPrM022931; Fri, 26 Jan 2007 16:42:29 -0500 Received: by patriot.net (Postfix, from userid 500) id 8ABEC47587; Fri, 26 Jan 2007 16:41:37 -0500 (EST) In each case, where it says id 8ABEC47587 or with ESMTP id l0QLgPrM022931, or something like that, the ids it is referring to are called queue ids. If you are looking at the system log for the mail services on a given server, the only way you can typically tie in a given log entry to a given message is through the queue-ids. Looking in the system log file for postfix on this machine, the entries relevant to queue-id 943801E4011 are: Jan 26 22:42:32 bag postfix/smtpd[27954]: 943801E4011: client=bag[127.0.0.1] Jan 26 22:42:32 bag postfix/cleanup[28483]: 943801E4011: message-id=[EMAIL PROTECTED] Jan 26 22:42:32 bag postfix/qmgr[27081]: 943801E4011: from=[EMAIL PROTECTED], size=2239, nrcpt=1 (queue active) Jan 26 22:42:32 bag postfix/local[28226]: 943801E4011: to=[EMAIL PROTECTED], orig_to=mailman-users@python.org, relay=local, delay=0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post mailman-users) Jan 26 22:42:32 bag postfix/qmgr[27081]: 943801E4011: removed You see the message-id here once, but all the other log entries relative to this particular event are logged with only the date and the queue-id, as well as whatever other information was being logged. So, you need the queue-id in order to be able to tie them all together. Now, these are not the only log entries for this message. Because of the way the mail server on this machine is configured, it actually handles each message three times -- once on inbound (before scanning for spam and viruses), once on inbound (after scanning), and again after the message has gone through Mailman and is being sent out. So, if we look for other log entries relative to this message-id, we find that we have to look at 992 different queue-ids, one for each of the subscribers on the outbound side, plus one on inbound (before scanning) and another on inbound (after scanning). I'll spare you and not even show you the complete list of all the queue-ids in question, and of course I'd never show you the complete set of all those log entries. Anyway, my point is this -- if you look at the headers of two messages that appear to be identical, you can look at the Received: headers to see if they really are identical. If each and every queue-id in both messages are exactly the same, then there must have been some sort of duplication that occurred within your mail client or somewhere else outside of the normal SMTP Message Transfer Agent system. If the queue-ids are identical up to a point but they diverge after that point, that tells you exactly where the message was somehow duplicated. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] List security: approved line got mailed out to listusers
At 10:59 PM + 1/26/07, Jacob Sam-La Rose wrote: What Mailman version is this? 2.1.9.cp2 That's a cPanel version number. Please see FAQ 6.11. Do you have a copy of the message from the list - complete with all headers? If nothing else, if the list is archived, this copy will be in archives/private/listname.mbox/listname.mbox. Headers: Subject: FYI (important): any email to / Jacob this morning... Date: 26 January 2007 11:00:05 GMT To: [EMAIL PROTECTED] Return-Path:[EMAIL PROTECTED] Envelope-To:[EMAIL PROTECTED] Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 Received: from yosafa by mrfriendly.asmallorange.com with Something has munged the heck out of these headers. In the raw mbox file, there are no preceding space characters before any of them. We want to see what is in the raw mbox file, not anything else. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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] Group Mismatch Error
Jay Chandler wrote: Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. Attempted to send a test message to my list. ommand died with status 2: /usr/local/mailman/mail/mailman post netoplist. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re-run configure, providing the command line option `--with-mail-gid=mailman'. Yet... mybox# ll total 38 -rw-r- 1 root mailman 41 Jan 26 13:33 adm.pw -rw-rw 1 mailman mailman 1995 Jan 26 13:36 aliases -rw-rw 1 mailman mailman 16384 Jan 26 13:36 aliases.db -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version -rw-rw 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg Is there something blindingly obvious that I'm missing? Maybe. Where did the netoptlist alias come from. Did Postfix find the alias somewhere else (maybe /etc/aliases*) either before or instead of Mailman's data/aliases*? -- 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] Group Mismatch Error
Mark Sapiro wrote: Jay Chandler wrote: Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. Attempted to send a test message to my list. ommand died with status 2: /usr/local/mailman/mail/mailman post netoplist. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re-run configure, providing the command line option `--with-mail-gid=mailman'. Yet... mybox# ll total 38 -rw-r- 1 root mailman 41 Jan 26 13:33 adm.pw -rw-rw 1 mailman mailman 1995 Jan 26 13:36 aliases -rw-rw 1 mailman mailman 16384 Jan 26 13:36 aliases.db -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version -rw-rw 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg Is there something blindingly obvious that I'm missing? Maybe. Where did the netoptlist alias come from. Did Postfix find the alias somewhere else (maybe /etc/aliases*) either before or instead of Mailman's data/aliases*? Nope-- I created that myself as a test list. The other aliases file is owned by root:wheel. -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / [EMAIL PROTECTED] Today's Excuse: Just pick up the phone and give modem connect sounds. Well you said we should get more lines so we don't have voice lines. -- 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] Finding the recipients for a given archived email
I have a mailing list whose membership changes frequently. I want to find out who received a two-month-old email in the archives. In other words, I want to know the list membership at the time that message was sent. How can I do this? I realize I could look at sendmail logs (if they went back that far), but is there an pure Mailman way to do this? I believe (not sure) that the vette(?) log keeps track of subscribes/unsubscribes, so I could theoretically reconstruct the list, starting with the current membership and working backward. Is this possible? Is there an easier way? -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. -- 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] List security: approved line got mailed out to listusers
Jacob Sam-La Rose wrote: Headers: Subject: FYI (important): any email to / Jacob this morning... Date: 26 January 2007 11:00:05 GMT To: [EMAIL PROTECTED] As Brad points out in another reply, these don't look like raw message headers for a few reasons, not the least of which being Subject:, Date: and To: preceeding the headers immediately below. Return-Path:[EMAIL PROTECTED] Envelope-To:[EMAIL PROTECTED] Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 Received: from yosafa by mrfriendly.asmallorange.com with local- bsmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOrV-z6-3K for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:03:20 -0500 Received: from hypnotoad.liquidweb.com ([72.52.133.24]:50358) by mrfriendly.asmallorange.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOrU-xz-PZ for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:03:16 -0500 Received: from localhost ([127.0.0.1]:50149 helo=hypnotoad.liquidweb.com) by hypnotoad.liquidweb.com with esmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOoT-00032t-0j; Fri, 26 Jan 2007 06:00:09 -0500 Received: from [81.103.209.178] (port=56306) by hypnotoad.liquidweb.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HAOoR-00032U-85 for [EMAIL PROTECTED]; Fri, 26 Jan 2007 06:00:07 -0500 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mrfriendly.asmallorange.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=AWL,HTML_MESSAGE autolearn=ham version=3.1.7 Mime-Version: 1.0 (Apple Message framework v752.2) Message-Id: [EMAIL PROTECTED] X-Mailer: Apple Mail (2.752.2) X-Clamantivirus-Scanner:This mail is clean X-Clamantivirus-Scanner:This mail is clean X-Beenthere:[EMAIL PROTECTED] X-Mailman-Version: 2.1.9.cp2 Precedence: list List-Id:Everything you wanted to know about poetry, but didn't know who to ask... fyi_metaroar.com.metaroar.com List-Unsubscribe: http://metaroar.com/mailman/listinfo/ fyi_metaroar.com, mailto:[EMAIL PROTECTED] List-Archive: http://metaroar.com/pipermail/fyi_metaroar.com List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://metaroar.com/mailman/listinfo/ fyi_metaroar.com, mailto:[EMAIL PROTECTED] Content-Type: multipart/mixed; boundary2746362320716674074== The multipart/mixed structure is probably due to Mailman's adding either msg_header or msg_footer or both as separate MIME parts, thus, by itself this doesn't tell me much about the original message. Errors-To: [EMAIL PROTECTED] X-Antiabuse:This header was added to track abuse, please include it with any abuse report X-Antiabuse:Primary Hostname - hypnotoad.liquidweb.com X-Antiabuse:Original Domain - jsamlarose.com X-Antiabuse:Originator/Caller UID/GID - [0 0] / [47 12] X-Antiabuse:Sender Address Domain - metaroar.com X-Source: X-Source-Args: X-Source-Dir: X-Antivirus-Scanner:Clean mail though you should still use an Antivirus Do you need to see the body of the email? I need to see the mime structure of the message including the part headers and at least the initial lines of the part that still has the Approved: line in it, and I need to see this as a raw message, not interpreted by some MUA. How did the message get sent to the list? Was it held and manually approved (a clue that something was wrong with Approved:). Sent as email straight to the list - didn't have to be manually approved - it went straight through. Was the Approved: line that went to the list in the first text/plain part of the message or was it in a subsequent part, e.g. an HTML alternative part. It was in the first text/plain part - though in the sent version I've got of the mail, the Approved: line is the very first line. Once it went through the list, there was a line space at the top of the email, before the Approved: line... Assuming that the message actually needed to be approved, the line would have been removed at least from the first text/plain part. If you are able to get that 'sent version' in its raw form, that would be most useful. You appear to be using Apple mail. You can view raw source via View-Message-Raw source (option-command-U). -- 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
Re: [Mailman-Users] Group Mismatch Error
Jay Chandler wrote: Mark Sapiro wrote: Jay Chandler wrote: Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. Attempted to send a test message to my list. ommand died with status 2: /usr/local/mailman/mail/mailman post netoplist. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re-run configure, providing the command line option `--with-mail-gid=mailman'. Yet... mybox# ll total 38 -rw-r- 1 root mailman 41 Jan 26 13:33 adm.pw -rw-rw 1 mailman mailman 1995 Jan 26 13:36 aliases -rw-rw 1 mailman mailman 16384 Jan 26 13:36 aliases.db -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version -rw-rw 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg Is there something blindingly obvious that I'm missing? Maybe. Where did the netoptlist alias come from. Did Postfix find the alias somewhere else (maybe /etc/aliases*) either before or instead of Mailman's data/aliases*? Nope-- I created that myself as a test list. The other aliases file is owned by root:wheel. My mistake, I got it backwards. Postfix is executing the wrapper as mailman:mailman, the owner:group of the aliases. Mailman's wrapper is expecting group 'nobody'. You can't change the owner:group of the aliases or list creation won't be able to update them. This means you need to reconfigure the wrapper to expect group 'mailman' instead of 'nobody'. There is probably some FreeBSD port magic way to do this, but I don't know what it is. -- 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] Finding the recipients for a given archived email
Kelly Jones wrote: I have a mailing list whose membership changes frequently. I want to find out who received a two-month-old email in the archives. In other words, I want to know the list membership at the time that message was sent. I'm assuming you don't care about regular vs digest which you can't track because changes aren't logged. I believe (not sure) that the vette(?) log keeps track of subscribes/unsubscribes, so I could theoretically reconstruct the list, starting with the current membership and working backward. Is this possible? Is there an easier way? It's the subscribe log, but yes you can get the subscribes and unsubscribes and work backwards. Address changes currently aren't logged (they will be in 2.2), but that may not be significant for your purpose. No, I don't know an easier way unless you have a backup somewhere of the list's config.pck from the date of interest. If you do, you could use bin/dumpdb to get the information. -- 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
