To protect your email reputation, we are now enforcing stricter email address validation on prospect import to prevent spammy addresses or role-based email addresses (addresses not relating to a person) — both are generally present when people buy lists (against the rules of any email service provider) or do not have high quality data. Mailing either type of address can have a very significant impact on your deliverability and/or result in blacklisting by certain ISPs.
Now, if a user imports a CSV file which includes a prospect with an address on our list of un-mailable or role-based addresses, then that row will be rejected from the import. This screenshot is of the new import error CSV, a link to which is emailed to the user after their import has finished. Note that there is a new Error Type: Email Not Allowed.
The Import Error Description has more details; emails can now be rejected because they are role-based, or because they are likely to cause spam complaints and blacklisting.
Addresses with the following prefixes are considered un-mailable, and will not be allowed as a prospect address during import under any circumstances:
Addresses with these prefixes are likely to cause blacklisting and/org spam complaints, which can greatly affect deliverability.
Addresses with the following prefixes are role-based addresses, and are not allowed for the same reasons (the cause a huge number of spam complaints since they often represent multiple people, many of whom are not the intended recipient):
If you can demonstrate a very legitimate business need, then these role-based addresses can be temporarily enabled for you by our support team.