[Mailman-Users] Mailman chewing up resources
Hello, We run a VPS running Debian with Mailman 2.1.11 and Postfix. Python is 2.5.2. Up until a couple of weeks ago, we were running a number of quite small mailing lists (max 200 members) with no problems. But then we imported the subscriber list of a list that we'd moved from Yahoogroups that contained 800+ members, and that's when the trouble started. This list not only has 800 or so members, but it's a fairly active list. We also have quite a number of deferred messages from Yahoo in the queue, but that's a different story. We've just implemented DKIM, hopefully that will help sort that one out. The problem we're seeing is that if the list gets any way busy, the memory usage of the python process that runs Mailman skyrockets, dragging the system to a crawl. We're a little clueless as to how to debug this further, so any help would be appreciated. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Footers As Attachments
I've been using Mailman for a long time for several small lists that I maintain. There are two configuration issues that I still do not understand. First, messages sent to participants have the footer as an attachment. The only way I could get rid of the attachment was to delete the footer text. The messages on this list have the footer, and it is not showing up as an attachment, so I am doing something wrong. The other question has to do with bounce processing. When I load a new list of email addresses, how can I check for bad ones other than wait until there are enough bounces within a period of time to unsubscribe? It would be very helpful to be able to designate an email address to which ALL bounces are sent. Can that be done? Thanks! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Footers As Attachments
Zone Page wrote: I've been using Mailman for a long time for several small lists that I maintain. There are two configuration issues that I still do not understand. First, messages sent to participants have the footer as an attachment. The only way I could get rid of the attachment was to delete the footer text. The messages on this list have the footer, and it is not showing up as an attachment, so I am doing something wrong. See the FAQ at http://wiki.list.org/x/84A9 The footers are not (usually) separate MIME parts on this list because people tend to post plain text, and this list uses Mailman's content filtering to remove non plain text parts from posts so the footers can be added to the simple plain text message body. The other question has to do with bounce processing. When I load a new list of email addresses, how can I check for bad ones other than wait until there are enough bounces within a period of time to unsubscribe? It would be very helpful to be able to designate an email address to which ALL bounces are sent. Can that be done? When you load a new list of email addresses, invite the list rather than subscribing it. Problem solved. There already is an address to which all bounces are sent. It is listname-boun...@... If you have control over the MTA that delivers this mail, you can deliver it anywhere you want. You can also set the bounce processing threshold score to 1 to disable delivery and notify the admin upon the first bounce. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman chewing up resources
Geoff Shang wrote:
The problem we're seeing is that if the list gets any way busy, the memory
usage of the python process that runs Mailman skyrockets, dragging the
system to a crawl.
Which Python process? mailmanctl should not be affected. Beyond that,
there are 8 qrunner processes. Are they all affected, or just one or
two?
We're a little clueless as to how to debug this further, so any help would
be appreciated.
There is an issue that affects memory usage in the qrunners. They keep
a cache of list objects in memory to reduce disk IO. The cache is
supposed to free the space used by a list object when there are no
more references to that object, but it turns out there is a
self-reference in the list objects, so the cache simply grows until it
holds a copy of each list.
There are other issues in that large messages can cause the runners
that handle it to grow, and Python's memory management is such that
Python itself never gives freed memory back to the OS. Memory can be
freed within Python and it will be available for reuse within that
process, but it is not given back to the OS.
I recommend disabling the list cache within the qrunners. This was done
for the now defunct 2.2 branch, but has not been done on the 2.1
branch.
The attached Runner.patch.txt file contains a patch to do this. I
suggest you try the patch and see if that helps.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
=== modified file 'Mailman/Queue/Runner.py'
--- Mailman/Queue/Runner.py 2008-05-08 03:42:28 +
+++ Mailman/Queue/Runner.py 2008-12-19 20:59:20 +
@@ -20,7 +20,6 @@
import time
import traceback
-import weakref
from cStringIO import StringIO
from Mailman import mm_cfg
@@ -198,22 +197,18 @@
if keepqueued:
self._switchboard.enqueue(msg, msgdata)
-# Mapping of listnames to MailList instances as a weak value dictionary.
-_listcache = weakref.WeakValueDictionary()
-
def _open_list(self, listname):
-# Cache the open list so that any use of the list within this process
-# uses the same object. We use a WeakValueDictionary so that when the
-# list is no longer necessary, its memory is freed.
-mlist = self._listcache.get(listname)
-if not mlist:
-try:
-mlist = MailList.MailList(listname, lock=False)
-except Errors.MMListError, e:
-syslog('error', 'error opening list: %s\n%s', listname, e)
-return None
-else:
-self._listcache[listname] = mlist
+# We no longer cache the list instances. Because of changes to
+# MailList.py needed to avoid not reloading an updated list, caching
+# is not as effective as it once was. Also, with OldStyleMemberships
+# as the MemberAdaptor, there was a self-reference to the list which
+# kept all lists in the cache. Changing this reference to a
+# weakref.proxy created other issues.
+try:
+mlist = MailList.MailList(listname, lock=False)
+except Errors.MMListError, e:
+syslog('error', 'error opening list: %s\n%s', listname, e)
+return None
return mlist
def _log(self, exc):
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Footers As Attachments
On 3/12/2010 11:01 AM, Mark Sapiro wrote: Zone Page wrote: I've been using Mailman for a long time for several small lists that I maintain. There are two configuration issues that I still do not understand. First, messages sent to participants have the footer as an attachment. The only way I could get rid of the attachment was to delete the footer text. The messages on this list have the footer, and it is not showing up as an attachment, so I am doing something wrong. See the FAQ at http://wiki.list.org/x/84A9 I already read that article, but it's over my head. The footers are not (usually) separate MIME parts on this list because people tend to post plain text, and this list uses Mailman's content filtering to remove non plain text parts from posts so the footers can be added to the simple plain text message body. Is that Option 2? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Footers As Attachments
Zone Page wrote: On 3/12/2010 11:01 AM, Mark Sapiro wrote: The footers are not (usually) separate MIME parts on this list because people tend to post plain text, and this list uses Mailman's content filtering to remove non plain text parts from posts so the footers can be added to the simple plain text message body. Is that Option 2? Yes, that's option 2. Note, if your list is an announcement type of list, and you want to post HTML (rich text), you can always remove the list's msg_footer and just include the equivalent at the bottom of your posts. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Footers As Attachments
On 3/12/2010 1:07 PM, Mark Sapiro wrote: Zone Page wrote: On 3/12/2010 11:01 AM, Mark Sapiro wrote: The footers are not (usually) separate MIME parts on this list because people tend to post plain text, and this list uses Mailman's content filtering to remove non plain text parts from posts so the footers can be added to the simple plain text message body. Is that Option 2? Yes, that's option 2. Note, if your list is an announcement type of list, and you want to post HTML (rich text), you can always remove the list's msg_footer and just include the equivalent at the bottom of your posts. The page says, Choosing option #2 from the above list is quite a bit more difficult to configure than you may think it is. Even if you can get the system to do this, the result would most likely be quite a bit more drastic than you think. So, how do I configure my list this way? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Messages not departing
I have a number of messages stuck between qfiles/retry and qfiles/out, and for about a week or so, messages have been departing very sporadically. Checking logs/error, I noticed a glitch in parser.py, which I stuck up on a pastebin, here: http://pastebin.ca/1835827 I'm running Debian Etch (old stable) on the server, current version of mailman from the repository (2.1.9-7), kernel 2.6.18-5-686. Any idea what's going on per the pastebin? -Dennis Carr -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Footers As Attachments
Zone Page wrote: The page says, Choosing option #2 from the above list is quite a bit more difficult to configure than you may think it is. Even if you can get the system to do this, the result would most likely be quite a bit more drastic than you think. So, how do I configure my list this way? Here's one suggestion. filter_content: Yes filter_mime_types: empty pass_mime_types: multipart message/rfc822 text/plain text/html filter_filename_extensions: default (it doesn't matter much with the above in pass_mime_types) pass_filename_extensions: empty collapse_alternatives: Yes convert_html_to_plaintext: Yes This will ensure only plain text is delivered to the list and will accept essentially all text/plain parts of a message and in addition will accept HTML that is not a multipart/alternative sub-part and use an external command (defaults to lynx) to convert the HTML to plain text. It will break or remove signatures from some signed mail. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Messages not departing
Dennis Carr wrote: I have a number of messages stuck between qfiles/retry and qfiles/out, and for about a week or so, messages have been departing very sporadically. Checking logs/error, I noticed a glitch in parser.py, which I stuck up on a pastebin, here: http://pastebin.ca/1835827 That has nothing to do with outgoing mail in out/ or retry/. It is a message that had defective MIME structure as indicated. It was possibly truncated somewhere along the delivery path to Mailman, but more likely was just spam with a defective MIME structure. It was queued in qfiles/in/ by the MTA and the exception occurred when IncomingRunner picked it up from the in/ queue and tried to parse it into an email.Message.Message instance for processing. As it says, that message was ignored. As far as the retries and slow delivery are concerned, look at Mailman's smtp-failure log for the reason the messages are queued for retry. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Messages not departing
On Fri, 12 Mar 2010 12:01:58 -0800 Mark Sapiro m...@msapiro.net wrote: Dennis Carr wrote: I have a number of messages stuck between qfiles/retry and qfiles/out, and for about a week or so, messages have been departing very sporadically. Checking logs/error, I noticed a glitch in parser.py, which I stuck up on a pastebin, here: http://pastebin.ca/1835827 That has nothing to do with outgoing mail in out/ or retry/. It is a message that had defective MIME structure as indicated. It was possibly truncated somewhere along the delivery path to Mailman, but more likely was just spam with a defective MIME structure. It was queued in qfiles/in/ by the MTA and the exception occurred when IncomingRunner picked it up from the in/ queue and tried to parse it into an email.Message.Message instance for processing. As it says, that message was ignored. As far as the retries and slow delivery are concerned, look at Mailman's smtp-failure log for the reason the messages are queued for retry. OK, here's what I found: Mar 12 10:08:11 2010 (31200) delivery to xell...@slayers.org failed with code 45 0: 4.1.2 x...@slayers.org: Recipient address rejected: Domain not found I've found similar messages with x...@fanfic.net at the end. Certainly mailman should be running these as bounces? Moreover, I should note that many of the users are not getting messages, and in logs/smtp, I see messages such as this: Mar 12 13:32:35 2010 (31200) 905831dc1003100904u3451a9b7kbc405d64f96d9...@mail.gmail.com smtp to ffml for 2 recips, completed in 60.504 seconds (Note that this is normally right around 1,000 recips.) Semi-related message from logs/post: Mar 12 13:35:37 2010 (31200) post to ffml from dennistheti...@chez-vrolet.net, size=1444, message-id=pine.lnx.4.64.1003121020550.31...@kimba.chez-vrolet.net, 2 failures In short, what's up, and how to fix this? -Dennis -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Messages not departing
OK, here's what I found: Mar 12 10:08:11 2010 (31200) delivery to xell...@slayers.org failed with code 45 0: 4.1.2 x...@slayers.org: Recipient address rejected: Domain not found I've found similar messages with x...@fanfic.net at the end. Certainly mailman should be running these as bounces? Note that the SMTP error code is 450, which is a retryable error; it is not a permanent error. The domain slayers.org may be one that does not exist, or it may be that at the time the mail is queued, the relevant name servers are offline or misconfigured so that the MTA cannot tell if the domain really exists. The MTA and Mailman cannot be sure. In this case, the MTA will keep trying for the queue length time in its configuration file. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: bsfin...@anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Messages not departing
Dennis Carr wrote: OK, here's what I found: Mar 12 10:08:11 2010 (31200) delivery to xell...@slayers.org failed with code 45 0: 4.1.2 x...@slayers.org: Recipient address rejected: Domain not found I've found similar messages with x...@fanfic.net at the end. Certainly mailman should be running these as bounces? It would if your MTA returned a 5xx status instead of a 450. Moreover, I should note that many of the users are not getting messages, and in logs/smtp, I see messages such as this: Mar 12 13:32:35 2010 (31200) 905831dc1003100904u3451a9b7kbc405d64f96d9...@mail.gmail.com smtp to ffml for 2 recips, completed in 60.504 seconds (Note that this is normally right around 1,000 recips.) Semi-related message from logs/post: Mar 12 13:35:37 2010 (31200) post to ffml from dennistheti...@chez-vrolet.net, size=1444, message-id=pine.lnx.4.64.1003121020550.31...@kimba.chez-vrolet.net, 2 failures In short, what's up, and how to fix this? If this started, what changed in your MTA configuration? Or your DNS? What is apparently happening is you are getting failurs and the message is queued for retry and there may be a couple of addresses that get accepted. I suspect a DNS issue with the MTA's lookups of the recipient domains. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mail to all users
Hi I am fairly new to mailman, and have a weekly newsletter that I send out. How can I know if the mail is send to all the users, because I have my one email address on the list but does not receive the mail that I send to the list. Thanks Wynand Louw -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] 3rd party email unsubscribe request fails
Folks, I have recently set up Mailman version 2.1.13. Everything works as expected except for the email form I use on my website to unsubscribe folks. It takes and email address submission and composes an email to listname-requ...@listserv.mydomain.org with body of: unsubscribe address=submit...@email.adr end apache gets an email response from mailman as follows: ... The results of your email command are provided below. Attached is your original message. - Results: Usage: unsubscribe [password] [address=address] Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish to unsubscribe an address other than the address you sent this request from, you may specify `address=address' (no brackets around the email address, and no quotes!) - Unprocessed: unsubscribe address=exam...@yahoo.com end - Done. I have a similar form for subscribe requests that works as expected. my webserver sends the requests as apa...@mydomain.org. It is not an admin, moderator, or list member of the list I am trying to modify. Is there something wrong with apa...@mydomain.org sending the unsubscribe request? As I understand it, if the request is sent w/o password, the user must confirm the request -- which is exactly what I want. Regards, -- -- Michael Y! darthwonka --- - - __o -- _ \,_ (_)/ (_) I have not failed. I've just found 10,000 ways that won't work. - Thomas A. Edison -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Remove / Strip Sender Signature Question
Hi All I searched archives and checked faq but couldn't find this, apologies if I'm keyword 'tarded this morning. Is it possible to strip the Sender Signature? Our lists are subscribed to some other lists, and we're having problems with members unsubscribing us from those lists instead of unsubbing from ours. Thanks in advance, any help appreciated, moose -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mail to all users
Wynand Louw wrote: How can I know if the mail is send to all the users, because I have my one email address on the list but does not receive the mail that I send to the list. Unless you have not metoo checked in your entry in the admin Membership Management... - Membership List pages, you should receive your own posts to the list. The answer to your question though is in general, you can't. If you have enabled bounce processing and you have sufficient access, you can see if there are bounces recorded in Mailman's bounce log, and you can check the outgoing MTA's log to see if the messages were successfully delivered to the recipient's incoming mail servers, but ifen that is no guarantee that the message was delivered to the recipient's mailbox. If you have an address subscribed to the list that should receive the mail, and it does, you can be reasonably confident that the mail was sent to all eligible recipients, but you can't know that it was received by all. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 3rd party email unsubscribe request fails
Michael Belanger wrote: I have recently set up Mailman version 2.1.13. Everything works as expected except for the email form I use on my website to unsubscribe folks. It takes and email address submission and composes an email to listname-requ...@listserv.mydomain.org with body of: unsubscribe address=submit...@email.adr end apache gets an email response from mailman as follows: ... The results of your email command are provided below. Attached is your original message. - Results: Usage: unsubscribe [password] [address=address] Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish to unsubscribe an address other than the address you sent this request from, you may specify `address=address' (no brackets around the email address, and no quotes!) - Unprocessed: unsubscribe address=exam...@yahoo.com end This was solved on the #mailman irc channel after the post was submitted, but before it was approved. The unsubscribe address=exam...@yahoo.com command in the message body was unprocessed because there was an invalid command in the subject. The subject was Remove from my email List and remove is a synonym for unsubscribe, so the subject looked like an unsubscribe command with syntax errors and produced the Usage: message for 'unsubscribe'. Emails to the -request address can contain commands in the Subject: header. UnVERPed confirmations in particular work this way. Thus, if the Subject is not intended to be a command, it must not begin with any of the following email command words: confirm echo end help info join leave lists password remove set stop subscribe unsubscribe who or it will be interpreted as a command and if it contains an error, will abort processing of the actual command(s). -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Remove / Strip Sender Signature Question
Artabase wrote:
I searched archives and checked faq but couldn't find this, apologies if
I'm keyword 'tarded this morning.
Is it possible to strip the Sender Signature?
What is the sender signature?
Our lists are subscribed to some other lists, and we're having problems
with members unsubscribing us from those lists instead of unsubbing from
ours.
Do you mean that your list is subscribed to some other list, and the
other list adds a footer similar to the following:
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/yourlist%40yourdomain
and then members of your list see that footer, follow the Unsubscribe
link, request unsubscription, and then receive the confirmation (sent
to your list) and confirm the unsubscribe?
If that's what you mean, you have a couple of choices. Mailman has no
facility for removing that footer from the post to your list, but you
can add your own footer with a message something like
DO NOT USE THE ABOVE LINK TO UNSUBSCRIBE!
To unsubscribe from this list, go to http://... or send a blank email
to yourlist-unsubscr...@yourdomain.
Or you could add header_filter_rules to your list with regexps like
^subject:\s*confirm [0-9a-f]{32}\s*$
^from:.*-confirm\+[0-9a-f]{32}@
and an action of Discard to prevent the confirmations from reaching
your list.
Of course someone with intent to unsubscribe your list from the remote
list could always request a password reminder from the remote list
which would be posted to your list, and then use the password to
unsubscribe without confirmation.
You could add
^subject:\s*[...@]+@[^\s]+\s+mailing list reminder\s*$
to the regexps above to stop the password reminders too.
If the above is not the scenario that you are encountering, then please
be more specific about exactly what it is.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
