The reason it's so slow is a large number of the connections are most likely
being tied up for long periods by mailservers than don't respond. About 80
of my 120 connections when I sent out mailings would do the same thing.
Apply the big concurrency patch. My concurrency is at 508 now, and I can do
millions of messages per day. During sending, about 100-120 of the
connections are tied up by slow or nonresponding mailservers.
I'd raise my concurrency higher, but I have to make some kernel mods first
(FD_SET problem).
Jay
> -----Original Message-----
> From: Greg Jorgensen [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 27, 2000 3:44 PM
> To: qmail
> Subject: How many outbound messages can you send per hour?
>
>
> We send lots of newsletters and other subscription-type
> emails. Our qmail
> server seems to max out at 10,000 outbound messages per hour.
> I already have
> concurrencyremote set to 120, and reverse DNS lookups and
> other slowdowns
> turned off. The CPU (a dual UltraSparc) is not maxing out; it
> looks like we've
> reached a limit of the SMTP protocol and the number of
> connections allowed.
>
> I can see that separating outbound and incoming mail on
> different servers would
> help; most of the bounces come in while the bulk of the
> subscriptions are going
> out. We are going to add some servers, but I'm wondering if
> 10,000/hour is a
> typical limit, or is there some way I can send more messages
> in an hour?
>
> Thanks!
>
>
> =====
> Greg Jorgensen
> Deschooling Society
> Portland, Oregon, USA
> [EMAIL PROTECTED]
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Messenger - Talk while you surf! It's FREE.
> http://im.yahoo.com/
>
