Is there any chance the BDAT/Chunking support will be added to sendmail?
Our "friends" at MS365 have changed have changed something:
Chunking and the BDAT command. In an effort to better support security standards (for example, DomainKeys Identified Mail or DKIM), Office 365 no longer removes bare line feeds from messages."
"Email servers that supports the SMTP BDAT command can accept messages
with bare line feeds. Most modern email servers support BDAT; however,
Unlikely - there doesn't seem to be any real benefit that would
outweigh the conversion overhead.
The interesting question is how MS and Google will handle this. If they
make it mandatory, it will be hard for others not having support for it.
What does the Proofpoint company say about BDAT support?
The interesting question is how MS and Google will handle this. If they
make it mandatory, it will be hard for others not having support for it.
BTW: RFC 3030:
5) Servers that offer the BDAT extension MUST continue to support
the regular SMTP DATA command. Clients are free to use DATA to
transfer appropriately encoded to servers that support the
CHUNKING extension if they wish to do so.
5) Servers that offer the BDAT extension MUST continue to support
the regular SMTP DATA command. Clients are free to use DATA to
transfer appropriately encoded to servers that support the
CHUNKING extension if they wish to do so.
So that means what MS does RFC violation again.
Marco Moock wrote:
5) Servers that offer the BDAT extension MUST continue to
support the regular SMTP DATA command. Clients are free to use
DATA to transfer appropriately encoded to servers that support the
CHUNKING extension if they wish to do so.
So that means what MS does RFC violation again.
Do you mean M$ "MTA"s do not support DATA anymore?
Can you provide evidence of your claim?
Is this specific to some M$ servers?
Marco Moock wrote:
So that means what MS does RFC violation again.
IIRC the normal SMTP DATA command makes usage of CRLF mandatory.
Is my guess right that using LF is simply a problem in the composing software?
Marco Moock wrote:
Marco Moock wrote:
So that means what MS does RFC violation again.
Doesn't look like it - at least not in this context.
IIRC the normal SMTP DATA command makes usage of CRLF mandatory.
See the fine RFCs, e.g., 5321
2.3.8. Lines
Lines consist of zero or more data characters terminated by the
sequence ASCII character "CR" (hex value 0D) followed immediately
by ASCII character "LF" (hex value 0A). This termination sequence is
denoted as <CRLF> in this document. Conforming implementations
MUST NOT recognize or generate any other character or character
sequence as a line terminator.
Is my guess right that using LF is simply a problem in the composing software?
Whatever sends "bare LF" is broken - also explained in the RFCs.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 36:47:28 |
Calls: | 6,707 |
Files: | 12,239 |
Messages: | 5,353,438 |