Re: [Mailman-Users] how limit traffic
On Mon, Jan 19, 2004 at 04:52:09PM +, Navegante wrote: I need to use a newsletter with 2400 email adresses (op-in list)but my hosting plan doesn?t allow me to send more than 200 mails in one shot (recent spaming issues and server black lists from other users). Is there a way to force Mailman spit the list in 200 mails (12 lists!) or does shots of 200 adresses per time limit? Can i use some sort of cron jobs? Look at the following segment in Defaults.py: # Ceiling on the number of recipients that can be specified in a single # SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. Only used with the SMTPDirect DELIVERY_MODULE. SMTP_MAX_RCPTS = 500 Incidentally, please restrict your replies to only the relevant pieces of the e-mail and do not reply to a digest changing only the subject line. For a new question, please start a new thread so you don't mess up the threading model for those of us with real mail clients. Thanks! -- Ed Wilts, Mounds View, MN, USA mailto:[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] how limit traffic
At 4:52 PM + 2004/01/19, Navegante wrote: Is there a way to force Mailman spit the list in 200 mails (12 lists!) or does shots of 200 adresses per time limit? Mailman will aggregate together as many recipients as it can per message envelope, if you make sure that the VERP and per-user features are turned off. This will make it a bit more difficult to manage the mailing list (especially bounces from misconfigured mail servers). See also http://www.python.org/cgi-bin/faqw-mm.py?req=all#4.11, http://www.python.org/cgi-bin/faqw-mm.py?req=all#6.6, and http://www.python.org/cgi-bin/faqw-mm.py?req=all#2.2. In particular, make sure that SMTP_MAX_RCPTS in ~mailman/Mailman/mm_cfg.py (see ~mailman/Mailman/Defaults.py for details) is set to a sufficiently high level to meet your needs. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) -- 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] how limit traffic
At 12:02 PM -0600 2004/01/20, Ed Wilts wrote: Look at the following segment in Defaults.py: # Ceiling on the number of recipients that can be specified in a single # SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. Only used with the SMTPDirect DELIVERY_MODULE. SMTP_MAX_RCPTS = 500 Which won't work with the majority of MTAs. Most limit the maximum number of recipients per message to be something like 100 or 200. If the local MTA has been modified to have a higher limit than normal, it should deal with the issue of envelope splitting if the remote MTA has a smaller limit. The flip side of having so many recipients per message is that many mail systems will flag your messages as being spam, especially larger sites like AOL. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) -- 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] how limit traffic
= Original Message From Brad Knowles [EMAIL PROTECTED] = At 12:02 PM -0600 2004/01/20, Ed Wilts wrote: SMTP_MAX_RCPTS = 500 Which won't work with the majority of MTAs. Most limit the maximum number of recipients per message to be something like 100 or 200. If the local MTA has been modified to have a higher limit than normal, it should deal with the issue of envelope splitting if the remote MTA has a smaller limit. I had what I consider, if not an interesting experience, at least a learning one recently concerning Mailman's smtp_max_rcpts. Mailman 2.0.9 (I know - I'm building another server for the latest/greatest) AIX 5.1 / RS6000 (ditto) The symptoms were happening on a list with over 6,000 subscribers, followed by the same problem on a list with over 880 addresses. The message's qfiles .db file was over 50,000 bytes. Each time qrunner fired up (remember, this is still the cronned qrunner), locks would be made, and the queue held up until qrunner timed out. Either that, or qrunner was terminated because Postfix would fail with a queue file write error. Every hour and a half, the message would get 'reinjected' in the qfiles directory. I would delete the db and msg files, get the large queue mostly emptied out, but then the message would get reinjected, causing the backlog again. My temporary 'cure' was to leave the corrupt .db file in the qfiles directory. That seemed to stop that message from returning. I left the bad db file there for about a week, until the next large message/large recipient list. It started to dawn on me what the problem was, when I tried to vi the corrupt .db file, and vi gave me 'a line cannot be longer than 2048 characters.' At this point, mm_cfg.py contained the option, SMTP_MAX_RCPTS = 300. If an average email address is 20 characters, and Mailman chunkifies a large group of addresses, in this case 300, that's 6000 characters. Postfix has a hard limit of 2048 characters for a line. Even dropping SMTP_MAX_RCPTS to 100 would be a borderline 2000 characters, not taking into account some addresses that are over 30 characters long. The short of it is, I dropped SMTP_MAX_RCPTS to 50 so Mailman chunkifies smaller, and the large lists no longer have a problem with corrupt .db files. As well, (without earlier stats to compare to) large messages to large recipient lists seem to zip through the queue faster. Example 1: Jan 14 15:59:03 2004 (17224) smtp for 6914 recips, completed in 1201.166 seconds (345 addresses/minute, primetime, large message, primarily 'outside' addresses) Jan 14 16:00:07 2004 (17228) post to [a list] from [a addy], size=38412, success Example 2: Jan 16 03:03:27 2004 (13054) smtp for 6915 recips, completed in 144.519 seconds (2882 addresses/minute, off prime, small message, primarily 'outside' addresses) Jan 16 03:03:27 2004 (13054) post to [a list] from [a addy], size=640, success Example 3: Jan 20 12:59:48 2004 (14466) smtp for 6915 recips, completed in 1125.579 seconds (368 addresses/minute, primetime, large message, primarily 'outside' addresses) Jan 20 12:59:48 2004 (14466) post to [a list] from [a addy], size=38481, success At least, that's my theory and I'm sticking to it. -- 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