Differences

This shows you the differences between two versions of the page.

--- pub:smtpi [2024/08/20 12:30] – [Relay Issues] kkramer
+++ pub:smtpi [2024/08/23 21:57] (current) – [Relay Issues] kkramer
@@ Line 165: / Line 165: @@
 ===== Relay Issues =====
-We have a user that is reporting that email is not reaching one of their recipients. The email appears as **‘SNT’** in the iMail log, but it was confirmed that they did not receive the email.
+A user reported that a specific email is not reaching one of their recipients. The email appears as **‘SNT’** in the iMail log, but it was confirmed that the recipient did not receive the email.
 If the user sends email to this email address from Outlook it works fine.  Just not working out of the iMail server.
@@ Line 173: / Line 173: @@
 In the job, we can see the successful negotiations to the email server/relay. iMail reached out to the email server/relay and the server/relay replied with an acknowledgment. Later, we see that the email server/relay replied with the message that it queued up the message for sending "R: 250 2.0.0 Ok: queued as 76987E006C". The question is: Did the email server/relay send the email package that it placed in the queue and what was the output of sending the email or not sending the email to the recipient "eaglenest@lakestreetcom.com".
 {{:pub:imail:imail-ns2.jpg?600|}}\\
-Based on the provided log information from the exchange server, below is a breakdown of the information provided.  It clearly shows that the email for "eaglelake@mainstreet.com" was not sent. See the information under Conclusion and Issues for the details.
+Below is a breakdown of the information provided from the **exchange server**.  It clearly shows that the email for "eaglelake@mainstreet.com" **was not sent**. See the information under Conclusion and Issues for the details.
 . Email Connection and Processing:
@@ Line 190: / Line 190: @@
      - Status: Sent.
-Conclusion:
+**Conclusion:**
 - The email to `XXRISKI@XXMETALS.COM` was successfully sent.
 - The email to `eaglenest@lakestreetcom.com` was not sent and is currently deferred due to the sending server's IP being listed on Cloudmart CSI Suspect.
-Issues:
+**Issues:**
 - The main issue is that the IP `[999.41.198.25]` is listed on the Cloudmart CSI Suspect list, causing the email to `eaglenest@lakestreetcom.com` to be deferred. This needs to be addressed to ensure successful delivery.
@@ Line 204: / Line 204: @@
 Senders can check to make sure they have good email authentication protocols, reverse DNS lookup, good IP address reputation (not on a blacklist), good content quality, and make sure emails are not accidentally sending malicious email content.
-Helpful items to consider when assuring that emails going from iMail on your IBM i server through a relay server successfully reach recipients without being blocked or rejected by receiving email servers. These items will help mitigate situations in which iMail successfully hands the email package to the relay server for transport, but the email does not reach the recipient on the To Address of the email.
-===== Considerations =====
-Helpful items to consider when assuring that emails going from iMail on your IBMi server through a relay server successfully reach recipients without being blocked or rejected by receiving email servers. These items will help mitigate situations in which iMail successfully hands the email package to the relay server for transport, but the email does not reach the recipient on the To Address of the email.
+===== Relay Considerations =====
+Helpful items to consider when assuring that emails going from iMail on your IBM i server through a relay server successfully reach recipients without being blocked or rejected by receiving email servers. These items will help mitigate situations in which iMail successfully hands the email package to the relay server for transport, but the email does not reach the recipient on the To Address of the email.
 . Email Authentication Protocols
@@ Line 240: / Line 240: @@
 . Check for Malware or Phishing Links
-  * •	Scan Emails: Regularly scan outgoing emails to ensure they don’t contain malicious attachments or phishing links, as these are prime reasons for being marked as spam.
+  * 	Scan Emails: Regularly scan outgoing emails to ensure they don’t contain malicious attachments or phishing links, as these are prime reasons for being marked as spam.
 . Email Throttling