I've read the other responses here, but thought an answer to the original
was most appropriate. Comments embedded.
Simpler-Webb, Inc. Austin, TX
"Mauve has more RAM" - Dilbert
(address munged to protect me from spam spewing cretins)
>This is my ISP's response when I asked about doing SMTP, and Queuing:
>This doesn't scale.
>The queue is one directory.
The queue is one directory by default. You can make it as many directories
as you want (with sendmail). If the ISP really gets this many customers
doing this, then putting a little brain power into a creative solution would
be worthwhile. If they only have you, they should shut up - it's a non
Quote:>Guess what happens when 500 domain customers
>(we have well over 1000) do this, and each of them get 100 emails queued.
At that point you redesign the MTA to support the traffic model of your
customers. It's not that difficult and is exactly what folks like AOL have
had to do.
This solution is really designed for the customer who only gets 5-10 emails
every 1-4 hours. There are quite a few people like that. Run the numbers
on randomized dial-in, weighted for business hours, etc. and the load is
Quote:>That's 50,000 files in a directory. The traversal time to search and
>attempt delivery from the queue on each of these will be measured in
Perhaps. But we're talking about one customer who wants to queue 5-10 email
messages. If there are 100+ messages queued in one queue interval (a couple
hours I would guess), then the customer (you) need a dedicated connection.
>What do you think?
I think it's bunk. Technically correct, but practically useless. They
pulled numbers out of ??? and used them to prove their unwillingness to be
creative. The real numbers do not support their position. The capabilities
of the technology do not support their position.