We've made a recent switch from a third-party service to an in-house solution to address the demand for better spam protection. With the observed benefit of meeting a better spam-free email environment, this change also affords us quicker turnarounds for new features, stability, closer alignment with our acceptable use policy, and better outbound IP protection from external blacklists.
The development team is also hard at work implementing a new feature to the spam solution that will intelligently adjust spam policies based on everyday user interaction with our Hostedemail product.
- Email troubleshooting
- Additional troubleshooting
Cannot receive or marking emails as spam
- Ensure that the domain's MX records are properly configured and pointing to Enom using a DNS lookup tool.
- Ensure that the email receiving address is not blocking the sending address.
- Check the user's block list and webmail filter settings.
- You will want to verify that the recipient is blocking neither the sending IP, IP range, domain, or user.
- Obtain the sending IPs from the received message headers at the end of the 'Received-SPF' line.
- Check whether the sender's DMARC, DKIM, and SPF policies match what's found in the receiving users' mail headers.
- Identify the sending IP, see whether you can identify the IP within the SPF TXT record of the sending domain. Use the SPF record checker tool to validate the correct IP.
- Check the headers to identify whether the DKIM validation passed using the 'X-HE-DKIM-Result' line of the header data.
- Check the sending domain's DMARC policy. If the DKIM or SPF validation failed, then the policy can give insight into why the sender's message was marked as spam or rejected altogether.
Cannot send emails
Start by distinguishing the possible error reasons, an SMTP-reject or a bounce-reject.
|Type of reject||Reason|
|SMTP-reject||The email client (Thunderbird, Apple Mail, etc.) or webmail client produces a pop-up stating the message cannot be sent. This means that we are not allowing the message to be sent.|
|Bounce-reject||The user sends the email and later discovers a message in their inbox stating the message was not delivered. This means that recipient Y's email server rejected the message.|
- Ask your user to save a draft of the message and review it yourself.
- Would the contents and size of the recipient list of this message be largely considered spam by a foreign recipient(s)?
- Does this message meet the terms of our acceptable use policy?
- If the user is disabled/suspended from sending emails, submit a ticket so we can further investigate.
Ask the user for a copy of their auto-generated undelivered mail bounce message. The recipient email server, at its discretion, may or may not provide a reason why the message was rejected. If a reason is provided, attempt to self-serve and correct the reason for rejection as there are many common reasons possible.
- The recipient does not exist.
- The recipient's mailbox is full.
- The sender did not pass SPF, DKIM, DMARC policy check.
- Sender's IP is blacklisted.
- For these cases, contact our support team as we may arrange to have the IP delisted.
If you still need assistance determining the reason for message delivery failure, contact us and provide the necessary information needed to troubleshoot further.
- The recipient's email address.
- The sender's email address.
- The date, timestamp, and timezone of the failure.
- The error message and any associated bounceback email headers.
Article is closed for comments.