RE: Large Mailshot (not spam) causing problems wit h regard to everyday urgent business e-mails

  • From: John Mason <John.Mason.Jr@xxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 15 Jan 2004 15:33:20 -0500


> -----Original Message-----
> From: Mulnick, Al [mailto:Al.Mulnick@xxxxxxxxxx] 
> Sent: Thursday, January 15, 2004 3:22 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Large Mailshot (not spam) causing 
> problems wit h regard to everyday urgent business e-mails
> 
> 
> http://www.MSExchange.org/
> 
> I have a little trouble following the technical terminology.  
> Could be that I'm just on the wrong side of the pond however :)  
> 
> What does 'duff addresse's ' mean?  Is this an invalid 
> recipient?  If so, why is it trying again?  Maybe I'm 
> misunderstanding what's going on?
> 
> If you're going to send a large amount of mail like that, 
> might I suggest an alternate delivery server for such email?  
> A Windows 2000 server is a fine server to do the job as is 
> Windows 2003.  It's just sending that you're concerned with 
> and nothing fancy based on your description.  What you will 
> still have to contend with is the NDR's.  Those will go back 
> to the domain they were sent from.  In your case, possible 
> stopping the queues.  I would suggest a timed delivery in 
> that case so you can at least have all of the NDR's come in 
> over night.  
> 
> The same timing might alleviate the need for a separate 
> server altogether, but either way has worked in the past 
> where I've seen it.  I prefer the alternate server though.  
> You never know how long it will take to send the messages and 
> it wouldn't affect production until the NDR's started coming back. 
> 
> 100,000 messages aren't that many necessarily, so probably 
> one server or laptop would likely do it.
> 
> Al
> 

I would add not only move the mailing lists to another machine, but also
look at using software designed to manage a mailing list.


John


Other related posts: