Howdy,
I'm running Mailman 2.1.5 and upgraded to Python 2.4 yesterday. Since
then I've gotten 9 tracebacks in the error log as below, with ~130
bounces processed during that time. I've never seen this error before
with Mailman that I can remember.
Dec 03 07:48:21 2004 qrunner(47971): Traceback
On Wed, 24 Nov 2004 08:16:05 +1100, Terry Allen [EMAIL PROTECTED] wrote:
Is it possible to delete a list using the HTML pages in
Mailman? If not, am I correct in that deleting a list requires
running the rmlist command from the command line like this:
Good question. I see there's a
I'm using Mailman 2.1.5.
I ran into a situation today where a list owner changed the
bounce_score_threshold from 7 to 3, and 55 subscribers were disabled
when cron/disabled ran. Most of these users haven't seen a bounce in
at least weeks, in some cases years, but they all did have bounce
scores
On Thu, 15 Jul 2004 09:48:02 -0400, Alan McKay [EMAIL PROTECTED] wrote:
Update : further investigation shows it is not every user, but most users.
And if I go into the admin interface and unsub the user then immediately
resub them with the same address, it appears (at least at this point)
to
On Thu, 15 Jul 2004 19:30:54 +0200, Brad Knowles [EMAIL PROTECTED] wrote:
There are a variety of log processing programs, depending on your
MTA, etc If you use postfix, check out pflogsumm (see
http://jimsun.linxnet.com/postfix_contrib.html).
Or the extended version, pflogstats.
On Saturday, January 18, 2003, at 08:45 PM, Mary Ann Horton wrote:
Are there any known cookie issues (the FAQ is silent on the subject)
or suggested fixes or workarounds?
Yes. Mailman 2.0 cookies contain a :, which breaks Mailman 2.1 web auth
(because it breaks Python's cookie handling).
On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote:
One of my goals for the digester was that either digest could be burst
and the individual messages would look exactly as if they had arrived
independently. Or at least, they'd be useable to do follow ups back
to the list.
On Saturday, January 18, 2003, at 10:47 PM, Bryan Fullerton wrote:
On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote:
One of my goals for the digester was that either digest could be burst
and the individual messages would look exactly as if they had arrived
independently
On Wednesday, January 16, 2002, at 02:11 PM, Ricardo Hempel wrote:
Hello friends, I'm a beginner using mailman, my english is not very
good and I'm new in this list. I have a question, ... I It seems that
I erase one part of the code of the html page of General List
Information Page , where
Howdy,
Anyone know why the format of the digest subject line changed?
In 2.0.x it was, for example:
Trawler-world-list digest, Vol 5 #570 - 21 msgs
In 2.1, it changed to:
Trawler-world-list Digest, Vol 5, Issue 571
So... why the change?
Thanks,
Bryan
Several of my list owners are quite unhappy with the state of plain
text digests in 2.1. Here's one comment sent to me this morning:
=
I must admit that until this post appeared I had not noticed that the
messages were still numbered. Since the index is numbered, the number
is really usefull
This just came thru on my mm2.1 setup - anyone seen anything like it?
Looks like there's a corrupt pending request somewhere, but I'm unsure
how to fix.
Thanks,
Bryan
Begin forwarded message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date: Tue Jan 14, 2003 8:00:01 AM Canada/Eastern
To: [EMAIL
Ah, I suspect this might be a result of the 2.0/2.1 cookie problems.
Haven't seen this recently, and subsequent attempts to add addresses to
sender filters have worked as expected.
Thanks,
Bryan
On Friday, January 10, 2003, at 11:57 AM, Bryan Fullerton wrote:
Howdy,
When I approve
On Tuesday, January 14, 2003, at 04:44 PM, Jeff A. Earickson wrote:
I upgraded from 2.0.13 to 2.1 and I have two nasty problems:
* non-subscribers can post to lists
* subscribers can reply to a moderated-only list and have
their email go to the list
The latter has caused an email storm
On Monday, January 13, 2003, at 05:32 PM, Kory Wheatley wrote:
I received the below error when I tried to create a mailing list from
the Mailman web interface page. It did add the list into the alias
file,
but it
failed to run postalias probably because of permission issue's I'm
guessing.
I
Howdy,
When I approve a message and also select Add [email] to a sender
filter, is it supposed to add them to the non-member filter lists
under the admin/[list]/privacy/sender web interface? I just approved a
message and selected that option, but they're not listed in the sender
filters.
On Tuesday, January 7, 2003, at 08:37 PM, Paul Allen Rice wrote:
I've noticed that when I log out of the admin page for one list, go to
another and login there, then come back to the first list, all without
shutting down my browser, Mailman allows me back into the first list
admin
area without
On Tuesday, January 7, 2003, at 11:40 PM, Barry A. Warsaw wrote:
Great sleuthing, Bryan!
Thanks!
I don't have time tonight to work out a fix, but this is an excellent
clue, and I'm hopeful there's a workaround.
I'll submit a bug. :)
Bryan
On Monday, January 6, 2003, at 07:05 PM, Barry A. Warsaw wrote:
I've only ever seen this with lists on python.org that we upgraded
from MM2.0 according to the instructions in the UPGRADING file (see
UPGRADING INDIVIDUAL LISTS). I've never seen this for brand new MM2.1
lists. I've suspect it's
On Tuesday, January 7, 2003, at 12:15 AM, Barry A. Warsaw wrote:
BTW, for the hacker inclined, an possibly useful way to debug this is
to edit SecurityManager.py, the __checkone() method. Stick something
like this before the first try: line (untested):
syslog('debug', 'key: %s, c[key]:
On Tuesday, January 7, 2003, at 07:12 AM, Stephan Berndts wrote:
I realized the problem that trawler-world-list-help matches not only
the rewriterule for trawler-world-list-help but also that for
trawler-world-list. (Is there one in your case? I cannot remember.)
Nope, here there's only a
On Monday, January 6, 2003, at 07:42 PM, Barry A. Warsaw wrote:
Very interesting. I wonder if this could be some Apache bug or other?
We're running 1.3.27 on python.org so I don't have direct experience
with this bug on Apache 2.0
Sorry, any references to 2.0 are Mailman - I'm using Apache
I've run into something since I installed mm2.1 and wanted to see if
anyone else is seeing it before I report it as a bug.
From time to time (ah, the best kind of bug), the cookie set when
logging into a list seems to go bad - after authenticating, any other
admin operation (admin pages,
On Monday, January 6, 2003, at 02:29 PM, Bryan Fullerton wrote:
From time to time (ah, the best kind of bug), the cookie set when
logging into a list seems to go bad - after authenticating, any
other admin operation (admin pages, admindb, list archives) results in
prompting again
On Monday, January 6, 2003, at 04:01 PM, Dan Phillips wrote:
I had the same problem initially. I manually deleted all the old
cookies set by mailman and it worked fine. Deleting just the cookie
from that list didn't help.
Unfortunately, in this case both of the lists are active, so they're
Howdy,
I notice that in mm2.1 the a message has been held notices to list
owners/moderators now include the content of the message. When spam is
held, this can result as the notice itself being tagged as spam, which
causes them to be thrown in my spam folder. Is there an option to use
the
On Thursday, January 2, 2003, at 11:24 PM, Barry A. Warsaw wrote:
This is normal, and no, you don't need to worry about the lost data
files. In fact, once you get comfortable that the only bad messages
are spam, you can set QRUNNER_SAVE_BAD_MESSAGES=0 in your mm_cfg.py to
just discard them.
On Friday, January 3, 2003, at 11:11 AM, Guillaume Duteil wrote:
I am using 2.1b5 and I needed to set
OWNERS_CAN_ENABLE_PERSONALIZATION to 1 in /Mailman/Default.py
Humm, this is the right setting, but you know you should not be
changing Mailman/Defaults.py, right?
From Defaults.py:
# NEVER
I guess now that mm2.1 has been released, general questions should go
here? If not, let me know and I'll send to -dev.
Just installed mm2.1 and moved over some lists yesterday. Today I found
the following in logs/error:
Jan 02 18:58:19 2003 (35619) message is unparsable:
29 matches
Mail list logo
