108342204215229709048Q: What's the difference between Role and Catch All emails after they're being verified through your system?
Are they safe to send emails to?
ReoonSupport
May 14, 2024A: Thanks for the query. The Role emails can be compared to the Safe emails. The only difference between the role and safe are the safe emails belongs to individual person, while the role addresses are for company position (that is also valid). Please check the meaning of all statuses below.
Safe: It's pretty much self-explanatory. Everything is good about that email address, and most likely this is a personal email address.
Role: Role addresses are also valid and safe. The only difference is it is a company role-related email address (not a personal one). For example, support@reoon.com (it belongs to the support team, not an individual person).
Catch-All: This means that the email server accepts emails at any address (even if the individual address does not exist) and most likely redirects them to a specific address that an admin can read. So, if you send emails to these addresses, your email will not bounce even if that individual address does not exist.
Disposable: It is a temporary email address. A lot of companies offer temporary email addresses, which are generally valid for about one hour. Sometimes people use these addresses to verify something and after that they never check the email again (also, they will not be able to).
Invalid: It means that the email address is not available/registered. Your email will bounce back.
Inbox Full: The inbox of that user is full and can no longer receive new emails. However, if he deletes some old emails or increases storage, he can start receiving emails again.
Disabled: Similar to invalid. But that account was good before but the provider disabled that. For example, Gmail blocked an account of someone.
Unknown: We couldn't verify the status of that individual address (although the server is configured for receiving emails). Your credits are automatically refunded for such results.
Let us know if you have any other questions. Have a great day.
Understood and makes sense ... but then why is catch-all marked as NOT safe to send in the reports?
For example, we may a customer who has registered with their email address john@johnsmith.com That could be their genuine individual email which they receive and read personal emails on. Separately, they may have set up their email server for johnsmith.com to have a catch-all function ... so that any emails sent to dave@johnsmith.com or nobody@johnsmith.com all get forwarded to a specific mailbox. Perhaps this forwarding email box is also the john@johnsmith.com inbox, as they only use that but don't want to miss any other incoming mail. There's nothing wrong with that and the john email is still a good email to send marketing to. However your system would seem to suggest that just because catch-all is set up, that email isn't safe to send to? Why?
We got your point. The catch-all emails are safe for subscribed users or the email address lists that you trust. However, the story can be different for cold emailing, especially with a purchased/scraped list (sending to a small percentage compared to the full list is still okay). Let's say you send 50 emails to the users of one domain/service (which is catch-all) and let's say 20 of them are not valid (so will still delivered to an admin inbox). So if an admin checks them and finds 20 emails in that inbox came from you, the admin can mark you as a spam sender or can even block you. Some email servers also do that automatically. That's why we marked that as not safe. But you can make your decision based on the email score or status for simpler usage.