search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

Exploders seem to be prohibited from adding List-* header fields #4

Closed ietf-svn-bot closed 2 years ago

ietf-svn-bot commented 3 years ago

keyword_SMTP owner:alexey.melnikov@isode.com type_defect | by alexey.melnikov@isode.com

3.9. Mailing Lists and Aliases

An SMTP-capable host SHOULD support both the alias and the list models of address expansion for multiple delivery. When a message is delivered or forwarded to each address of an expanded list form, the return address in the envelope ("MAIL FROM:") MUST be changed to be the address of a person or other entity who administers the list. However, in this case, the message header section (RFC 5322 [11]) MUST be left unchanged; in particular, the "From" field of the header section is unaffected.

In particular "MUST be left unchanged" seems to prohibit addition of header fields.

Issue migrated from trac:4 at 2022-01-31 12:33:17 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set component to smtp

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Discussion: https://mailarchive.ietf.org/arch/msg/emailcore/Cs0f39GQqVblw7PQKM7_S4lcRVQ

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed status from new to assigned

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set owner to alexey.melnikov@isode.com

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com commented

Discussion at the January 2022 interim ended with the suggestion to remove:

However, in this case, the message header section (RFC 5322 [11]) MUST be left unchanged; in particular, the "From" field of the header section is unaffected.

However further discussion continued after the interim meeting on the mailing list.

aamelnikov commented 2 years ago

This was implemented in -11.