Transactional service: We sent a proof and did not receive the mail. What happen?
Sometimes it can happen that when you send a transactional mail test, the recipient does not receive it. In this article, we will address some of the possible causes of this problem and provide solutions to resolve it.
One of the most common reasons why transactional mail doesn't reach its recipient is that the sender has been blocked due to previous hard bounce responses. Hard bounces occur when the recipient's mail server permanently rejects a message due to reasons such as an invalid email address or a full mailbox. When this happens repeatedly, mail servers can take action and block the sender to protect against potential abuse or spam.
To check if the sender is blocked, the first step is to send a test with another sender, preferably from a different email address. If the transactional mail is delivered successfully, the problem is likely with the original sender. In this case, you should review your hard bounce response history and take steps to clean up and keep your contact list up to date.
In the event that the transactional mail test is not delivered even when using another sender, it is possible that corporate mail is being blocked by the recipient organization's antispam server. To rule out this possibility, it is recommended to test using a free email service provider account, such as Gmail, Hotmail or similar.
If the test is successfully delivered through a free service provider account, it is likely that the recipient's mail server is blocking corporate emails for security reasons or spam filtering policies. In this case, the security settings of the corporate mail server should be reviewed and adjusted to allow the delivery of legitimate transactional mail.
When the integration is done via API, the first step to determine the delivery problem is to check the API response itself. If the reason is that the contact was previously marked as a hard bounce, this will appear in the response to the request sent to it.
When the integration is done through SMTP, the steps indicated above must be followed to verify the possible causes of non-delivery. If the problem persists, it is recommended to contact the Icomm support team at success@icommkt.com. The technical support team will be happy to help and, if necessary, proceed with the unlocking of the account to facilitate the successful delivery of transactional emails.
Block sender for previous hard bounces
One of the most common reasons why transactional mail doesn't reach its recipient is that the sender has been blocked due to previous hard bounce responses. Hard bounces occur when the recipient's mail server permanently rejects a message due to reasons such as an invalid email address or a full mailbox. When this happens repeatedly, mail servers can take action and block the sender to protect against potential abuse or spam.
To check if the sender is blocked, the first step is to send a test with another sender, preferably from a different email address. If the transactional mail is delivered successfully, the problem is likely with the original sender. In this case, you should review your hard bounce response history and take steps to clean up and keep your contact list up to date.
Try a free service provider account
In the event that the transactional mail test is not delivered even when using another sender, it is possible that corporate mail is being blocked by the recipient organization's antispam server. To rule out this possibility, it is recommended to test using a free email service provider account, such as Gmail, Hotmail or similar.
If the test is successfully delivered through a free service provider account, it is likely that the recipient's mail server is blocking corporate emails for security reasons or spam filtering policies. In this case, the security settings of the corporate mail server should be reviewed and adjusted to allow the delivery of legitimate transactional mail.
Integration via API
When the integration is done via API, the first step to determine the delivery problem is to check the API response itself. If the reason is that the contact was previously marked as a hard bounce, this will appear in the response to the request sent to it.
Integration via SMTP
When the integration is done through SMTP, the steps indicated above must be followed to verify the possible causes of non-delivery. If the problem persists, it is recommended to contact the Icomm support team at success@icommkt.com. The technical support team will be happy to help and, if necessary, proceed with the unlocking of the account to facilitate the successful delivery of transactional emails.
Updated on: 08/09/2023
Thank you!