> Thanks for the info. I assume from what you're saying
> that this is normal behavior outside of being a little
> slow. It takes a couple of hours of the wrapper running
> resend before sendmail even throws it in the spool...,
> is this normal wait for a list say of 10,000 members?
AH the truth comes out. This has nothing to do with resend or
majordomo. It has too do with your system configuration in general.
Guesses about your site:
Your not running your own caching DNS server
You try and deliver all your mail directly
Whats happening is that sendmail is looking up EVERY one of those 10k
members and making sure they are valid hosts before entering them into
the queue.
You see when a mail message comes in it works like this.
Mail message -> sendmail running in daemon mode
Deamon -> runs resend
resend -> sendmail
Sendmail -> expands the list into a queue
Queue is run pushing mail out to the users
So you see a resend running but there is a child of the resend which
is a sendmail process.
You should just ship it up stream to someone else to deliver for you,
someone like digex with better connectivity. You should cache the
names on your end (DNS.)
A list with 10K members should periodicly be sorted and or broken down
into smaller lists. Majordomo doesn't do this yet AFAIK.
johno
References:
|
|
