Mailman 3 January 2009 - Mailman-Users

moving discarded emails to an archive somewhere
by Luke Daly 22 Jan '09

22 Jan '09

Hi Guys is there a way to move discarded emails to another list? I have been asked if we can retain the email's that are discarded due to not having perms to send to the list be moved to another list for archiving purposes.

4 3

re-set Digest volume numbering
by Terry Boom 22 Jan '09

22 Jan '09

I have searched the archives and seen the question posted frequently, but never answered. Is there a way to re-set digest numbering in Mailman? Thanks. Terry Boom

2 1

Re: [Mailman-Users] Email address with trailing space
by Marion Bates 21 Jan '09

21 Jan '09

Sorry for the antique thread bump here, but it was the top hit for my "mailman address trailing space" search, so I thought I'd contribute. ------------------------------------- Re: [Mailman-Users] Email address with trailing space Wed, 10 Jan 2007 10:38:22 -0800 Trader Joe wrote: >While doing "mass subscription", I accidently put in >an extra space at the end of several email addresses >and now I'm unable to unsubscribe or remove these >email via Web tools. Anyone know how to remove these? ----------------------------------------------------------------------------------------- I had the same issue -- version 2.1.9 under Fedora Core 9. The email address had a trailing space, and attempts to delete it via the web interface resulted in nothing more than a page refresh, with the address still subscribed; the remove_members script reported "No such member" whether I passed it the address with a space, an escaped space, or no space. A later reply included a now-dead link to part of the FAQ. I looked at the archived version here: http://web.archive.org/web/20070221134632/http://www.python.org/cgi-bin/faq… But those suggestions didn't work in my case. So I grepped the list_members output for just the "correct" part of my bad email address, and lo and behold, the problematic address looked like this: user.name(a)domain.com\&#160 That's the entity code for a non-breaking space, which I imagine ended up in MM from a copy-paste from rich email. Leveraging another suggestion in this old thread, I was able to remove it but had to escape the ampersand: ./remove_members mylistname user.name(a)domain.com\&#160 In case this is helpful to anyone else. Thanks, all! -- MB

1 0

Preserving S/MIME-Encoded Mail
by b19141＠anl.gov 20 Jan '09

20 Jan '09

I have a collegue who is experimenting with signed mail (S/MIME). He sent me a test mail and he also sent it to a test Mailman (2.1.11) list. Here is the basic MIME header structure for the mail sent directly to me: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MIME-Version: 1.0 Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0000_01C97713.0AE16F40" This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C97713.0AE16F40 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0001_01C97713.0AE16F40" ------=_NextPart_001_0001_01C97713.0AE16F40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit <<the body of the mail>> ------=_NextPart_001_0001_01C97713.0AE16F40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <<the body of the mail in HTML-format>> ------=_NextPart_001_0001_01C97713.0AE16F40-- ------=_NextPart_000_0000_01C97713.0AE16F40 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" <<the base64-encoded digital signature>> ------=_NextPart_000_0000_01C97713.0AE16F40-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ And here is the MIME structure after Mailman has processed the mail: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4389576766350830338==" This is a multi-part message in MIME format. --===============4389576766350830338== Content-class: urn:content-classes:message Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0000_01C97713.0AE16F40" This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C97713.0AE16F40 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0001_01C97713.0AE16F40" ------=_NextPart_001_0001_01C97713.0AE16F40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit <<the body of the mail>> ------=_NextPart_001_0001_01C97713.0AE16F40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <<the body of the mail in HTML-format>> ------=_NextPart_001_0001_01C97713.0AE16F40-- ------=_NextPart_000_0000_01C97713.0AE16F40 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" <<the base64-encoded digital signature>> ------=_NextPart_000_0000_01C97713.0AE16F40-- --===============4389576766350830338== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline <<the mailman-inserted footer>> --===============4389576766350830338==-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Note that Mailman has taken the existing three-part MIME structure (plain-text body, HTML-formatted body, and digital signature) and instead of placing the list footer as a fourth part in the same MIME structure, Mailman has created a new two-part MIME structure with the original three-part MIME structure as a first part and the list footer as a second part. While this resulting structure is valid MIME-encoding (I think), the result is that the initial header lines Content-class: urn:content-classes:message Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0000_01C97713.0AE16F40" are not at the beginning of the MIME structure. I believe that this is causing the mail to appear as an unsigned mail message. I have just begun reading "S/MIME 3.1" RFC 3851, and my initial quick reading leads me to believe that this Content-Type: multipart/signed; header line needs to appear in the first part of the MIME headers and not within a subsidiary MIME header. Is there a reason why Mailman does not place the list footer as a fourth section in the existing MIME structure? Thanks. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

5 11

Mailman doesnt deliver after server migration
by jknowlton＠vp44.com 20 Jan '09

20 Jan '09

