Mailman 3 January 2009 - Mailman-Users

FAQ: How To Rename a Mailman List
by b19141＠anl.gov Jan. 5, 2009

Jan. 5, 2009

I need to rename two Mailman 2.1.9 lists. The FAQ 4.70 gives explicit instructions, but it does not mention changing the /var/lib/mailman/data/aliases (location on my Unbutu system) file to reflect the new name and then running the newaliases command. Should this be added to the FAQ? ---------------------------------------------------------------------- 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

2 1

Alternate Port question
by Patrick Healy Jan. 5, 2009

Jan. 5, 2009

Hi, I'm using Mailman v2.1.5. Originally lists were created using port 8181 as the default port. Later port 80 was freed up and I reset (so I thought) everything to port 80. However, whenever something is went out on the list, it still continues to show port 8181 as the port. Any thoughts on how/where to change this? Thanks! Pat Healy

2 1

Re: [Mailman-Users] The economics of spam
by Jan Steinman Jan. 5, 2009

Jan. 5, 2009

> From: Rich Kulawiec <rsk(a)gsp.org> > > On Tue, Dec 23, 2008 at 10:15:43AM -0800, Jan Steinman wrote: >> I would willingly pay a hundredth of a cent (or so) per email sent >> if it >> would reduce spam to near-zero. > > This is a thoroughly-discredited, utterly broken idea... based on > the ludicrous > notion that abusers... will, for absolutely no reason > whatsoever, suddenly and magically behave honestly and pay to send > mail. No, it is based upon the idea that a system could be implemented whereby it would be impossible to avoid the payment. Or should we just admit that any crook can hack any arbitrary ATM machine, or that any mass-marketer can send paper mail without a stamp? I don't believe anyone in this discussion was relying on the ethics of voluntary payments to reduce spam. :::: If vegetarians eat only vegetables, what do humanitarians eat? :::: Jan Steinman <http://www.Bytesmiths.com/Item/99-3033-17-18>

6 12

mailman mailing list members limit?
by abcloans05＠yahoo.com Jan. 5, 2009

Jan. 5, 2009

Hello, I'd like to know if there's a limit on how many members I can have? I have around 2,400 members and when I send an e-mail only few get it. Thank you, Jen

2 1

Rejecting on size before content-filters
by Bernie Cosell Jan. 4, 2009

Jan. 4, 2009

Is it possible to change the testing-order so that the list size limit is tested [and generates an appropriate reject] *before* the content filters are processed? [I just ran into one that was nearly double the maximum size but got kicked out because it also ran afoul of one of the content filters, and so what I ended up doing was ignoring the content filter and putting in "message too long...etc" into the 'Reason' on my bounce screen]. tnx! /Bernie\ -- Bernie Cosell Fantasy Farm Fibers mailto:bernie@fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--

2 6

Warnings from senddigests
by Jesper Dybdal Jan. 4, 2009

Jan. 4, 2009

I've just installed Mailman version 2.1.11. In general, it works fine. Whenever my mailman cron job runs senddigests, I get the following warnings (on stdout or stderr, mailed to me by cron): >/home/mailman/Mailman/Handlers/Scrubber.py:192: DeprecationWarning: get_type() deprecated; use get_content_type() > ctype = part.get_type(part.get_default_type()) >/home/mailman/Mailman/Handlers/Scrubber.py:303: DeprecationWarning: get_type() deprecated; use get_content_type() > ctype = part.get_type() >List: jdtest: problem processing /home/mailman/lists/jdtest/digest.mbox: >iso-8859-15 The first two sounds like very minor problems in Scrubber.py. I wonder about the last one. My test list does have messages in ISO 8815-15 (that is the character set my mail client uses for a message containing the Euro sign - at least if it also contains the Danish non-usascii letters). I currently have to digest subscribers, so I don't know if this a real problem. Does Mailman perhaps simply not support ISO 8859-15? -- Jesper Dybdal, Denmark. http://www.dybdal.dk (in Danish).

2 9

Re: [Mailman-Users] Warnings from senddigests
by b19141＠anl.gov Jan. 4, 2009

Jan. 4, 2009

