Other

Best Practices

Watch Your Email Reputation

Email marketing campaign servers with a low email reputation score will typically experience aggressive algorithms that will filter every email coming from that specific IP address. On the other hand, maintaining a high reputation score will see less intrusive filtering only applied to individual emails and email campaigns instead of blanket IP addresses. It would be definitely beneficial to not let other users to influence your email reputation. For example, if you are on a shared server – other companies/users could be sending out their own campaigns without filtering emails through our service. It would be a waste if you spent all the time and investment controlling your email campaigns and someone else is just email blasting causing the entire IP to be affected.

Improve Your Email Reputation

After using our service to filter out emails, if the scores are already terrible for your current email campaign server IPs, it might benefit to do email campaigns on a new or more reputable IP to see better ROI. This would start your email reputation on a clean slate. As a disclaimer, we are not sure how feasible this would be for everybody but your team will need to discuss internally. However, using our service on existing IP should raise the reputation score for that specific IP. On IPs with existing completed high volume campaigns, the scores will be slow to change.

Result Code Best Practices

There are two main use cases for Global Email result codes.

1. Validating emails at the point of entry on a web entry form

2. Sending bulk emails in a marketing campaign.

Each case will require their own set of standards, and a different approach. Provided below is our recommendation on how to treat specific result codes.

• Accept – Send mail. There is a high chance of email delivery success.

• Caution – Email delivery not guaranteed.

• Reject – Do not send.

These recommendations are to be used as a reference, and each case may vary from user to user.

Note

For a full list and definitions of the available result codes for Global Email, see: Result Codes

Code	Short Description	Email Marketing Campaign	Point of Entry
ES - Email Status		Melissa Recommendation
ES01	Valid Email	Accept	Accept
ES03	Unknown Email	Reject	Reject
ES04	Mobile Email Address	Reject	Accept
ES05	Disposable Domain	Reject	Caution
ES06	Spamtrap Domain	Reject	Caution
ES07	Accept All Server	Caution	Accept
ES08	Role Address	Caution	Accept
ES09	Protected Mailbox Caution	Caution	Accept
ES10	Syntax Changed	Accept	Accept
ES11	Top Level Domain Changed	Accept	Accept
ES12	Domain Changed (Spelling)	Accept	Accept
ES13	Domain Changed (Update)	Accept	Accept
ES20	Verify (Precision: Domain Result)	Caution	Accept
ES21	Verify (Precision: Cached Mailbox Result)	Accept	Accept
ES22	Verify (Precision: Real-time Mailbox Result)	Accept	Accept
ES23	Verify (Precision: Unicode Result)	Caution	Accept
ES24	Verify (Precision: Pending Mailbox Result)	Caution	Accept
ES30	Privacy Flag (TLD)
ES31	Suspicious Characters
ES36	Spamtrap Mailbox
ES37	Breach Flag
EE - Email Error
EE01	Email Syntax Error	Reject	Reject
EE02	Email Domain Not Found	Reject	Reject
EE03	Email Server Not Found	Reject	Reject
EE04	Invalid Email	Reject	Reject
DE - Domain Error
DE03	Domain Not Found
DV - Domain Verified
DV01	Domain Found
Transmission Service Error
SE01	Cloud Service Internal Error	Reject	Reject
General Transmission Error
GE01	Empty Request Structure	Reject	Reject
GE02	Empty Request Record Structure	Reject	Reject
GE03	Records Per Request Exceeded	Reject	Reject
GE04	Empty License Key	Reject	Reject
GE05	Invalid License Key	Reject	Reject
GE06	Disabled License Key	Reject	Reject
GE07	Invalid Request	Reject	Reject
GE08	Product/Level Not Enabled	Reject	Reject
GE09	Customer Does Not Exist	Reject	Reject
GE10	Customer License Disabled	Reject	Reject
GE11	Customer Disabled	Reject	Reject
GE12	IP Blacklisted	Reject	Reject
GE13	IP Not Whitelisted	Reject	Reject
GE14	Out of Credits

ES37 - Breach Flag Usage Guidelines

The ES37 result code enhances both internal and client security by identifying potentially compromised email accounts. However, it’s important to note that the Breach Flag is not intended as an anti-fraud measure. Emails marked with an ES37 code should not be dismissed as fraudulent solely based on this flag. Instead, the code serves as a warning flag, prompting additional monitoring or two-factor authentication (2FA) for the affected email address.