Start a conversation

Top 10 Common Questions - Mimecast

How can I verify a message has been delivered?

Mimecast provides full tracking details for every message that has routed through our platform.  By navigating into the details of a particular message, you can confirm the recipient’s mail server that accepted the message and the exact time it was processed.


Why was a message delayed?

While you should always review the tracking and receipt information for the message first, “greylisting” is the most common cause of delayed messages.  This occurs when an email sent to a particular user originates from a sender/IP address that we haven’t seen before, and we therefore impose a temporary delay of 60 seconds and make the sender retry the connection.  This is a common practice in the email security industry, as it helps to dramatically cut down on inbound spam messages.  You can see all of these greylisting events within the Connection Attempts Viewer.



How can I tell if my message was delivered using encryption/TLS?

Within the delivery details, Mimecast indicates if a message was delivered via TLS or via our Secure Messaging web portal solutions:


Why can’t I receive emails from my own domain name from external sources?  Why am I getting an “Anti-Spoofing policy - Inbound not allowed” error?

By default, Mimecast configures anti-spoofing policies for your organization that prevent inbound emails with your domain name from reaching your users.  It’s easy to make exceptions to this policy for legitimate senders that are sending inbound messages on your behalf.


How do I permit or block a sender for either one user or my whole company?

Mimecast provides great flexibility in setting up block and permit policies for your organization – these can be setup per user or for the entire organization:


How do I permit or block all subdomains for a particular domain name?  Can I add a wildcard to the Permitted Senders group?

While it’s not possible to add wildcard entries to your Permit and Block default groups (within Directories – Groups) you can easily create a Permit or Block policy that accomplishes this.  Use the “Domain” entry within the policy and simply set it to *



What’s the difference between a rejection and a bounce?

Rejections are emails that Mimecast never accepted for delivery, either due to a policy, IP reputation, or content of the message.  Bounces are emails that Mimecast accepted that we couldn’t then deliver to their final destination.  They are broken out in the platform for easy tracking.


How can I release a rejected email?

As per the question above, an email that you see in the Rejection Viewer was never accepted for delivery by Mimecast, and therefore the email cannot be released or forwarded on to the end user.  Once you make the appropriate policy change to allow acceptance of this email, you’d need to have the originator re-send it to you.


How do I export mail from Mimecast?

Mimecast Administrators with sufficient privileges can export data directly through the Administration Console.


Why was this message held?  How do I release it?  Can I track when a message was released by a user?

Administrators have full traceability of all held emails on the platform and can release them on behalf of their user community when appropriate.  Our hold release log shows when emails were released (and who released them):

Choose files or drag and drop files
Was this article helpful?
  1. Carlos Rios

  2. Posted