We’ve added an option to specify an optional second master DNS server for zones in our Secondary DNS service. Unlike the first master, only an IPv4 or IPv6 address is accepted for the second master. This can be useful if you want to specify a redundant master server or dual stack IPv6 and IPv4 connectivity for the same master.
New Outbound Mail Features
As we mentioned earlier, there are several new new features for our Outbound Mail service pending imminent release. We’re pleased to announce the release of the following:
- Mail mirroring support for Outbound accounts
- Mail forwarding (BCC) for Outbound accounts
- IPv6 access filter to compliment the existing IPv4 filter
Due to a last minute bug, the following feature will be delayed until May 22:
- Option to send 5xx response for common DNS errors instead of 4xx
For more information on the bug that was discovered, please read post Bug in “Mail Server” Type Outbound Accounts. The IP and DNS related changes would cause these accounts to reject submissions due to missing parameters, so we decided to delay this feature until those affected could be notified.
We recently announced several major new features for our Outbound Mail service. The new mirroring and BCC options necessitated a major rewrite of the account control center interface in addition to the server-side processing. The rewrite was based on the original implementation as described in the online documentation, but a bug was discovered in the old version that allowed the source filter to be removed for “mail server” outbound types after it was added (entering a source filter was always required during the add process).
Connection source filters are only mandatory on mail server type accounts; filters for the other two types (single address and single domain) are optional.
Upon further research we discovered that there were only 24 mail server outbound accounts that are missing the required source filtering. We have notified these account holders individually of the bug, so if you didn’t get a email directly from us, your account is not affected. This post is in the interest of full disclosure rather than sweeping the problem under the rug.
This requirement will be enforced starting May 22, 2010. After this date, mail server type accounts that are missing a source filter will return the error “An IPv4 address or host filter is required for this submission type.” We apologize for any inconvenience this may cause. Please contact technical support if you require assistance.
Mail Forwarding IPv6 Enabled
As part of our ever expanding quest to fully IPv6 enable our services, the new IPv6 enabled mail forwarding servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.
We’re getting close to tackling the big one: IPv6 enabled incoming mail. Stay tuned!
We are changing the source of forwarded mail as handled by the “Mail Forwarding” option in the account control center. Messages forwarded to external email addresses were previously sent from 208.79.240.32/28. Starting today, we will begin migrating forwarding to a new group of servers out of 208.79.241.112/28. This change is permanent and is being made as part of our recent announcement on enforced content filtering for forwarded mail.
This will also allow us, in the future, to insert forwarding delivery results into the online mail logs. More immediately, these new servers will be also be IPv6 enabled.
[May 8] The IPv6 enabled servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.
