From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: Re: mx.gnus.org being very strict
Date: Mon, 10 May 2004 16:30:34 +0200 [thread overview]
Message-ID: <m3wu3ks6b9.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <8765b5pktg.fsf@dod.no> (Steinar Bang's message of "Sun, 09 May 2004 19:33:15 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Matthias Andree <ma@dt.e-technik.uni-dortmund.de>:
>
>> If the destination mailer doesn't adhere to the standard, it will
>> have a hard time displaying conformant mail.
>
> I don't understand what you mean by "destination mailer". If it is
> the final MTA, then the statement doesn't make sense to me.
I meant the MUA.
> If it's the destination MUA, then there are two ways of adhering to
> the standard:
> 1. strictly adhering to the standard, and refusing all mesasages that
> don't fit
The injecting agent has to reject this crap.
This is what happened in this case, no reason to complain. Fix the generator.
> 2. adhering to the standard, but put some configurable best guess on
> the messages that don't (in Norway that would typically be to
> display messages with 8bit characters and no MIME markup, as
> text/plain; charset=iso-8859-1)
> It sounds to me that you're advocating alternative 1.
Yup. I am still under the uncontradicted assumption that mx.gnus.org was
the first hop, and hence the proper place to apply conformance constraints.
German-language newsgroups are a nice proof that guess-work does not
quite work, postings are sprinkled with undecodable characters.
If the originator extends an existing format (8-bit national characters
in the originally 7bit medium) and that extension is standardized, it
must be properly marked. You send 8bit, you declare 8bit. Period.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
next prev parent reply other threads:[~2004-05-10 14:30 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
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 [this message]
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=m3wu3ks6b9.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).