Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Miles Bader <miles@gnu.org>, ding@gnus.org
Subject: Re: mx.gnus.org being very strict
Date: Mon, 3 May 2004 15:25:43 -0400	[thread overview]
Message-ID: <20040503192543.GB21891@fencepost> (raw)
In-Reply-To: <m3ekq12xbn.fsf@merlin.emma.line.org>

On Mon, May 03, 2004 at 08:13:32PM +0200, Matthias Andree wrote:
> > Anyway, you know the old rule: be conservative in what you produce,
> > and liberal in what you accept.  So yeah, it'd be nice if everyone
> > would use lots of headers, but rejecting mail outright because there
> > are no mime-headers on 8-bit mail is a bit overly strict.
> 
> Well, if they are going to emit ("produce" doesn't seem right) the stuff
> they have accepted verbatim, accepting junk means producing junk,
> breaking the "conservative in what you produce" part. Gateways, Relays
> always face this problem. Accept liberally and emit garbage, or accept
> only conforming mail and emit conservatively formatted data.

If you are a gateway, you should probably just be as transparent as you
can...

It's the endpoints that know what's going on; when gateways try to interpret
things, they as often as not just muck things up.

There are cases where you can't be transparent, and have to interpret, of
course, as when you're converting from one form to another.

-Miles
-- 
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.



  reply	other threads:[~2004-05-03 19:25 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 [this message]
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
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=20040503192543.GB21891@fencepost \
    --to=miles@gnu.org \
    --cc=ding@gnus.org \
    /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).