See my previous thread in the February Archive about a 140,000 member list:
http://mail.python.org/pipermail/mailman-users/2003-February/026400.html
especially this message:
http://mail.python.org/pipermail/mailman-users/2003-February/026429.html
while that was with 2.1 the same concepts apply
The Mailman queue runners load your entire list into memory for all operations.
So yes, that is normal for Mailman.
I originally attempted to manage an announce only list with over 150,000 members on a
1.5GB Redhat but had to give up because these tasks grew to over 130MB each.
I am currently runn
I would interested in having people search their mail logs for the bounce message
shown in my first message and finding out whether anyone else is seeing this message.
While I don't know if this makes any difference I have a 2.1.3 system just upgraded
this week.
-
Someone emailed me to point out that this form of Sender: and Errors to: address is
only used if you have personalization turned on.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ
I meant to say that the issue is with the mailman form of
Sender:
and
Errors-to:
Not
Reply-to
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw
Serious issue for those with aol subscribers.
I'm currently whitelisted with aol and usually have no problem with mail delivery.
Currently running 2.1.3
This morning I noticed aol bouncing just about all of the emails from my mailman
server with one or the other of the following
bounce messages:
I am currently running a mailman 2.x announce only list
Due to the size of my mailing list I needed to split my original list into smaller
sublists for performance reasons.
In this setup:
(1)Users subscribe to one initial list and need to confirm
(2)A cron script executes periodically and move
