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 > Administration Setup > Monitoring > 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:
|
T |
| D | Recipient | The email address of the person to whom the email is sent | admin@acme.com |
| 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. | user@acme.com |
| 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:
In addition, there are responses that can appear at any point during the delivery sequence:
|
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:
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:
|
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 |
More Information:
- Salesforce: Request an Email Log
- Salesforce: Email Log Reference
- Error Codes: Common Email Log Error Codes