![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
At 20:21 01-03-2009, Dave CROCKER wrote:
What inconsistencies are you seeing, specifically, so we can fix them.
email-arch Section 2.2.2 "The Relay performs MHS-level transfer-service routing and store-and- forward, by transmitting or retransmitting the message to its Recipients. The Relay adds trace information [RFC2505] but does not modify the envelope information or the message content semantics. It can modify message content representation, such as changing the form of transfer encoding from binary to text, but only as required to meet the capabilities of the next hop in the MHS." RFC 5321 Section 2.3.10: "A "relay" SMTP system (usually referred to just as a "relay") receives mail from an SMTP client and transmits it, without modification to the message data other than adding trace information, to another SMTP server for further relaying or for delivery."The draft says that a relay can modify message content representation whereas RFC 5321 says that a relay does not do any modification to the message data other than adding trace information.
Regards,-sm
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.