Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: Re: mx.gnus.org being very strict
Date: Sat, 08 May 2004 12:03:00 +0200	[thread overview]
Message-ID: <m3pt9fjkx7.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <8765ba0zup.fsf@dod.no> (Steinar Bang's message of "Thu, 06 May 2004 09:38:38 +0200")

Steinar Bang <sb@dod.no> writes:

> This goes back to the summer of 1993 when I read the MIME standard,
> and started using quoted-printable in emails, on an infrastructure that
> consisted of sendmails universally patched to do just-send-8, and a
> silently agreement that the charset used should be latin-1.
>
> Suffice to say the feedback I got from people receiving
> quoted-unreadable was so _universally_ negative, that I quickly
> stopped doing it.  In the eyes of others, things just worked, and I
> broke them.

Virtually every MUA talks MIME today, several MTAs (among them sendmail)
and MDAs (among them maildrop) and filters have options to convert
quoted-printable text/* to 8bit text/*.

What may have been an issue in the time when everyone was using Berkeley
"mail" and perhaps elm, is not an issue today. 8BITMIME set off as a
standard to smooth the transition from 7bit to 8bit, the ultimate goal
would have been that every MTA supported 8BITMIME (which may, BTW, be
implemented as returning to the sender an 8BITMIME mail that would have
been to be sent to a 7bit destination).

DJB was the first [name lacks here] to deliberately throw his sabot into
the gears, breaking the whole idea of having 8BITMIME
transitional. qmail as a gateway will happily trash mail. I still
occasionally receive mail with d or | where a German Umlaut should have
been, which proves that there are still 7bit systems in use with systems
that just-send-eight.

> So one thing I never would do, would be to set up an MTA to reject
> messages that has 8 bit, but no MIME.  I can't imaging what kind of
> standards-obsessed narrowmindedness would make anyone do so.

Yay. How does the recipient know the character set?

Norway may not face the ambiguity because virtually everything fits, but
for instance France (cœur is ISO-8859-15), Germany, Finland (Z charon,
€) suffer from the confusion whether an 8bit text is ISO-8859-1, -15,
Windows-1252 or UTF-8. Heuristics or "conventions" don't apply. The
introduction of the Euro symbol about five years ago broke the
assumption that a mail or news was in ISO-8859-1 character set.

There are means to transport that character set information.
These means are called MIME.

If the admin determines he doesn't want to relay mail lacking such
information, or information that it is 8bit content counter to what
RFC-2822 says, then that is a wise one, is a perfectly legal one (he has
the power to set his system's policies) and has my sympathy.

Given that the relay was pretty early in the delivery chain, it was the
sender who got his mail back right away - and that's where strictness
and being conservative have to apply.

-- 
Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95



  parent reply	other threads:[~2004-05-08 10:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 10:37 mx.gnus.org being very strick Lars Magne Ingebrigtsen
2004-05-01 19:36 ` Matthias Andree
2004-05-02 13:11   ` mx.gnus.org being very strict Lars Magne Ingebrigtsen
2004-05-03 10:10     ` Matthias Andree
2004-05-03 10:56       ` Lars Magne Ingebrigtsen
2004-05-03 11:51         ` Matthias Andree
2004-05-03 13:27           ` Miles Bader
2004-05-03 15:29             ` Per Abrahamsen
2004-05-03 18:13             ` Matthias Andree
2004-05-03 19:25               ` Miles Bader
2004-05-03 20:16                 ` Matthias Andree
2004-05-04  8:48                   ` Per Abrahamsen
2004-05-06  1:29                     ` Matthias Andree
2004-05-06  7:38                       ` Steinar Bang
2004-05-06 14:11                         ` Josh Huber
2004-05-06 23:09                           ` Miles Bader
2004-05-08 10:06                           ` Matthias Andree
2004-05-08 10:03                         ` Matthias Andree [this message]
2004-05-08 20:29                           ` Steinar Bang
2004-05-09 11:44                             ` Matthias Andree
2004-05-09 17:33                               ` Steinar Bang
2004-05-10 14:30                                 ` Matthias Andree
2004-05-10 17:20                                   ` Steinar Bang
2004-05-11 11:10                                     ` Matthias Andree
2004-05-16 11:48                                       ` Lars Magne Ingebrigtsen
2004-05-17  9:51                                         ` Matthias Andree
2004-05-03 14:45           ` Wes Hardaker
2004-05-03 18:15             ` Matthias Andree
2004-05-03 11:01 ` mx.gnus.org being very strick Reiner Steib
2004-05-03 11:10   ` mx.gnus.org being very strict Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3pt9fjkx7.fsf@merlin.emma.line.org \
    --to=ma@dt.e-technik.uni-dortmund.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).