[Mailman-Users] bounce notifications
Hi. Am a novice user. When mailman returns notification of a bounce to an administrator, the content always comes within an attachment. Is there any way of telling it to send the details within the body of the e-mail, because when you have lots there's a great deal of extra clicking involved, and it's more difficult to automatically process the information with code (e.g. within Outlook) Thanks very much Andrew -- 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] bounce notifications
Andrew wrote: When mailman returns notification of a bounce to an administrator, the content always comes within an attachment. Is there any way of telling it to send the details within the body of the e-mail, because when you have lots there's a great deal of extra clicking involved, and it's more difficult to automatically process the information with code (e.g. within Outlook) The only ways to change that would be modifying the source code or using an MUA that displays attached messages inline. The bounce notice is sent as an attached message in order to preserve its headers and MIME structure exactly as Mailman received it. -- 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 current version?
On Nov 18, 2009, at 10:54 PM, Mark Sapiro wrote: And the fact that a couple of days a week I usually spend the entire day away from computers (unless you count the cyclometer on my bicycle). :) I only have a little more to add: * I just got back from 2 weeks of travel, so I've blown my chances at inbox-zero for the year. ;) * I only have time to skim mailman-users. * I'm not going to hold up Mailman 3 final release for lack of u/i. If 3.0 is a stable distribution engine, with a robust API and a data migration strategy, it will be good enough to release. That doesn't mean it will be appropriate for all sites to upgrade, but it will useful to a lot of people anyway. So it's likely you won't see an updated Mailman u/i until 3.1 (or more radically, as a separate project that talks to the API). -Barry PGP.sig Description: This is a digitally signed message part -- 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] Corrupt 'config.pck' file
Hello - I have an issue with my Mailman App. I'm using an OpenBSD server. 3.5 and I have version 2.1.4. When I attempt to go to the web page for the lists for Email groups I get the following mesg: Traceback (most recent call last): File /usr/local/lib/mailman/scripts/driver, line 87, in run_main main() File /usr/local/src/ports/mail/mailman/w-mailman-2.1.4/fake-i386/usr/local/lib/m ailman/Mailman/Cgi/admin.py, line 67, in main File /usr/local/src/ports/mail/mailman/w-mailman-2.1.4/fake-i386/usr/local/lib/m ailman/Mailman/Cgi/admin.py, line 234, in admin_overview File /usr/local/src/ports/mail/mailman/w-mailman-2.1.4/fake-i386/usr/local/lib/m ailman/Mailman/MailList.py, line 128, in __init__ File /usr/local/src/ports/mail/mailman/w-mailman-2.1.4/fake-i386/usr/local/lib/m ailman/Mailman/MailList.py, line 609, in Load MMCorruptListDatabaseError: [Errno 2] No such file or directory: '/var/spool/mailman/lists/aq-ngp-ml/config.db.last' I realize that since I don't have a config.db.last file I looked that the Config.pck and the config.pck.last files and they are both empty. I do not have a backup for this email group so I need to understand how to recreate the config. files. Do I rebuild this from scratch OR is there another way besides rebuilding it? Also can I cp files from other lists and use that as my seed to rebuild? I've also performed a 'dumpdb' and found nothing that I could use. Can anyone provide me the steps to take to rebuild this list? I'm new to mailman so any instructions please be very specific with the directions. Thanks in advance for your comments and support. Regards, Quintin QT Williams IT Operations Manager TeraRecon, Inc. 2955 Campus Dr. Ste 325 San Mateo, CA 94403 O: 650.653.4305 C: 925.640.3537 F: 650.989.6814 -- 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] Personalization - How do I explicitly disable Sender field rewrite
I just upgraded to 2.1.9 and it seems that Personalization now re-writes the Sender or From field on all recipients' emails to use the 'description' of the list. I've been unsuccessful in disabling this unless I delete the description field, but then there would be no description on the listinfo page. Is there a quick entry I can put into mm_cfg.py or modify on one of the other files to disable the Sender/From rewrite? It seems like defaulting to 'No' for personalization starts out ok. Then I change it to 'Yes' and it makes the From field: list description em...@address.blah I want just: em...@address.blah When I change Personalization back to 'No', the effect stays the same. Now I'm unable to get rid of this From field rewrite unless I make a new list. We want Personalization in order to use some variables in the footer, and of course to remedy some external user spam filtering issues. But we don't want the Sender/From field to contain the list's description. -Tim- -- 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] Personalization - How do I explicitly disableSender field rewrite
Tim Van Dyne wrote: I just upgraded to 2.1.9 and it seems that Personalization now re-writes the Sender or From field on all recipients' emails to use the 'description' of the list. I've been unsuccessful in disabling this unless I delete the description field, but then there would be no description on the listinfo page. Is there a quick entry I can put into mm_cfg.py or modify on one of the other files to disable the Sender/From rewrite? This should have nothing to do with personalization. This is controlled by General Options - anonymous_list. It seems like defaulting to 'No' for personalization starts out ok. Then I change it to 'Yes' and it makes the From field: list description em...@address.blah I want just: em...@address.blah When I change Personalization back to 'No', the effect stays the same. Now I'm unable to get rid of this From field rewrite unless I make a new list. I don't understand the interactions you discribe unless you are also making other changes. We want Personalization in order to use some variables in the footer, and of course to remedy some external user spam filtering issues. But we don't want the Sender/From field to contain the list's description. Rewriting of the From: header is controlled only by anonymous_list. If anonymous_list is Yes, the From: is rewritten to Description list posting address; if No, the From: is not rewritten at all. personalize = Yes does not rewrite message headers. It only expands the replacements available for msg_header and msg_footer. personalize = Full Personalization rewrites only the To: to the real name address of the recipient. -- 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] Personalization - How do I explicitly disableSender field rewrite
Tim Van Dyne wrote: I just upgraded to 2.1.9 and it seems that Personalization now re-writes the Sender or From field on all recipients' emails to use the 'description' of the list. I've been unsuccessful in disabling this unless I delete the description field, but then there would be no description on the listinfo page. Is there a quick entry I can put into mm_cfg.py or modify on one of the other files to disable the Sender/From rewrite? This should have nothing to do with personalization. This is controlled by General Options - anonymous_list. I realized about an hour after I sent the message that personalization doesn't affect this. But I didn't know that anonymous_list added the description. It seems like defaulting to 'No' for personalization starts out ok. Then I change it to 'Yes' and it makes the From field: list description em...@address.blah I want just: em...@address.blah When I change Personalization back to 'No', the effect stays the same. Now I'm unable to get rid of this From field rewrite unless I make a new list. I don't understand the interactions you discribe unless you are also making other changes. Has to do with me thinking it was personalization somehow. We want Personalization in order to use some variables in the footer, and of course to remedy some external user spam filtering issues. But we don't want the Sender/From field to contain the list's description. Rewriting of the From: header is controlled only by anonymous_list. If anonymous_list is Yes, the From: is rewritten to Description list posting address; if No, the From: is not rewritten at all. personalize = Yes does not rewrite message headers. It only expands the replacements available for msg_header and msg_footer. personalize = Full Personalization rewrites only the To: to the real name address of the recipient. Thank you for pointing this out, I will take into account this new direction with 'General Options - anonymous_list' and see if I can get things working the way we want it. -- 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] Corrupt 'config.pck' file
Quintin T. Williams wrote: Hello - I have an issue with my Mailman App. I'm using an OpenBSD server. 3.5 and I have version 2.1.4. When I attempt to go to the web page for the lists for Email groups I get the following mesg: Traceback (most recent call last): [...] File /usr/local/src/ports/mail/mailman/w-mailman-2.1.4/fake-i386/usr/local/lib/mailman/Mailman/MailList.py, line 609, in Load MMCorruptListDatabaseError: [Errno 2] No such file or directory: '/var/spool/mailman/lists/aq-ngp-ml/config.db.last' I realize that since I don't have a config.db.last file I looked that the Config.pck and the config.pck.last files and they are both empty. When the config.pck for a list is non-existent or unreadable, Mailman tries to fall back to config.pck.last and then to the Mailman 2.0.x files config.db and config.db.last. When it ultimately throws the MMCorruptListDatabaseError exception, it reports the status from the last file it tried which often is the No such file or directory: .../config.db.last because most 2.1.x installations don't have the old config.db files. I do not have a backup for this email group so I need to understand how to recreate the config. files. Do I rebuild this from scratch OR is there another way besides rebuilding it? Also can I cp files from other lists and use that as my seed to rebuild? I've also performed a 'dumpdb' and found nothing that I could use. Can anyone provide me the steps to take to rebuild this list? You effectively need to recreate the list configuration and membership from scratch. I think the easiest thing is to remove the config.pck and config.pck.last from the lists/LISTNAME/ directory and then create a new LISTNAME list and proceed to configure it and add members. I'm new to mailman so any instructions please be very specific with the directions. rm /var/spool/mailman/lists/aq-ngp-ml/config* /path/to/mailman/bin/newlist aq-ngp-ml Then you can use the web admin interface to configure the lis and mass subscribe the members. This will leave the existing archives intact. -- 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] Personalization - How do I explicitly disableSender field rewrite
Tim Van Dyne wrote: I realized about an hour after I sent the message that personalization doesn't affect this. But I didn't know that anonymous_list added the description. The description was added in Mailman 2.1.6. -- 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] Personalization - How do I explicitly disableSender field rewrite
I'm assuming I would change $prefix/Mailman/Handlers/Cleanse.py somehow
then.
So, of this, what would I change?:
if mlist.anonymous_list:
syslog('post', 'post to %s from %s anonymized',
mlist.internal_name(), msg.get('from'))
del msg['from']
del msg['reply-to']
del msg['sender']
# Hotmail sets this one
del msg['x-originating-email']
i18ndesc = str(uheader(mlist, mlist.description, 'From'))
msg['From'] = formataddr((i18ndesc, mlist.GetListEmail()))
msg['Reply-To'] = mlist.GetListEmail()
Or am I going in the wrong direction? I'm looking to just take the
description
out of the equation for anonymous_list.
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, November 19, 2009 2:31 PM
To: Tim Van Dyne; mailman-users@python.org
Subject: RE: [Mailman-Users] Personalization - How do I explicitly
disableSender field rewrite
Tim Van Dyne wrote:
I realized about an hour after I sent the message that personalization
doesn't affect this. But I didn't know that anonymous_list added the
description.
The description was added in Mailman 2.1.6.
--
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] Personalization - How do I explicitly disableSender field rewrite
Tim Van Dyne wrote: I'm assuming I would change $prefix/Mailman/Handlers/Cleanse.py somehow then. So, of this, what would I change?: [...] msg['From'] = formataddr((i18ndesc, mlist.GetListEmail())) Change the above line to msg['From'] = mlist.GetListEmail() -- 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] Personalization - How do I explicitly disableSender field rewrite
Tim Van Dyne wrote: I'm assuming I would change $prefix/Mailman/Handlers/Cleanse.py somehow then. So, of this, what would I change?: [...] msg['From'] = formataddr((i18ndesc, mlist.GetListEmail())) Change the above line to msg['From'] = mlist.GetListEmail() Right before you sent that out I found the same exact thing here: http://mail.python.org/pipermail/mailman-users/2003-October/032475.html Thanks so much for the help. Problem solved. -- 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
