Loading
Prepare for Email to Become the Default Login ExperienceRead More
Sales Productivity
Email Log Reference

Email Log Reference

Understand the format and field values of email log files.

Required Editions

Available in: Lightning Experience and Salesforce Classic
Available in: All Editions except for Database.com
User Permissions Needed
To access email logs: Modify All Data

The following table describes the format of the log file and lists examples of its fields:

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 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 that the email 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 isn’t 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 wasn’t accepted and the requested action didn’t occur. However, the error condition is temporary and the action may be requested again.
5xx - Permanent Negative Completion reply
The command wasn’t accepted and the requested action didn’t 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

If the email was sent successfully, the email’s encryption.

This information is valid only when Mail Event is set to D.

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 the email was encrypted and successfully sent, this value indicates 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
R Email Direction

The category of the email.

The possible values are:

Outbound
Emails that originate in Salesforce and sent to targeted recipients.
Inbound
Emails sent via external senders to specific service addresses in Salesforce.
Outbound
S Sent via TLS

Indicates whether the email was sent via TLS.

true
Sent via TLS
false
Sent without TLS
true
T TLS Option

TLS setting used for the email.

0
None
1 - Preferred
If the message transfer agent (MTA) advertises TLS and a common cipher was negotiated, TLS was used. If TLS couldn’t be negotiated, the email was delivered.
2- Required
If TLS couldn’t be negotiated or a common cipher couldn’t be agreed on, the email bounced back to the originator.
3- Preferred Verify
If the MTA advertises TLS, a common cipher was negotiated, and Salesforce verified the receiver, TLS is used. Verification means that a valid certificate authority has signed the receiver’s certificate and the hostname in the certificate matches the host to which we connected. If TLS couldn’t be negotiated or the verification failed, the email was delivered unencrypted.
4 - Required Verify
If TLS couldn’t be negotiated, a common cipher couldn’t be agreed on, or the sender couldn’t be verified, the email bounced back to the originator. Verification means that a valid certificate authority has signed the receiver’s certificate and the hostname in the certificate matches the host to which we connected.
1
U SPF status

The Sender Policy Framework (SPF) authentication status of the email.

Pass
SPF check succeeded, and the email passed the authentication process.
Fail
The SPF check failed
None
An SPF record wasn’t published for the sender's domain.
Pass
V Sender ID status

Sender ID authentication status of the email.

Pass
The Sender ID check succeeded, and the email passed the authentication process.
Fail
The Sender ID check succeeded, and the email passed the authentication process.
None
The Sender ID check wasn’t performed.
Pass
W Sender ID PRA status

The Sender ID PRA (Purported Responsible Address) authentication status of the email.

Pass
The Sender ID PRA check succeeded, and the email passed the authentication process.
Fail
The Sender ID PRA check failed, or the email failed the authentication process.
None
The Sender ID PRA check wasn’t performed.
Pass
X DomainKeys status

DomainKeys status of the email.

Pass
The DomainKeys check succeeded.
Fail
The DomainKeys check failed.
None
Typically occurs when a DomainKeys check wasn’t performed.
Pass
Y Header From

The From field in the email header.

My Email <my.email@acme.com>
Z DKIM Selector

The DKIM selector of the email.

A DKIM selector is a string used to locate the appropriate public key in the sender's DNS records.

In this example DKIM signature, the DKIM Selector is selector202307

DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector202307; c=relaxed/simple; q=dns/txt; h=From:Subject:Date:Message-ID; bh=XXXXXXXXXXXXXXXXXXXXXX; b=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY 
selector202307
AA DKIM Domain

The domain associated with the DKIM signature. Specifically, the domain that owns the cryptographic keys used to sign the email message.

In this example DKIM signature, the DKIM Domain is example.com.

DKIM-Signature: v=1; a=rsa-sha256; d=example.com; ...

example.com
AB DKIM Success

Indicates whether the DKIM-Signature header was included in the email headers.

true
The email headers included the DKIM-Signature header.
false
The email headers didn’t include the DKIM-Signature.
none
Either the DKIM Domain or DKIM Selector wasn’t available.
true
 
Loading
Salesforce Help | Article