I provide support via email (only) on a best-effort basis.
If you think that there is a configuration problem or operational issue with one of the domainMX.net servers, need help updating your DNS information, or have other technical questions related to the service, please send an email to "support".
If your problem is urgent, please use the "trouble" email address. Examples of urgent problems include:
Known Issues and Planned Outages
April 26, 2010 -- MX host name changes
An email was sent today to all active domainMX.net customers informing them of this change. The new MX hostnames were included in that email. If you are an active customer and did not receive this email, please contact support immediately.
July 17, 2009 -- Bounce and Bad User Filtering Implemented
As a result, starting today the domainMX.net servers are recording recipient addresses that are rejected by customer servers with permanent "unknown user" SMTP and DSN codes. Any recipient address that has been rejected by a customer server ten or more times in the preceding five days is blacklisted. Blacklisted addresses will be rejected immediately by domainMX.net servers; delivery to customer servers will not be attempted. Blacklisted addresses will be removed from the list after five days, though additional failures may put the address back on the list after only a few hours.
If you find that a legitimate address within your domain is being rejected by the domainMX.net servers you should report this immediately using the contact information above. Blacklisted recipients are rejected with the following error:
550 5.7.1 <firstname.lastname@example.org>... too many failures for this recipient
In addition, all "bounce" messages related to permanent failures (SMTP 5xx codes) are being aggressively filtered prior to delivery. After this change, most (99%+) bounce messages are being dropped when an email from a non-customer domain is rejected by a customer SMTP server with a permanent error code.
I resisted making these changes for a long time, as I think DSN errors and bounce messages serve a purpose. Unfortunately, the few cases where they are useful wind up buried under the flood of bounces for randomly targeted spam. This brings the domainMX.net behavior in line with current Internet best practice in this area.
Current issues will be listed here once I become aware of them.
Time and date information for planned outages should be considered
approximate, and is subject to change.
I've collected some information that may help you resolve email related problems on your own. This information is provided as-is, and your mileage may vary. Enjoy!
Adding MX records to your DNS information
Test your MX servers
Traceroute/Ping your server from the domainMX.net servers