Hi All, 

I need to email around 40 K users across different geographical locations in Exchange. 
I have PowerShell script to send users. 

But I know what will impact on Exchange's server performance. 

Q) What is the maximum number of email in Exchange server 2010/2013. 

Q) How can I send emails to users without affecting server performance.  

Hi,

By default, you have no limit  https://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx.

But, however, you risk being considered a spammer. you must change dynamicaly the subject in your screen and you must split your distribution list.

I recommend usin a marketing tool, Dynamics CRM Marketing, ClickDimension, Sarbacane to make your marketing campaign.

Yannick.

Hi Sandy,

Below is the answer

Q) What is the maximum number of email in Exchange server 2010/2013. 

Personally I always recommend using a different relay system for email blast  to protect my production IP addresses and also to keep the load off of exchange so that it can process its production important emails.

If you do decide to do it yourself, make sure that you are using a different domain and a different IP address as you WILL get blacklisted in a day very easily.


create a separate receive connector just for this source ip and up the limit (number of connections per source) for this connector and configure relay permissions for this app accordingly.


Q) How can I send emails to users without affecting server performance.  


Your hardware plays an important part in terms of performance. Too small a disk? Too few CPUs? Not enough memory?

The size of the messages, the number of AV signature that scan the messages, the complexity of the message structure, etc. all play an important role in how much that processing taxes the machine.

However if you are strong enough and confident on your hardware and memory then i would recommend to send these mass mailing on off production hours.

Hi Sandy,

Below is the answer

Q) What is the maximum number of email in Exchange server 2010/2013. 

Personally I always recommend using a different relay system for email blast  to protect my production IP addresses and also to keep the load off of exchange so that it can process its production important emails.

If you do decide to do it yourself, make sure that you are using a different domain and a different IP address as you WILL get blacklisted in a day very easily.


create a separate receive connector just for this source ip and up the limit (number of connections per source) for this connector and configure relay permissions for this app accordingly.


Q) How can I send emails to users without affecting server performance.  


Your hardware plays an important part in terms of performance. Too small a disk? Too few CPUs? Not enough memory?

The size of the messages, the number of AV signature that scan the messages, the complexity of the message structure, etc. all play an important role in how much that processing taxes the machine.

However if you are strong enough and confident on your hardware and memory then i would recommend to send these mass mailing on off production hours.

The 40K users - are they inside your Exchange organization, or are they external (eg client companies on the Internet) ?

As for the maximum number of emails, for Exchange 2010 there was a maximum number of 500k messages, as stated here, yet your number is far smaller - so not an issue. Never seen any cap limit referenced for Exchange 2013, so it might just be up to your hardware/network/etc just as Sathish said.

One way of lessening the burden against your infrastructure is to stagger the delivery - eg. send 20K mails in one day, and 20K the next. Or if possible, expand the interval even more.

The 40K users - are they inside your Exchange organization, or are they external (eg client companies on the Internet) ?

As for the maximum number of emails, for Exchange 2010 there was a maximum number of 500k messages, as stated here, yet your number is far smaller - so not an issue. Never seen any cap limit referenced for Exchange 2013, so it might just be up to your hardware/network/etc just as Sathish said.

One way of lessening the burden against your infrastructure is to stagger the delivery - eg. send 20K mails in one day, and 20K the next. Or if possible, expand the interval even more.