Glenn Parsons (gparsons@nortelnetworks.com)
Thu, 17 May 2001 15:19:10 -0400
Janusz,
Thanks for your comments...and vote of confidence
> The draft looks good. I have a three minor comments.
>
My thoughts are below.
Cheers,
Glenn.
> - 4.2.6, RECEIVE RULES: I find this section a bit vague. First, it is not
> clear why there would be "further delivery errors" after the system has
> received the message - please clarify. Second, the meaning of "the message
> is acknowledged" is vague - does this mean: accepted by the receiving
> system in the SMTP session? anything else?
>
Hmmm, we were talking about gateways to legacy... How about:
If the receiving system is incapable of storing the return path (or MAIL
FROM) to be used for subsequent delivery errors (i.e., it is a gateway to a
legacy system or protocol), the receiving system must otherwise ensure that
further delivery errors don't happen. Systems that do not support the return
path MUST ensure that at the time the message is acknowledged (i.e., when a
DSN would be sent), the message is delivered to the recipient's ultimate
mailbox. Non-Delivery notifications SHOULD NOT be sent after that final
delivery.
> - 4.2.12: should be organized into SEND section and RECEIVE sections
>
Good point. How about:
4.2.12 Content-Transfer-Encoding Because Internet mail was initially specified to carry only 7-bit US- ASCII text, it may be necessary to encode voice and fax data into a representation suitable for that environment. The "Content-Transfer- Encoding:" header describes this transformation if it is needed.
SEND RULES
An implementation in conformance with this profile SHOULD send audio and/or facsimile data as "Binary" when binary message transport is available (see section 5). When binary transport is not available, implementations MUST encode the audio and/or facsimile data as
"Base64".
RECEIVE RULES
Conforming implementations MUST recognize and decode the standard
encodings, "Binary", "7bit, "8bit", "Base64" and "Quoted-Printable"
[MIME1]. The detection and decoding of "Quoted-Printable", "7bit", and "8bit" MUST be supported in order to meet MIME requirements and to preserve interoperability with the fullest range of possible devices.
> - In the conformance table, I still see "Content-Langauge" (i.e.
> misspelled Language).
>
Oops :-) Will fix.
This archive was generated by hypermail 2.0b3 on Thu May 17 2001 - 22:20:01 IDT