Pavel Kankovsky writes:
On 19 May 2000, D. J. Bernstein wrote:
allow non-MIME 8-bit mail, for example, even though the relevant RFCs
(*) If yes, what extra functionality was provided? (Apparently, it was not
an ability to transfer non-English plaintexts because you do not know how
to
On Mon, 22 May 2000, Russell Nelson wrote:
Interpreting, and encoding are two different things. You're talking
about interpretation of a bytestream, and Dan is talking about the
encoding. In particular, he's dissing Content-Transfer-Encoding:
quoted-unreadable.
Sure. But he said
On 19 May 2000, D. J. Bernstein wrote:
The word ``accept'' in 822bis means that parsers won't die.
Hmm...a secure program should never ``die'' interpreting data (from an
untrusted source). Ergo, any data should be ``accepted''. :)
No. RFCs are merely one source of information about the
On Fri, 19 May 2000, Russell Nelson wrote:
The problem with bare linefeeds is simple: their interpretation
is ambiguous on a Unix machine Because some do [send them],
qmail rejects them.
The interpretation of 8-bit characters with code = 128 is even more
ambiguous (at least unless the
Pavel Kankovsky [EMAIL PROTECTED] writes:
(*) If yes, what extra functionality was provided? (Apparently, it was
not an ability to transfer non-English plaintexts because you do not
know how to interpret bytes you receive without MIME (or MIME-like)
metadata.)
It was, in fact, an ability to
Thus said Lindsay Haisley on Fri, 19 May 2000 02:00:03 CDT:
A bare line feed is considered 'obsolete syntax' as defined subsequently in
section 4.1, 'Miscellaneous obsolete tokens'. Please note from the above
that while compliance with this draft requires that originating MTAs or
MUAs must
Version 1.03 of qmail-smtpd is currently configured to reject incoming mail
with bare linefeeds. If a bare linefeed is received, qmail-smtpd returns
an error 451 and a reference to http://pobox.com/~djb/docs/smtplf.html
which explains the error by reference to an IETF draft document known as
Lindsay Haisley writes:
Version 1.03 of qmail-smtpd is currently configured to reject incoming mail
with bare linefeeds.
Yup. The problem with bare linefeeds is simple: their interpretation
is ambiguous on a Unix machine. Same thing for a bare carriage-return
on a Macintosh. No SMTP
Yup. The problem with bare linefeeds is simple: their
interpretation is ambiguous on a Unix machine.
This is an oversimplification. Unix machines are perfectly capable of
interpreting bare LFs in whatever way the spec might say they should.
There is a practical problem because MTA and MUA
Greg Hudson writes:
Yup. The problem with bare linefeeds is simple: their
interpretation is ambiguous on a Unix machine.
This is an oversimplification.
I don't believe so. Email messages consist of lines of text. While
in transit, those lines are separated by the Tenex newline,
Thus spake Russell Nelson on Fri, May 19, 2000 at 06:58:35AM CDT
Given the differing interpretations of bare linefeeds and
carriage-returns, they must be disallowed by the SMTP specification,
and they must not be accepted by SMTP clients or servers.
Russ, thanks.
How do you reconcile this
Lindsay Haisley writes:
Thus spake Russell Nelson on Fri, May 19, 2000 at 06:58:35AM CDT
Given the differing interpretations of bare linefeeds and
carriage-returns, they must be disallowed by the SMTP specification,
and they must not be accepted by SMTP clients or servers.
Thus spake Russell Nelson on Fri, May 19, 2000 at 01:22:36PM CDT
I would point out to the author of the spec that it is requiring that
messages be mangled when received on Unix systems.
I'm sure the IETF process permits such input.
Also, the patch is there on www.qmail.org, if it bothers
Lindsay Haisley writes:
Thanks, Russ. The 'fix' is fairly trivial and I've already done it, and in
fact routinely do it for qmail installs I do. In real-world terms, it costs
more in tech support time to deal with complaints and problems resulting
from rejection of non-compliant email
Lindsay Haisley writes:
My purpose here was to inquire regarding what appears to be a conflict
between qmail and an emerging standard.
You are misinterpreting 822bis. If someone tries to relay some spam
through your server, and the spam uses obsolete syntax, do you think
that your server is
Thus spake Russell Nelson on Fri, May 19, 2000 at 02:28:22PM CDT
The tech support response should be "Your email client has a bug.
Update it to the newest version. If the problem is still present, ask
your email client vendor to fix it. Give them the smtplf URL." OTOH,
Dan could have
- Original Message -
From: "Russell Nelson" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Fri 19 May 2000 8:26
Subject: Re: The current status of IETF drafts concerning bare linefeeds
Life *is* change. You can detect the absence of life by the absence
of change. "Be
17 matches
Mail list logo
