1) I've just faced a huge problem: the listname-bounces address has become
crazy, sending bounced messages to the list-admins, and issuing "You have
been removed from list" messges to bouncers, then again, then again, in a
loop that sent 4000 messages before I interrupted it by sending all -bounce
The first option under General is:
The public name of this list (make case-changes only).
If this were done right - changing this field would cause the list to be
renamed.
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/
these are unconditional right now, and should be a GUI-selectable
item. If I can find the time I'll try to hack up a patch.
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Dan Mick <[EMAIL PROTECTED]> writes:
> It might be that inverting the problem might be the right answer:
> Mailman 2.1 goes through an API for all "member"-type queries, and
> so perhaps storing the member info external to config.db via a new
> "member-adaptor" interface, so that TMDA could also
[EMAIL PROTECTED] (Barry A. Warsaw) writes:
> The intent though is that once I go to beta (next release), those
> attributes and their semantics will be frozen through the MM2.1
> release.
Right now TMDA assumes attributes containing e-mail addresses will
either be lists, or dictionaries in whic
> Dan Mick <[EMAIL PROTECTED]> writes:
>
> > It might be that inverting the problem might be the right answer:
> > Mailman 2.1 goes through an API for all "member"-type queries, and
> > so perhaps storing the member info external to config.db via a new
> > "member-adaptor" interface, so that TMD
> "JRM" == Jason R Mastaler
> <[EMAIL PROTECTED]> writes:
JRM> Right now TMDA assumes attributes containing e-mail addresses
JRM> will either be lists, or dictionaries in which the addresses
JRM> are the keys. This seems to hold true for both MM 2.0 and
JRM> 2.1a.
Yup,
> "MP" == Marc Perkel <[EMAIL PROTECTED]> writes:
MP> The first option under General is:
MP> The public name of this list (make case-changes only).
MP> If this were done right - changing this field would cause the
MP> list to be renamed.
Too much work for MM2.1, but it's o
[Fil describes problems with the mailmanctl -s flag...]
This is fixed now in CVS I believe. There was a subtle (is there any
other kind? :) race condition and a reference counting issue in the
handoff of the lock from the parent to the child. Pesky bugger to
track down, but I think I've got it
> "JRM" == Jason R Mastaler
> <[EMAIL PROTECTED]> writes:
JRM> I think Message.UserNotification.send() should also add a
JRM> 'Date' header just as it adds 'Message-ID' (which I'm glad to
JRM> see it now does!).
JRM> Accordingly, I've submitted a patch (#500670) to the
Dan Mick <[EMAIL PROTECTED]> writes:
> "ease" wasn't the point; the point is that "reaching into config.db"
> is unsupported, whereas "plugin membership module" *is* intended to
> be supported, and therefore stable interface. Then, since you've
> got your choice of storage formats, the world's y
I'm doing my first big mailing with Mailman/Exim to deliver effector for the
Electronic Frontier Foundation. The list is about 20,000 names.
Anyhow - started out moving right along, maybe too well - saturated the T1
pretty quick and the system slowed down. But the email logs were really going
fas
> Dan Mick <[EMAIL PROTECTED]> writes:
>
> > "ease" wasn't the point; the point is that "reaching into config.db"
> > is unsupported, whereas "plugin membership module" *is* intended to
> > be supported, and therefore stable interface. Then, since you've
> > got your choice of storage formats,
> "JRM" == Jason R Mastaler
> <[EMAIL PROTECTED]> writes:
JRM> I'd imagine my wanting access to the `member' addresses from
JRM> another application isn't all that uncommon. Mine just
JRM> happens to be written in Python which made this easy. It
JRM> might be nice to op
What version?
> I'm doing my first big mailing with Mailman/Exim to deliver effector for the
> Electronic Frontier Foundation. The list is about 20,000 names.
>
> Anyhow - started out moving right along, maybe too well - saturated the T1
> pretty quick and the system slowed down. But the email l
> "MP" == Marc Perkel <[EMAIL PROTECTED]> writes:
MP> I'm doing my first big mailing with Mailman/Exim to deliver
MP> effector for the Electronic Frontier Foundation. The list is
MP> about 20,000 names.
A good cause, for sure.
MP> During this time I saw a number of errors.
I think I have a problem. The html interface into mailman is working - the
email quit. I have a frowing number of python processes stacking up. I had
just started sending to a list of 20,000 for the first time.
I think something is locked up dealing with mail delivery and subscribing with
mailman
Version 2.08
Dan Mick wrote:
> What version?
>
> > I'm doing my first big mailing with Mailman/Exim to deliver effector for the
> > Electronic Frontier Foundation. The list is about 20,000 names.
> >
> > Anyhow - started out moving right along, maybe too well - saturated the T1
> > pretty quick
On 1/10/02 10:08 PM, "Marc Perkel" <[EMAIL PROTECTED]> wrote:
> Anyhow - started out moving right along, maybe too well - saturated the T1
> pretty quick and the system slowed down.
That's not good. IT's not a mailman problem, but it's not good. You need to
tune your MTA to slow it down down so
I'm running Redhat 7.2 I'm running the 2.4.17 kernel. Python is 1.5.2. Mailman
2.0.8 and exim 3.34.
Actually the problem is lack of logs. Mailman appears to be frozen with python
tasks backing up as if the mailman tasks are locking up. I'm sure it's also
processing a lot of bounced email.
Could
A few years ago we ran a Mailman logo contest, had quite a few very
good submissions, and eventually chose a logo by The Dragon De
Monsyne. Now with the advent of favicons I'd like to run another
mini-contest. I admit shameful jealousy in seeing more and more cool
favicons in my Mozilla tabs, a
Dan Mick <[EMAIL PROTECTED]> writes:
> I think you still must misunderstand;
Yup. I'm not very hip to the MM jargon yet.
> what I'm suggesting is that TMDF
TMDA == ``Tagged Message Delivery Agent''
> implement and supply a Mailman membership-management plugin for just
> this purpose.
You've
> > what I'm suggesting is that TMDF
>
> TMDA == ``Tagged Message Delivery Agent''
sorry.
> > implement and supply a Mailman membership-management plugin for just
> > this purpose.
>
> You've lost me. What is a Mailman membership-management plugin?
The thing we've been talking about. The t
> "MP" == Marc Perkel <[EMAIL PROTECTED]> writes:
MP> Actually the problem is lack of logs.
Is there nothing useful in errors/log? If not, it definitely ain't a
Mailman problem.
MP> Mailman appears to be frozen with python tasks backing up as
MP> if the mailman tasks are l
> "DM" == Dan Mick <[EMAIL PROTECTED]> writes:
DM> The thing we've been talking about. The thing virtclassed in
DM> MemberAdaptor.py and derived/instantiated in
DM> OldStyleMemberships.py. The thing that implements the
DM> membership-management API.
Except that I think TDM
Dan Mick <[EMAIL PROTECTED]> writes:
> The thing virtclassed in MemberAdaptor.py and derived/instantiated
> in OldStyleMemberships.py. The thing that implements the
> membership-management API.
Jargon. :-)
OK, I'll see what I can figure out.
--
(TMDA (http://tmda.sourceforge.net/))
(user-lev
I rebooted the system. Still have problems.
> Well, you can double check and see if there are any stale lock files
> in the locks directory. If you're exhausting your system resources as
> Chuq points out, and your Python processes are either hanging,
> thrashing with other processes, or just ge
On 1/10/02 10:30 PM, "Marc Perkel" <[EMAIL PROTECTED]> wrote:
> Python is 1.5.2.
That version's known to have some glitches.
> Actually the problem is lack of logs. Mailman appears to be frozen with python
> tasks backing up as if the mailman tasks are locking up. I'm sure it's also
> processin
> > "DM" == Dan Mick <[EMAIL PROTECTED]> writes:
>
> DM> The thing we've been talking about. The thing virtclassed in
> DM> MemberAdaptor.py and derived/instantiated in
> DM> OldStyleMemberships.py. The thing that implements the
> DM> membership-management API.
>
> Except
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
>> Python is 1.5.2.
CVR> That version's known to have some glitches.
Good point. Python 2.1.1 should be better. (And Python 2.1.2 release
candidate just went out tonight, but I don't think Mailman users need
freak out about
On 1/10/02 10:49 PM, "Marc Perkel" <[EMAIL PROTECTED]> wrote:
> Yea - 28 files in the locks directory. Do I delete the locks?
>
> Thanks for your help. I'll fix it in the morning.
Yes. Make sure there are no python processes in the queue, though, so you
don't step on something by accident.
_
On Thu, 10 Jan 2002 22:08:19 -0800
Marc Perkel <[EMAIL PROTECTED]> wrote:
> I'm doing my first big mailing with Mailman/Exim to deliver
> effector for the Electronic Frontier Foundation. The list is about
> 20,000 names.
I'm going to do some guessing here, so make allowances.
> Anyhow - starte
On Fri, 11 Jan 2002 01:21:36 -0500
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
> Two things are critical before we can move forward: we need to
> know what versions of the various bits of software you're running
> (and that includes OS, Python, Mailman, and Exim), and we need to
> see those traceb
> "SP" == Simone Piunno <[EMAIL PROTECTED]> writes:
SP> I've just upgraded from 2.1a3(CVS) to 2.1a4(CVS) and the same
SP> problem occurred (even re-issuing make install) I had to
SP> remove Cookie.py by hand.
I was able to reproduce the problem when upgrading from 2.1a2 to
curre
@ Barry A. Warsaw <[EMAIL PROTECTED]> :
> [Fil describes problems with the mailmanctl -s flag...]
> This is fixed now in CVS I believe.
It works.
-- Fil
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mai
35 matches
Mail list logo
