There appears to be a DNSSEC issue with reverse DNS records on 18.104.22.168/8, so if your IP lands in this range (22.214.171.124-126.96.36.199), you’re probably going to find yourself unable to send much email today.
The issue is DNSSEC related, so this will only impact receivers who use DNSSEC resolvers, but as Word To The Wise points out, this is nearly every major mail server today.
Hopefully arin.net is working on the problem, but due to TTLs and caching, DNS issues can linger for a couple of days.
As a sender, what can you do? Well, mostly, nothing but wait it out. As a receiver, you could exempt rDNS checks from this IP range, or just make sure that your mail server returns a temporary (4xx) failure and not a permanent failure for DNS errors on reverse DNS queries, such that mail queues up and is re-delivered rather than refused.
If you happen to be using an external mail filtering service or appliance, one of the critical setup steps is to ensure that MDaemon is configured to not accept messages that attempt to bypass your mail filtering service as spammers look ways to bypass filtering gateways.
There are multiple ways to accomplish this in MDaemon, but one of the easiest ones is often overlooked: IP Shield. IP Shield is a very simple feature, it provides an administrator a simple way to tell MDaemon to only accept mail from a particular domain if it matches one of the listed IP addresses. Once upon a time, this was used to prevent spammers and others from forging one’s own domain, but there are better ways to accomplish this in MDaemon now, so today, we’ll use IP Shielding in another way: By using wildcards. With a wildcarded sender domain, you can use IP Shield to ensure that MDaemon will only accept mail if it’s from a pre-defined IP address or uses authentication.
Open the Security menu
Click on Security Settings
Under Sender Authentication, open the IP Shield dialog
Uncheck Do not apply IP Shield to messages sent to valid local users
Check Do not apply IP Shield to authenticated sessions
Check Do not apply IP Shield to Trusted IPs
Check IP Shield honours aliases
Uncheck Check FROM header against IP Shield
In the Domain field, enter *
In the IP field, the IP address of your mail filtering gateway
Repeat these steps to add any other IPs that should be allowed to send mail without authentication.
Note that you can use wildcards and CIDR notation for IP addresses here.
Since users should be configured to use authentication, this will not impact normal user traffic, but it will block any unauthenticated attempt to send mail unless the IP matches one of the entries.
We’ve recently become aware of a phishing scheme targeting customers of various registrars. Since this is targeting administrators directly, I felt it was worth of a mention even though it’s not MDaemon specific. This is a little difference from most phishing as it’s targeted to domain owners, and specifically mentions their domain registrar by name.
An example message sent to one of my own addresses is below, noting that I am using “TUCOWS, INC.” as my registrar for the domain in question.
Dear Dave Warren,
The Domain Name HIREAHIT.COM have been suspended for violation of the TUCOWS, INC. Abuse Policy.
Multiple warnings were sent by TUCOWS, INC. Spam and Abuse Department to give you an opportunity to address the complaints we have received.
We did not receive a reply from you to these email warnings so we then attempted to contact you via telephone.
We had no choice but to suspend your domain name when you did not respond to our attempts to contact you.
Click here and download a copy of complaints we have received.
Please contact us for additional information regarding this notification.
Spam and Abuse Department
As with all phishes, you should simply ignore and delete it without any further action (or report it to the sending network, if you have the time and energy to hunt it down)