This example illustrates the sort of log file entry resulting when the MTA rejects a remote side’s attempt to submit a message. (This example assumes that no optional LOG_* options are enabled, so only the basic fields are logged in the entry. Note that enabling the LOG_CONNECTION option, in particular, would result in additional informative fields in such J entries.) In this case, the example is for an MTA that has set up SMTP relay blocking (see 18.7 Configuring SMTP Relay Blocking) with an ORIG_SEND_ACCESS mapping, including:
ORIG_SEND_ACCESS ! ...numerous entries omitted... ! tcp_local|*|tcp_local|* $NRelaying$ not$ permitted
and where email@example.com is not an internal address. Hence the attempt of the remote user firstname.lastname@example.org to relay through the MTA system to the remote user email@example.com is rejected.
26-Feb-2007 14:10:06.89 tcp_local JE 0 (1) firstname.lastname@example.org rfc822; email@example.com (2) 530 5.7.1 Relaying not allowed: firstname.lastname@example.org (3)
This log shows the date and time the MTA rejects a remote side’s attempt to submit a message. The rejection is indicated by a J record. (Cases where an MTA channel is attempting to send a message which is rejected is indicated by R records, as shown in Example 25–4 and Example 25–5).
The last J record written to the log will have an indication stating that it is the last for a given session. Also, the current version of Messaging Server does not place a limit on the number of J records.
The attempted envelope From: and To: addresses are shown. In this case, no original envelope To: information was available so that field is empty.
The entry includes the SMTP error message the MTA issued to the remote (attempted sender) side.