Generate Email Log for Troubleshooting Delivery

Email logs are very useful when troubleshooting potential email delivery problems. Email logs can pull data associated with emails sent by your improveit 360 system from the last 30 days, available as a .CSV file to download. 

• Navigate to Setup > Environments > Logs > Email Log Files.

• Click on Request an Email Log button.
• Fill out the parameters of your request: Start and End Time, and if you want to filter by any specific To/From email addresses. The log may take a few minutes to generate, so you can enter a delivery notification recipient who will be emailed a copy of the log when it is finished generating.
• Click Submit Request.

Reading the CSV File/Email Log

The following table describes the format of the log file and lists examples of its fields (Source: here):

COLUMN	FIELD	DESCRIPTION	EXAMPLE
A	Date/Time	The date and time the message was sent, in GMT	3/06/2009 13:37
B	Internal Message ID	The unique internal ID of the message	16/A4-20983-88E21E84
C	Mail Event	Indicates the final email event in the mail server. Events can be one of the following values: R - Reception The email was successfully received. D - Delivery The email was successfully sent. T - Transient Failure The email transmission was delayed. Salesforce retries delivery over a 24-hour period. The first retry occurs five minutes after the first transient failure, the second occurs ten minutes after that, the third twenty minutes after that, and so on. P - Permanent Failure The email could not be delivered.	T
D	Recipient	The email address of the person to whom the email is sent	[e-mail]
E	Sender	The Envelope From address used in the email. The default value is the email address of the person who sent the email. If Email Security Compliance or Bounce Management are enabled, this address contains *.bnc.salesforce.com.	[e-mail]
F	Remote Host	The IP address of the application server that delivered the email to the email server	10.0.0.1
G	Bytes Transferred	The size of the email	11856
H	User ID	The Salesforce ID of the user who sent the email	00540000000rSXT
I	Message ID Header	The ID header at the beginning of every email	21749386.​106091224027705044.​JavaMail.​sfdc@na2-app4-2-sjl.​ops.sfdc.net
J	Retry Count	The number of attempts made to deliver the email	11
K	Seconds in Queue	The number of seconds the email had to wait before being delivered	300
L	Delivery Stage	The final stage the delivery was in before it was logged. The values of the stages in the order that they appear during the SMTP sequence are: BANNER The SMTP connection response EHLO The beginning of the session with the mail server STARTTLS Establishes a secure communication session with the email server MAIL FROM Announces the sender of the email RCPT TO Announces the recipient of the email DATA Announces that the subsequent text is the email message BODY The state when the body of the email is being sent to the recipient RSET Resets the server state, ending the session In addition, there are responses that can appear at any point during the delivery sequence: while not connected The client is trying to establish a connection while idle The client has connected, but is not sending or receiving any commands reading confirmation A command was sent and the client is waiting for a response handshaking TLS An error occurred while trying to establish a secure connection out of band bounce The receiving server accepted a command, but then for an unknown reason rejected it in unknown state An unknown error has occurred	during RCPT TO
M	Relay Address	The hostname of the designated relay system	relay.my.org
N	Relay Port	The port of the designated relay system	587
O	Delivery Status Notification	After every delivery stage, a three-digit response code is sent from the mail server. The first number indicates whether the command was successful or unsuccessful; the second digit indicates the type of error; and the third provides additional information to resolve the potential problem. The five possible values of the first digit are: 1xx - Positive Preliminary reply The command was accepted, but no response has been sent 2xx - Positive Completion reply The requested action has successfully completed 3xx - Positive Intermediate reply The command was accepted, but the requested action needs more information 4xx - Transient Negative Completion reply The command was not accepted and the requested action did not occur. However, the error condition is temporary and the action may be requested again. 5xx - Permanent Negative Completion reply The command was not accepted and the requested action did not occur Every email service provider implements the codes differently, so there is no comprehensive list for what the second or third digits indicate. For more information on these codes, view the official SMTP documentation, section 4.2.1: http://​www.ietf.org/rfc/rfc2821.txt​?number=2821	421 no adequate servers
P	TLS_Cipher	The encryption of an email that was sent successfully. This information is valid only when Mail Event is set to D - Delivery. The valid entries are: TLS version:cipher The TLS version and cipher : The message wasn’t encrypted None The message was used for an internal delivery	TLSv1.2:AES256-GCM-SHA384
Q	TLS_Verified	If a successfully sent email was encrypted, this value shows whether the encryption certificate was verified against the configured certificate authorities. This information is valid only when Mail Event is set to D - Delivery. The valid entries are: Verified The peer certificate was verified against the configured certificate authorities Unverified The peer certificate wasn’t verified against the configured certificate authorities	Verified

More Information:

• Salesforce: Request an Email Log
• Salesforce: Email Log Reference
• Error Codes: Common Email Log Error Codes