[Mailman-Users] Shunting due to unknown encoding?
The following is an error log entry that *seems* to be associated with Mailman holding up delivery of messages. If I do a bin/unshunt, that seems to end the constipation for a while, although the same entries get into the error log anew. Any idea what can be done about this? It appears to me that it's trying to encode a string as unicode, but the unicode library doesn't recognize "gb2312" as a valid encoding scheme...? And so this particular message is getting shunted, but should that have any effect on other messages? Sep 16 21:09:13 2003 (31119) SHUNTING: 1062284017.614586+9fafb35059e24e6af1604ba d0d81a1c0cae6c64a Sep 16 21:09:13 2003 (31119) Uncaught runner exception: unknown encoding: gb2312 Sep 16 21:09:13 2003 (31119) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/var/mailman/pythonlib/email/Header.py", line 144, in make_header File "/var/mailman/pythonlib/email/Header.py", line 272, in append LookupError: unknown encoding: gb2312 Now that I look a bit further back in the error log, I find this: Sep 16 17:19:54 2003 (31186) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/var/mailman/pythonlib/email/Header.py", line 144, in make_header File "/var/mailman/pythonlib/email/Header.py", line 272, in append UnicodeError: ASCII decoding error: ordinal not in range(128) Error on the same, line, but different error. Shortly thereafter, in the smtp log: Sep 16 17:25:40 2003 (12262) All recipients refused: [Errno 4] Interrupted syste m call Sep 16 17:25:41 2003 (12262) All recipients refused: [Errno 104] Connection rese t by peer Sep 16 17:25:42 2003 (12262) All recipients refused: Server not connected And then the floodgates opened and mail started going to the lists again. I think that at 17:19 I did a bin/mailmanctl restart, then at 17:25, I did the bin/unshunt. Any help appreciated... -- 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Prevent unsubscribe due to content filtering?
I have a couple of subscribers whose employers have installed rather overzealous content filtering on their MTAs. Even though there's nothing particularly salacious on the list in question, these MTAs are rejecting enough messages to cause these subscribers to be disabled and then unsubscribed. I'm trying to figure out the easiest way to persuade Mailman not to count "content" bounces toward unsubscribing. The MTA returns "550 Error: Content Rejected" as the bounce message. In the meantime, I'm experimenting with the bounce settings to slow it down, at least. Any suggestions? I guess there's a feature request there... Nick -- Nick Arnett Phone/fax: (408) 904-7198 [EMAIL PROTECTED] -- 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Group id Catch-22 after list move
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf ... > Postfix should only need to access your mailman auto-generated > aliases. So > we have a userid and group dedicated for mailman (and the http > server), then > just add the userid for postfix to the mailman group on your MTA. Thanks, but that's all done. The problem is that the old lists want one userid and group, any new lists want a different one. I can't figure out why Postfix gets the error in the one case, but not the other. Nick -- 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Group id Catch-22 after list move
I recently moved a couple of lists to a new machine, also upgrading from a 2.1 beta to the final. I copied the entire Mailman directory structure from the old to the new machine, then installed 2.1. I also switched from Sendmail to Postfix. Now I seem to have a Catch-22 with regard to user ids. My old lists are running okay. However, any new list I create has a user id problem with Postfix -- I get the "Mailman expected the mail wrapper script to be executed as group..." error when posting to a new list. If I re-install, using the group name it expects for the new lists, then the new lists work, but the old ones produce that error. I've looked at the source until my eyes cross and I can't figure out how to fix this. Any suggestions? Oh, and one more annoyance. The urls for the admin pages for the internal Mailman list only work if "Mailman" in the url has an upper-case "M", but it is lower-case in all of the pages. Can't figure out how to fix that, either... I tried re-creating the list, but then I get the problem described above. Yeah, I did something bad, apparently. [And just to make my life more interesting, some dang spammer decided to forge "listserv (at) mccmedia.com" as his spam's return address, which is aliased to mailman, so the internal list is getting swamped with bounces that look like postings from non-members.] Nick -- Nick Arnett Phone/fax: (408) 904-7198 [EMAIL PROTECTED] -- 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] inetd doesn't start mailman...?
I'm using RedHat 7.1 and Mailman 2.1b2... and although I appear to have everything configured properly for inetd to start Mailman, it doesn't. Linuxconf also reports that it thinks Mailman isn't running, when it actually is, and manages to stop it when it tries to restart it. I'm afraid I don't know enough about this area to know where to look for the problem. Suggestions? Nick -- Nick Arnett Phone/fax: (408) 904-7198 [EMAIL PROTECTED] -- 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] Digests: "From" address and topics
I'm using Mailman 2.1b2 and digests are going out with a "From" header with
the -request address, rather than the list address. I found a closed bug
for this
(https://sourceforge.net/tracker/?func=detail&atid=100103&aid=231776&group_i
d=103) that says it was to be fixed in Mailman 2... but apparently it hasn't
been. Does this need to be re-opened?
Second problem with digests -- topic restrictions don't seem to affect the
digest. Users who only want to receive one topic in the digest are
receiving everything. My test setup is to select one topic, then set "Do
you want to receive message that do not match any topic filter?" to "No." I
can't find a bug on that one. Does this need to be filed? (A topic of
"Brin:" shouldn't match every message in a list whose name is "Brin-L",
should it ("[Brin-L]" appears in the subject line)? The colon doesn't have
any special meaning in Python's re, does it?
Any suggested fixes for these in the meantime? I'm happy to muck about in
the source, given a pointer or two as to where to go. I've only explored it
a bit so far.
I'm trying to make it easy for a friend to participate in a high-traffic
list without having to read everything, and only receive one digest a day,
but it really isn't working well -- very frustrating. (The friend is David
Brin, the writer and futurist, who doesn't have a lot of time to muddle
through this mess.)
--
Nick Arnett
Phone/fax: (408) 904-7198
[EMAIL PROTECTED]
--
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] email.iterators missing after upgrading Mailman & Python...?
Uninstalling Python and reinstalling with the RPMs from python.org appears to have solved this problem. Nick > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Nick Arnett > Sent: Monday, July 29, 2002 7:01 PM > To: [EMAIL PROTECTED] > Subject: [Mailman-Users] email.iterators missing after upgrading Mailman > & Python...? > > > I'm trying to upgrade from 2.01 to 2.2b1 and RH 7.2... and all > seemed to go > well, except that it's not finding email.iterators. I don't even see the > email module in the Python installation, which mystifies me. > I've installed > Python 2.2 (#1, April 12). It looks to me as though the email > module should > have been installed with it. And I can't find the module anywhere for > download... > > This must be something trivially obvious, but I sure can't see it. > > Thanks in advance for help. > > -- > [EMAIL PROTECTED] > (408) 904-7198 > > > -- > 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 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] email.iterators missing after upgrading Mailman & Python...?
I'm trying to upgrade from 2.01 to 2.2b1 and RH 7.2... and all seemed to go well, except that it's not finding email.iterators. I don't even see the email module in the Python installation, which mystifies me. I've installed Python 2.2 (#1, April 12). It looks to me as though the email module should have been installed with it. And I can't find the module anywhere for download... This must be something trivially obvious, but I sure can't see it. Thanks in advance for help. -- [EMAIL PROTECTED] (408) 904-7198 -- 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] Feedback?
Thanks for the suggestion, that that's not really what I'm after. I'm talking about adding that sort of functionality to the e-mail messages themselves, with links back to the server. I'm quite familiar with Slashdot, Zope, etc. Nick > -Original Message- > From: Dennis W Heltzel [mailto:[EMAIL PROTECTED]]On Behalf Of > Dennis W Heltzel > Sent: Wednesday, July 17, 2002 6:42 AM > To: Nick Arnett > Cc: [EMAIL PROTECTED] > Subject: Re: [Mailman-Users] Feedback? > > > This sounds a lot like what a weblog server does. A great example of this > in action is http://www.slashdot.org. If you have access to a server that > can run Zope, you should try a Zope product called "Squishdot". I believe > it does user feedback really well, though my experience with it is > limited. -- 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
[Mailman-Users] Feedback?
Does anyone here know of any message feedback mechanism that can be added to Mailman? I'm looking to add a web-based rating mechanism. Initially, the idea is to let people give others negative feedback points, but the price of doing so is that you received a percentage of a point yourself, thus creating a disincentive for downgrading a lot of other people. I'm not interested in debating the ethics or efficacy of such a mechanism right now, but I'd be more than happy to hear suggestions about how to make it work properly. I expect it to be relatively simple -- addition of a code identifying the sender and recipient, which feed back via a CGI to Apache and then MySQL. I'm a bit concerned about the implicit slowdown in delivery, but I'm not looking at a high-volume list yet. That's the one-click approach. Otherwise, I could munge something into the archives, but that'll require login to identify who's voting. Any and all suggestions will be welcome. Pointers on the best place(s) to touch the code will be gratefully accepted. Nick -- [EMAIL PROTECTED] (408) 904-7198 -- 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
