An equal probability is that you're actually generating INDIVIDUAL
messages (one per recipient), rather than messages with a BCC: recipient
list, in which case, my advise would be to switch to BCC: addressing, but
if that isn't an option, look at a cascaded MTA queue (messages which
don't deliver on the first try get sent to a secondary queue which won't
retry right away - and those which fail to deliver from that queue get
moved to one that takes even LONGER) - a fairly typical (read: default
Sendmail setup) queue retry is every 15 minutes, 24/7 --- if you've got a
few hoser domains in there, they can stuff you up quick.
I hadn't considered the BCC option. That would definitely speed the process
up as well. However, we're dealing with potentially 5,000 emails at one
time. That is a lot of addresses to put in the BCC field. Can it hold that?
Also, I'm passing this as a variable to an e-mail function that I have. I'm
not sure what the capacity of a variable is in ASP. It may not be able to
handle a variable that large.
Check your server logs to see if the domains you're emailing to are trying
to perform callbacks (GTE and it's affiliated telco domains are/were doing
this for some time - this is the same bunch of idiots who've blocked many
european IP ranges from sending mail to them, and such sites have to relay
through other hosts in order to deliver to GTE customers). Any domain
that does this might be a candidate for being added to a special case
handler to be shuttled to a low priority queue right off the bat.
Might I suggest you set up a database for the special conditions and the
queues you'd place them in? <g>
Wow, this is getting complicated! All I want to do is send e-mails...
Jesse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
