[Mailman-Users] Empty module name again
One of my lists just up and quit on me;
looks like the problem described here
http://mail.python.org/pipermail/mailman-developers/2004-February/016511.html
I run about 20 other lists and the only one affected is the one that is
set to work in French. All the others are just fine. On June 1, mailman
stopped delivering mail on the French list. Nothing that I know of was
changed on the system. This one list just stopped delivering mail. I
can see the MTA invoke the 'post' script and I can see the message end
up in the qfiles/shunt directory.
See trace below,,,
Currently I have mailman 2.1.5 running under python 2.3.4 and RH9 Linux
MTA is sendmail 8.12.11, webserver is Apache 2.0.40
Things I've tried already:
0. Ran check_perms.
1. Installed scrubber patch 2.1.4 and reinstalled (as per the related
URL above)
2. Upgraded Python from RH RPM version 2.2.2 to source compiled version 2.3.4
3. Upgraded from 2.1.4 to 2.1.5 and reinstalled
4. Installed scrubber patch in 2.1.5 again and reinstalled again.
Through all this the other 20 lists apparently continue to function fine.
Here is the trace from the logs/errors
Jun 04 23:44:42 2004 (21659) Uncaught runner exception: Empty module name
Jun 04 23:44:42 2004 (21659) Traceback (most recent call last):
File /home/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /home/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /home/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /home/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 91, in process
send_digests(mlist, mboxfp)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 313, in
send_i18n_digests
uh = Utils.wrap('%s: %s' % (h, oneline(msg[h], lcset)))
File /home/mailman/Mailman/Handlers/ToDigest.py, line 390, in oneline
ustr = h.__unicode__()
File /home/mailman/pythonlib/email/Header.py, line 225, in __unicode__
uchunks.append(unicode(s, str(charset)))
File /usr/local/lib/python2.3/encodings/__init__.py, line 84, in
search_function
globals(), locals(), _import_tail)
ValueError: Empty module name
Jun 04 23:44:42 2004 (21659) SHUNTING:
1086417881.2896941+d6825c4106baed1e1951a1add26ebf40ab9b0124
Searching for the listname (vph) in logs/post shows last message was June 1.
Jun 01 06:40:48 2004 (1842) post to vph from [EMAIL PROTECTED], size=2933, message-id=
[EMAIL PROTECTED], success
Thanks for any suggestions for more things I can try.
--
Brian Wilson
Corvallis, Oregon
541-368-4120
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Empty module name again
Hi
This patch should work.
--- ToDigest.py.origSat Jun 5 18:54:11 2004
+++ ToDigest.py Sat Jun 5 18:55:22 2004
@@ -390,6 +390,6 @@
ustr = h.__unicode__()
oneline = UEMPTYSTRING.join(ustr.splitlines())
return oneline.encode(cset, 'replace')
-except (LookupError, UnicodeError):
+except (LookupError, UnicodeError, ValueError):
# possibly charset problem. return with undecoded string in
one line.
return EMPTYSTRING.join(s.splitlines())
Brian Wilson wrote:
One of my lists just up and quit on me;
looks like the problem described here
http://mail.python.org/pipermail/mailman-developers/2004-February/016511.html
I run about 20 other lists and the only one affected is the one that is
set to work in French. All the others are just fine. On June 1, mailman
stopped delivering mail on the French list. Nothing that I know of was
changed on the system. This one list just stopped delivering mail. I
can see the MTA invoke the 'post' script and I can see the message end
up in the qfiles/shunt directory.
See trace below,,,
Currently I have mailman 2.1.5 running under python 2.3.4 and RH9 Linux
MTA is sendmail 8.12.11, webserver is Apache 2.0.40
Things I've tried already:
0. Ran check_perms.
1. Installed scrubber patch 2.1.4 and reinstalled (as per the related
URL above)
2. Upgraded Python from RH RPM version 2.2.2 to source compiled version 2.3.4
3. Upgraded from 2.1.4 to 2.1.5 and reinstalled
4. Installed scrubber patch in 2.1.5 again and reinstalled again.
Through all this the other 20 lists apparently continue to function fine.
Here is the trace from the logs/errors
Jun 04 23:44:42 2004 (21659) Uncaught runner exception: Empty module name
Jun 04 23:44:42 2004 (21659) Traceback (most recent call last):
File /home/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /home/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /home/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /home/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 91, in process
send_digests(mlist, mboxfp)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /home/mailman/Mailman/Handlers/ToDigest.py, line 313, in
send_i18n_digests
uh = Utils.wrap('%s: %s' % (h, oneline(msg[h], lcset)))
File /home/mailman/Mailman/Handlers/ToDigest.py, line 390, in oneline
ustr = h.__unicode__()
File /home/mailman/pythonlib/email/Header.py, line 225, in __unicode__
uchunks.append(unicode(s, str(charset)))
File /usr/local/lib/python2.3/encodings/__init__.py, line 84, in
search_function
globals(), locals(), _import_tail)
ValueError: Empty module name
Jun 04 23:44:42 2004 (21659) SHUNTING:
1086417881.2896941+d6825c4106baed1e1951a1add26ebf40ab9b0124
Searching for the listname (vph) in logs/post shows last message was June 1.
Jun 01 06:40:48 2004 (1842) post to vph from [EMAIL PROTECTED], size=2933, message-id=
[EMAIL PROTECTED], success
Thanks for any suggestions for more things I can try.
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?
Hello, I'm a bit in a loss here: I was running Mailman 2.1.2 on Debian 3.0 with no problems. Using apt-get... to upgrade Mailman to 2.1.4 produced an error. Well, besides the fact that all my archives got deleted (why would a script (!) do that??), I finally got Mailman back up and running version 2.1.4. I had to fix a zillion permissions, and it took me forever. Probably not a Mailman-thing, I know, and the package-maintainer isn't my friend, I can tell you that. But the following should be only Mailman-related: After having fixed the web_page issue I could even access my lists. All of them. But then the disaster: I have lost some 3.500 subscribers in 3 different lists. Many other lists have been untouched, at least no loss there. I do not understand why only those 3 were affected any why anything got lost there in the first place. The status is, that I have a config.pck that is way smaller than my old ones in backup (e.g. 163 KB versus 533 KB). I'm missing _a lot_ of subscribers (plus of course the fact that now there are probably people in the list again that had unsubscribed!) and I can't recover. Why? Well, I thought that backing up /lists would be sufficient since all relevant data is in those files. Apparently not!? When I copy my old config.pck to the directory, overwriting the current (new) file (permissions set to list:list, 0660), then that file gets stripped in size when I save and/or start qrunner again. And of course the memberlist is still the old, small one, and interestingly enough, the settings (web_page_url e.g.) are lost even though that file should have the settings in it as they were obviously correct before. I do have config.pck.tmp.XXX-files which I tried to rename to config.pck. Again, it gets stripped down and only has a totally outdated number of subscribers. Why would that happen? What else could I do to recover those thousands of lost subscribers? Where _exactly_ are those addresses actually stored? Any why doesn't this seem to be documented somewhere? I really searched pretty much everywhere. Barry in http://mail.python.org/pipermail/mailman-developers/2002-August/012795.html didn't really help me. I really would appreciate any help I can get. My lists are not for fun and we need them. I still don't understand why the backup doesn't help. But maybe I'm simply missing something. Thank you very much, a very desperate Alex -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] spambot and -owner address
I know users mail addresses are hidden in the archive but what about *my* (our) addresses? Many Mailman generated webpages have a mailto: link to the list owner. It would be a real drag for me if a spambot harvested that address because I can't really rename the mail address so I'd just have to put up with the spam. I searched the archives but I didn't see any mention of this issue. What do other people do? TIA. = Please ignore the following ad... __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Messages held in shunt and retry queue
Their is nothing else that postfix has put in the maillog besides just repeats of that. Brian (i sent this to the list but never got the message. Sorry if its a repeat) On Friday 04 June 2004 18:52, Brad Knowles wrote: At 6:38 PM -0400 2004/06/04, Brian York wrote: maillog: Jun 4 16:31:29 listserv postfix/smtpd[27973]: connect from unknown[172.31.101.4] Jun 4 16:31:29 listserv postfix/smtpd[27973]: ACE50337E2: client=unknown[172.31.101.4] Jun 4 16:31:29 listserv postfix/cleanup[27975]: ACE50337E2: message-id=[EMAIL PROTECTED] Jun 4 16:31:29 listserv postfix/nqmgr[27596]: ACE50337E2: from=[EMAIL PROTECTED], size=902, nrcpt=1 (queue active) Jun 4 16:31:29 listserv postfix/local[27977]: ACE50337E2: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (|/var/mailman/mail/mailman post test) Jun 4 16:31:29 listserv postfix/smtpd[27973]: disconnect from unknown[172.31.101.4] This shows the message coming in. Nothing is going to appear in the shunt directory unless it has already been received by Mailman, and is in the process of being handled to be sent back out. Do you have any comparable logs for the outgoing messages on the MTA, or connection attempts for outgoing messages? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] How can I update 2.1.3 -- 2.1.5?
On Tue, 2004-06-01 at 17:31, Brad Knowles wrote: At 6:45 PM +0100 2004/06/01, Ian A B Eiloart wrote: Ah, I see, so I upgrade by reinstalling. But that isn't clear from the documentation, because as easy as doesn't mean is achieved by. So there's me thinking, OK, so its easy, but how do I do it?. Fair enough. We'll have to ask Barry to update the documentation to be more precise. I've clarified that first paragraph in the UPGRADING file, although because of SF CVS unavailability at the moment, I can't check in the change. Here's what it now reads: For the most part, upgrading Mailman entails installing the latest version over the existing version. Usually, you can unpack the new release, run 'configure' with the same options you used in your previous install, and then do a 'make install'. However, there are some changes that may need to be taken care of manually. Does that work for you? 2. The file refers to http://mail.python.org/pipermail/mailman-users/2000-September/006826.html. AFAICT that message is the wrong one. It doesn't relate to upgrading, and isn't from the person referenced, and its four years old. Documentation bug. Barry? I think the note there is a red herring now. Newer versions do a better job of migrating the template files from older versions, so I've simply removed that sections from the file. Cheers, -Barry signature.asc Description: This is a digitally signed message part -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?
Hi, Have you done 'bin/update' after moving the backup config.pck file into the newly installed list directory ? Alex Dupont wrote: Hello, I'm a bit in a loss here: I was running Mailman 2.1.2 on Debian 3.0 with no problems. Using apt-get... to upgrade Mailman to 2.1.4 produced an error. Well, besides the fact that all my archives got deleted (why would a script (!) do that??), I finally got Mailman back up and running version 2.1.4. I had to fix a zillion permissions, and it took me forever. Probably not a Mailman-thing, I know, and the package-maintainer isn't my friend, I can tell you that. But the following should be only Mailman-related: (snip) I think every packager should disclose their configure options so that upgrading can be done through our source distribution and the list dbs automatically updated ! -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Empty module name again
It seems to have done the trick. Thanks from me and the 100+ members of the affected list! Brian On Sat, 5 Jun 2004, Tokio Kikuchi wrote: Hi This patch should work. --- ToDigest.py.origSat Jun 5 18:54:11 2004 +++ ToDigest.py Sat Jun 5 18:55:22 2004 @@ -390,6 +390,6 @@ ustr = h.__unicode__() oneline = UEMPTYSTRING.join(ustr.splitlines()) return oneline.encode(cset, 'replace') -except (LookupError, UnicodeError): +except (LookupError, UnicodeError, ValueError): # possibly charset problem. return with undecoded string in one line. return EMPTYSTRING.join(s.splitlines()) -- Brian Wilson Corvallis, Oregon 541-368-4120 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
