search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

Wrong reference to section 3.7 in section 4.5.5 #45

Closed ietf-svn-bot closed 3 years ago

ietf-svn-bot commented 3 years ago

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

Alessandro Vesely wrote:

Section 4.5.5 starts with the paragraph:

There are several types of notification messages that are required by
existing and proposed Standards to be sent with a null reverse-path,
namely non-delivery notifications as discussed in Section 3.7, other
kinds of Delivery Status Notifications (DSNs, RFC 3461 [33]), and
Message Disposition Notifications (MDNs, RFC 3798 [37]).  All of

Now, Section 3.7 is "Mail Gatewaying". What is it referenced for here?

Perhaps, the paragraph should refer to Section 3.6.3, "Message Submission Servers as Relays", which discusses non-delivery notifications.

Issue migrated from trac:45 at 2022-01-31 12:37:29 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Proposed resolution:

https://mailarchive.ietf.org/arch/msg/emailcore/XanBD97AFqV519_aLNRWU-C88Mc/

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 3 years ago

@alexey.melnikov@isode.com commented

John Klensin wrote:

After doing a bit of checking, I don't know quite how this happened, but it appears to me that either 3.6.2 or 3.6.3 is what was intended (there is mention of NDNs in the former too, although only as a disclaimer. I'd going to take 3.7 out and add both of those for -02; one or the other can be removed if people like.

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set resolution to fixed

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Resolved in -02.