Share via


Exchange: Sending Mass Mailers, Marketing Emails, Newsletters


At times we might get a requirement where we want to send emails in bulk from our messaging system to internal/external users for a business case.

Though sending bulk emails is not at all advised due to many factors, when business demands we do not have any other option other than going further.

The business may demand we configure our mailing system to send advertisements, newsletters to the partners, customers in a week, in a day or even every 2 hours.

We would need to configure this requirement in a way that it should not affect the below parameters:

  1. a) Without affecting our normal email operations and without affecting our messaging system performance.
  2. b) Without getting blacklisted as a spammer.
  3. c) The mass email that we send should land in the end users inbox, not in the spam folder, and shouldn’t be trapped in their filters.

Based on industry best practices, here are a few points which can be taken into consideration when we plan for these type of requirements:

  1. Determine how the mass emails are going to be sent from which application (whether its internal IP or external IP). Then the mass mailer recipients (whether it goes only to internal recipients or both internal and external recipients). If it's for internal recipients only then the job wouldn’t be more complex.
  2. If it's going to be from an external IP then better to not allow a relay of these bulk emails through your domain.
  3. It's not advised to allow sending bulk emails from an unregistered external IP to external users from your domain since your IP and domain will get blacklisted in a matter of days.
  4. If still there is a requirement to send mass mailers from external IPs make sure the below are met
    1. Send the mail using a known and registered sender address (domain) of which the domain part is traceable using reverse lookup, and has a valid SPF.
    2. Make sure they send all the emails with the correct subject, message bodies, unsubscribe link and adhere to all the local and legal requirements.
    3. Try convincing the marketing team or the team who sends bulk email to use a different domain and a different IP address as your connecting IP will  get blacklisted easily and will affect your production emails.
  5. There are a few SMTP appliances that can be placed in the DMZ which can accept emails from the mass mailing apps and can do the job.

There is a number of cheap bulk emailing tools that will do this job easier, including dealing with bounces, unsubscribe requests, etc. It's even better to outsource this requirement to any one of them.

Since the major outsourced providers have been doing this business for a while in the market they will have all the configurations and settings in place with ISP’s which will increase the delivery success rate of these emails.

If you still would like to go for the mass mailing via external IP domains to external users through Exchange then make sure the below conditions are met:

  1. Create a dedicated server (CAS+MBX) for doing this job. Configure a relay on this server.
  2. Create a new database. Create the sender mailbox alone on this new database.
  3. Create an additional number of transport servers for load balancing since SubmissionServerOverrideList switch cannot be used from Exchange 2013. If you add Exchange 2010 hub server for this then you can use SubmissionServerOverrideList for that DB to use only that HUB server which will not affect the other transport servers.

Also, make sure the below values are set in the send connectors:

Maximum concurrent outbound connections: 1000 *

Maximum concurrent outbound connections per domain: 20*

Set-SendConnector -SmtpMaxMessagesPerConnection 200

Also, make sure that you alter and configure these values on the relay receive connectors according to the number of bulk emails:

  • ConnectionInactivityTimeout
  • ConnectionTimeout
  • MaxInboundConnection
  • MaxInboundConnectionPercentagePerSource
  • MaxInboundConnectionPerSource
  • MaxRecipientsPerMessage
  • MessageRateLimit

Finally, make sure these bulk emails are sent only during off business hours in order to avoid load on the transport services during production hours.

Hope this helps!