Hi all. I recently moved my mailman installation to a new server and now the lists refuse to work. Emails to the lists enter postfix and are delivered to the mailman service but won't be forwarded to the subscribers. I'm pretty sure it must be a permissions problem but I ran several times (as root and as user "list") check_perms -f and it says all is fixed. The web interface for the archives works ok. This is my error log: Jan 19 11:33:19 2009 (1838) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/lists/sottomessi/digest.mbox' Jan 19 11:33:19 2009 (1838) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 77, in process mboxfp = open(mboxfile, 'a+') IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/sottomessi/digest.mbox' Jan 19 11:33:19 2009 (1838) SHUNTING: 1232361198.639926+de15be9465eda20d7e81b720ee14e85fd1ff7232 Thanks. -JK

2 1

Change of domain for existing mailman list
by Grant Robinson [IAIDQ] 20 Jan '09

20 Jan '09

I previously used forum(a)domain.org as the email address for my mailman list, set up via Cpanel. So the list is known as forum_domain.org For various reasons I changed the email service of my domain.org to Gmail with the MX records, and now forum(a)domain.org does not work with mailman any more Is it possible to rename the mailman folders and configuration to run in a subdomain with email address forum(a)forum.domain.org retaining the archive? Surely someone has changed domain names before and ported their mailman installation. We just can;t find this on the online doco or discussion forum/fora. -- --- Cheers Grant Robinson

2 1

How to manually get a list of passwords for all members to be sent to the administration
by Steve Campbell 19 Jan '09

19 Jan '09

The subject line states the full question, but, I'd like to get a list of passwords for all the members to be sent to the administrator. I usually mass subscribe them in the form Common name <email address> so I don't have the option to insert the password and don't know them. At least I'm not aware of how to do it. Also, is there a way to add the preferred password when mass adding names? I'm running 2.1.5. Thanks Steve Campbell

4 8

Re: [Mailman-Users] Gathering additional iniformation at signup
by Jan Steinman 19 Jan '09

19 Jan '09

> From: Hank van Cleef > > The esteemed Mark Sapiro has said: >> >> Walter wrote: >> >>> I have just started using Mailman and wish to add fields (user >>> title, organization) that must be filled out upon subscription... >> >> In other words, this is not a simple change. > > ... I've > given some thought to redoing things so that a custom page can link > out to a non-Mailman process, then return the mail address and real > name to Mailman as an approved subscription for Mailman processing... This is not terribly difficult to do, if you have some basic HTML programming experience. One could (for example) build a POST form to gather all the information, then in the POST target file, scrape off all the extra info, stuff it in a database, then POST the name and email address to the appropriate Mailman page. I posted how to do the latter some time ago: <form action="http://your.domainname.here/mailman/subscribe/listname" method="post"> <input type="text" name="fullname"> <input type="text" name="email"> </form> So just add your additional fields, then change the "action" URL to a PHP (or your web language of choice) page that gathers your info and gets it to you in your desired form, then POSTS the "fullname" and "email" fields to Mailman. And Bob's your uncle! If you don't have the skills, I would be willing to contract the solution for you. Depending on how picky you are and how much customization you want, it could be thirty minutes or thirty days of work... :-) :::: Giving society cheap, abundant energy at this point would be the equivalent of giving an idiot child a machine gun. -- Paul Ehrlich :::: :::: Jan Steinman <http://www.VeggieVanGogh.com> ::::

1 0

Gathering additional iniformation at signup
by Walter 19 Jan '09

19 Jan '09

I have just started using Mailman and wish to add fields (user title, organization) that must be filled out upon subscription and available to the list moderator for approval. I can easily change the subscription form, adding these fields, but where do I go to modify the approval process to display them? I looked thru the archives and I'm guessing that I have to customize something in the admin pages, but where do I begin? Thanks.

4 3

Gratuitous "True".
by Dan Mahoney, System Admin 16 Jan '09

16 Jan '09

Hey all, After updating to 2.1.11 (from BSD ports, against python2.5), I'm seeing that several of my list archives have the word "True" scattered througout (at the bottoms of tables). Something like this: <td>October 2008:</td> <td> <A href="2008-October/thread.html">[ Thread ]</a> <A href="2008-October/subject.html">[ Subject ]</a> <A href="2008-October/author.html">[ Author ]</a> True <A href="2008-October/date.html">[ Date ]</a>  </td> <td><A href="2008-October.txt">[ Text 556 bytes ]</a></td> </tr> </table> True It would appear that the arch command is printing something it shouldn't be (either a config variable or something else?) Anyone have any idea what could be causing this? -Dan -- [23:49:00] LarpGM: Did my little TP comment scare you off? [23:49:22] ilzarion: no, the shrieking retarded child eating people did -Feb 06, 2001, times apparent. --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---------------------------

2 3