rfc2822_lone_lf_in_headers

March 26, 2020 Contributors

Name

rfc2822_lone_lf_in_headers — rfc2822 conformance

Synopsis

rfc2822_lone_lf_in_headers = "fix"
rfc2822_lone_lf_in_headers = "pedantic"

Description

RFC 2822 (section 2.2) requires that all headers end with a carriage return (CR) and a linefeed (LF). Technically, any MTA that accepts messages that do not separate headers with a CR LF sequence is not compliant. Therefore, the default behavior is to reject those messages during the SMTP session.

Many mail user agents do not comply to this standard and send messages with headers separated by lone LF. While non-compliant, you can have Momentum rectify these mistakes upon message reception by setting this option to "fix". Note: Setting this to "fix" will incur a slight performance penalty during reception. However, the performance impact is very small (almost negligible for a single message) and only applies to the messages that are badly formatted.

When set to fix, this option also fixes lone CRs.

Scope

rfc2822_lone_lf_in_headers is valid in global and pathway scopes.

See Also

rfc2822_lone_lf_in_body, rfc2822_messageid_header, rfc2822_missing_headers, rfc2822_trace_headers, rfc2822_max_line_length, rfc2822_date_header, rfc2821_pedantic_address_rules, rfc2821_allow_whitespace_in_envelope