Mailman 3 October 2010 - Mailman-Users

Mailman 2.1.12 can't accept email from Thunerbird 3.1.4 help!
by wilby 01 Oct '10

01 Oct '10

For some reason a very recent update to Thunderbird 3.1.4 email has suddenly stopped the Mailman 2.1.12 account, that I administer, from accepting my messages. I can send to this Mailman account from non-Tbird email software. Help needed badly. Thanks, Wilby -- View this message in context: http://old.nabble.com/Mailman-2.1.12-can%27t-accept-email-from-Thunerbird-3… Sent from the Mailman - Users mailing list archive at Nabble.com.

2 4

Re: [Mailman-Users] Mailman-Users Digest, Vol 80, Issue 2
by Troy Campbell 01 Oct '10

01 Oct '10

Thanks again Mark. I've decided to manage it with separate postfix config files (one for when there is no service group on a server, one for when there is just the Mailman service group, one for when there is just the IMAP service group and one when there is both) and just restart postfix and monitor it as part of VCS as it doesn't make sense to merge config files for other reasons anyway. Regards, Troy -----Original Message----- Troy Campbell wrote: >For some reason when I moved the mailman configuration a few months ago >I had to add /etc/mailman/aliases to the alias_maps e.g.,: > >alias_maps = hash:/etc/aliases > > hash:/etc/mailman/aliases > > > >whereas on the old installation I didn't. Since this is on a server >that can fail over to another server that has the IMAP configuration >which > >doesn't need /etc/mailman/aliases I would like to see if there is a >workaround so that they both have the same postfix configuration. >Sorry > >if this is more of a postfix question but I didn't get an answer on >their list yet. Postfix doesn't do IMAP, nor do other MTAs, so I'm not sure if the IMAP reference is relevant. Is the Mailman package on the other server the same as the one on this server which is clearly a downstream package if aliases are in /etc/mailman. >Basically trying to get the /etc/postfix/main.cf files identical so I >don't have to manage the differences and bounce postfix on failover. If Mailman is installed the same way from the same package on both servers, and there are no non-mailman differences in the Postfix configuration, there should be no reason why they couldn't use the same main.cf. On the other hand if the two servers have different Mailman packages, then their Postfix requirements could be different. On the third hand, this could be simply that on the other server, Mailman's aliases were copied to /etc/aliases so /etc/mailman/aliases wasn't needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Hold.py fails in hold_for_approval
by Morris Jones 01 Oct '10

01 Oct '10

I recently discovered that all of my moderated posts have been failing, most likely because my mailman version was older than my python version. This is the error: Sep 29 20:52:12 2010 (5588) Uncaught runner exception: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) Sep 29 20:52:12 2010 (5588) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop filebase) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 169, in _onefile 'Dequeuing message destined for missing list: %s', 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/Moderate.py", line 67, in process msgdata['sender'] = sender File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 212, in hold_for_approval if usersubject: TypeError: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) Sep 29 20:52:12 2010 (5588) SHUNTING: 1285818731.142787+9ceab13e8549d5e6690de9b9880bef9c7c238b8d My python version is 2.6.2, and I've been very careful to be sure that older pythons are not in the PATH. The first thing I did was update mailman to 2.1.14, which seemed to go just fine, but I still see this error. The timestamps of all the executables are current, and were overwritten by the new versions. The "version' command reports 2.1.14. Actually ... I see now that the actual line of code changed after installing the new version of mailman. Where it used to be: reason = Utils.wrap(exc.reason_notice()) it's now ... if usersubject: So it would appear that I need to get python to recompile all the pyc files, is that correct? How do I do that? I tried touching the .py files to make them newer ... Sorry, not a python guru ... Mojo -- Morris Jones, Monrovia, CA http://bridgemojo.com http://otastro.org http://mojo.whiteoaks.com

2 1

/etc/mailman/aliases.db
by Troy Campbell 01 Oct '10

01 Oct '10

For some reason when I moved the mailman configuration a few months ago I had to add /etc/mailman/aliases to the alias_maps e.g.,: alias_maps = hash:/etc/aliases hash:/etc/mailman/aliases whereas on the old installation I didn't. Since this is on a server that can fail over to another server that has the IMAP configuration which doesn't need /etc/mailman/aliases I would like to see if there is a workaround so that they both have the same postfix configuration. Sorry if this is more of a postfix question but I didn't get an answer on their list yet. Basically trying to get the /etc/postfix/main.cf files identical so I don't have to manage the differences and bounce postfix on failover. Regards, Troy

2 1

Digest options as email attachments
by Danny hendrawan 01 Oct '10

01 Oct '10

?Hi, I'd like to have my members list who choose to receive a digest mail to receive similar to the digest of this list i.e. with summary page and attachment emails for each topic. I looked at 'digest options' but cannot find anything to enable this option. Where can I set it up? Thanks, Danny

2 1