Settings Page

Settings

The settings page is the second page of the MTA policy wizard. This is where you can configure some basic settings to follow when sending mail to the receiving mailbox domain providers that the MTA policy will be applied to such as Gmail, Yahoo, iCloud, etc.

You'll see the following options on the settings page:

After connection error wait

This is how long to wait to retry a connection after a failure that caused a disconnect, the default of 10 seconds is probably fine.

Hours to retry messages for

If you're using a long-term automated warmup where mail will be sitting in a queue waiting to be delivered indefinitely, you may want to extend this to cover the number of days expected for the warmup period.

Maximum sends per connection

This is how many messages will be sent after a connection is established before disconnecting and starting a new connection. The default of 20 is probably fine.

Simultaneous connections per MX group

Although you send email addressed to a particular domain name, under the hood your mail is actually delivered to the domain's "MX" or Mail Exchange server(s) specified in their DNS configuration and not necessarily the domain that matches the one in the email address.

Let's use the example of the New York Times newspaper domain nytimes.com.

Using the terminal command dig we can request their MX record and see that Nytimes email is being hosted by a third party:

dig nytimes.com mx
;; ANSWER SECTION:
nytimes.com.		300	IN	MX	10 alt3.aspmx.l.google.com.
nytimes.com.		300	IN	MX	5 alt1.aspmx.l.google.com.
nytimes.com.		300	IN	MX	1 aspmx.l.google.com.
nytimes.com.		300	IN	MX	5 alt2.aspmx.l.google.com.
nytimes.com.		300	IN	MX	10 alt4.aspmx.l.google.com.

This is common: many corporate domains, branded domains, or 'vanity domains' use google workspace to host their email in a branded Gmail account.

The Simultaneous connections per MX group sets a default maximum number of connections in the aggregate to the domain in the MX record, as the domain name sent to is irrelevant in a technical sense.

This ensures that if you email 1000 corporate domains that use google workspace as their email host, you don't open 1000 connections to Gmail, as requested by Google in their bulk sender guidelines:

Last updated