rfc2822_missing_headers
March 26, 2020
Contributors
Name
rfc2822_missing_headers — rfc2822 conformance
Synopsis
rfc2822_missing_headers = "reject"
rfc2822_missing_headers = "allow"
Description
RFC 2822 requires that all messages consist of headers and a body, separated by a blank line. By default, Momentum will reject messages that are missing their headers, but by setting the Missing_Headers option to "allow", it will accept those messages and treat them as header-less messages, prepend trace headers as normal.
Scope
rfc2822_missing_headers is valid in the global and the pathway scopes.
See Also
rfc2822_lone_lf_in_body, rfc2822_lone_lf_in_headers, rfc2822_messageid_header, rfc2822_trace_headers, rfc2822_max_line_length, rfc2822_date_header, rfc2821_pedantic_address_rules, rfc2821_allow_whitespace_in_envelope