PERMANENT ERROR STRING 552

TCP/IP-channel-specific options: PERMANENT_ERROR_STRING_552 (string)
Important note: Prior to MS 8.0.1.3, the name of this option was 552_PERMANENT_ERROR_STRING. Unfortunately the leading digit "5" in the option makes this option unworkable in unified configuration due to XML token name restrictions, so the name of the option had to be changed to PERMANENT_ERROR_STRING_552. Both names work in 8.0.1.3 and later legacy configurations.

RFC 821showed 552 as a temporary error at a RCPT TO: command (although in all other cases 500 numbers are permanent errors); some servers have  implemented inconsistent use of the 552 error number. The MTA&#x27;s SMTP client by default, if this option is not set, normally interprets 552  as a temporary error when seen as a response to an address command  (MAIL FROM:, RCPT TO:, or VRFY:); but see below for a new-in-6.3  refinement of the MTA&#x27;s behavior when a 5xy response is seen to the  first RCPT TO: command in a transaction. If this SMTP client option is set, then when an 552 response is received to an address  command (MAIL FROM:, RCPT TO:, or VRFY), then the string associated  with the last line of that response (excluding the initial "552 ", but including any leading x.y.z extended error code) is  compared against this string. If, and only if, the string matches will the 552 error be treated as permanent. Case is not significant in the comparison. For instance, if dealing with a remote server that will return "552 user no longer present" as an  "intended" permanent error, then this option could be set to: PERMANENT_ERROR_STRING_552=user no longer present This option is not supported by the LMTP client; it is an SMTP client-only option.

New in 6.3, if the MTA&#x27;s SMTP client sees any 5xy response including a 552 response to its first RCPT TO:  command in a transaction and where after issuing its error the remote  SMTP server then immediately disconnects the session, (which behavior  is, by the way, a standards violation on the part of the remote SMTP  server), then the MTA (regardless of the setting of this option) will  unconditionally interpret this as a permanent error for that recipient,  but will reenqueue any additional recipients of that message (copy) for  another delivery attempt.

New in 7.0, the option value may use glob-style wildcards; this new feature  is available to aid in cases  where a remote server&#x27;s error response includes the input address,  hence where a static, fixed value does not provide adequate matching.

As of 8.0.1.3 multiple patterns can also be specified, separated by vertical bars ("&#x7c;").

See also:
 * Mapping entry patterns
 * TCPIP-channel-specific options