Jesper Dybdal wrote: > >I think you've diagnosed the problem. There is a pythonlib directory, >but it is empty. Note that the Debian/Ubuntu Mailman package deletes mailman/pythonlib/ Mark Sapiro replied to a posting Wed, 10 Jan 2007 09:48:30 -0800: >Some additional information: > >This is mailman 2.1.8-2ubuntu2. > >The reference to the 'bug fix' is at ><http://changelogs.ubuntu.com/changelogs/pool/main/m/mailman/mailman_2.1.8-2…> >in which is found > > * Make sure we don't ship /var/lib/mailman/pythonlib, should make that > go away on installations which already have it (closes: #242740). > >(I couldn't find a description of #242740). > >The above change seems to have been made some time ago, so perhaps the >issue is caused by some more recent change to the Ubuntu Python email >library. And Todd Zullinger <tmz(a)pobox.com> replied Wed, 10 Jan 2007 13:08:51 -0500 >That looks to be from the Debian Mailman package, which Ubuntu uses as >it's base. See the long trail here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242740 > >The short summary for the bug is "bad installation when >/var/lib/mailman/pythonlib is a symlink." > >(I've never found the Debian bugs page very easy to follow. :) I do not know how the original poster (OP) is building and installing Mailman. This removal of pythonlib is one of the reasons I decided to build my own Mailman package for Ubuntu from the SourceForge source. ---------------------------------------------------------------------- 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

1 0

Automatic bounce processing; listname-bounces vs. listname-bounces+XXXX
by John Wesley Simpson Hibbs Jan. 4, 2009

Jan. 4, 2009

Our mailing lists had been processing bounces correctly for quite some time. For some reason though, this has stopped functioning properly. Bounces were coming back to list-bounces+XXXX, and are now coming back to list-bounces, without the XXXX. The setting "Should Mailman perform automatic bounce processing?" is set to yes. Any help or advice would be greatly appreciated. john What I am getting now: ==================================================================== Subject: Uncaught bounce notification From: mailman-bounces(a)radiolists.net To: mailman-owner(a)radiolists.net Date: Thu, 01 Jan 2009 05:03:56 -0600 Precedence: bulk X-BeenThere: mailman(a)radiolists.net X-Mailman-Version: 2.1.5 List-Id: mailman.radiolists.net X-List-Administrivia: yes Sender: mailman-bounces(a)radiolists.net Errors-To: mailman-bounces(a)radiolists.net The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: http://lists.radiolists.net/mailman/admin/mailman/bounce Return-Path: <> Delivered-To: 9-mailman-bounces(a)radiolists.net Date: 1 Jan 2009 11:03:48 -0000 From: MAILER-DAEMON(a)example.com To: mailman-bounces(a)radiolists.net Subject: failure notice This is the mail delivery agent at example.com. I was not able to deliver your message to the following addresses. <user(a)example.com>: 208.77.188.166 does not like recipient. Remote host said: 550 <user(a)example.com>... User not known --- Below this line is a copy of the message. Return-Path: <mailman-bounces(a)radiolists.net> Subject: radiolists.net mailing list memberships reminder From: mailman-owner(a)radiolists.net To: user(a)example.com Date: Thu, 01 Jan 2009 05:01:05 -0600 Precedence: bulk X-BeenThere: mailman(a)radiolists.net X-Mailman-Version: 2.1.5 List-Id: mailman.radiolists.net X-List-Administrivia: yes Sender: mailman-bounces(a)radiolists.net Errors-To: mailman-bounces(a)radiolists.net This is a reminder, sent out once a month, about your radiolists.net mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request(a)radiolists.net) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner(a)radiolists.net. Thanks! Passwords for user(a)example.com: List Password // URL ---- -------- example_list(a)radiolists.net 123456 http://lists.radiolists.net/mailman/options/example-list/user% 40example.com ==================================================================== -- John Wesley Simpson Hibbs <john(a)swajime.com> SwaJime's Cove

3 6

ANNOUNCE: GNU Mailman 3.0a2 (Grand Designs)
by Barry Warsaw Jan. 3, 2009

Jan. 3, 2009

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Mailpersons, I'm happy to announce the availability of GNU Mailman version 3.0 alpha 2, code name "Grand Designs". Of course, this is still an alpha snapshot and not suitable for production systems, however there is a lot of good functional stuff in this release that is worthy of a look. Because this is still alpha software, you can have a big influence on where the code goes from here. I'm especially interested in feedback from integrators, and I welcome your contribution. Mailman 3.0 alpha 2 should be functional enough to create mailing lists, connect them to your MTA, add and remove members, and send email to those lists. Incoming mail integration is currently only supported for Postfix via LMTP; contributions for other MTAs and incoming mechanisms are welcome. The web interface is still not functional, so for now you have to interact with Mailman via the command line. Please feel free to discuss Mailman 3 development on the mailman- developers mailing list. You can submit branches and bugs to the Launchpad bug tracker at https://bugs.launchpad.net/mailman For detailed information on 3.0a2, please read docs/ALPHA.txt. This file explains how to build Mailman and run the test suite. The docs/ NEWS.txt file contains high level descriptions of what's changed since 3.0a1. Most notably are the new configuration system, the better test suite and installation process, and the new LMTP support. Mailman 3 also contains extensive doctests which explain how certain subsystems work. Please note that Python 2.6 is required. You can download the tarball either from the Cheeseshop or from Launchpad. An egg is available on the Cheeseshop. See: http://pypi.python.org/pypi/mailman/3.0.0a2 https://launchpad.net/mailman/+download for details. I hope you find this second snapshot useful and encouraging. Please participate! Enjoy, B. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAklfuV8ACgkQ2YZpQepbvXGRzACeLPvX9eeaPj4x9viw6qZqxgUA sawAn0iDsOHBMM6+RzfUJSQX9RORZTy/ =tTMG -----END PGP SIGNATURE-----

1 0

rejection messages
by J.A. Terranson Jan. 3, 2009

Jan. 3, 2009

Good Morning, If i reject a posting for exceeding size limits, the reason given will be "no reason given" if I reject using the default interface, and will only state the correct reason (too bog, please trim) if I reject from the "details" interface. This is both unintuitive and wrong: It was held for size, the first notice says it was held for size, and it is rejected for the reason held. Shouldnt the default reason (the reason for being held) be the reject reason? 2.11MM thanks! //Alif -- Yours, J.A. Terranson sysadmin_at_mfn.org 0xpgp_key_mgmt_is_broken-dont_bother "Never belong to any party, always oppose privileged classes and public plunderers, never lack sympathy with the poor, always remain devoted to the public welfare, never be satisfied with merely printing news, always be drastically independent, never be afraid to attack wrong, whether by predatory plutocracy or predatory poverty." Joseph Pulitzer 1907 Speech

2 3