Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: pgnus 0.25 problem
Date: 11 Sep 1998 15:03:39 +0200	[thread overview]
Message-ID: <kigemtiztqs.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "11 Sep 1998 11:13:33 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Jakub.Martynski@spam.is.lame.org (Jakub Martyński) writes:
> 
> > I found problem in Pgnus 0.25:
> > 
> > Signaling: (error "Invalid header: text/plain;")
> >   signal(error ("Invalid header: text/plain;"))
> 
> Which brings us to a general question -- what is Gnus supposed to do
> with broken headers?  Signalling errors is much too drastic, but
> should it just ignore them?  Or try to do something with them?  And
> if so, what?

"Be conservative in what you send; be liberal with what you receive."

Applied to Gnus, this means that it should try to be as lax as
possible when parsing the headers (in the above case, it should ignore 
the semicolon and perhaps assume the charset is latin1), and ignore
them when they're totally bogus.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Union break!


  reply	other threads:[~1998-09-11 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-11  8:18 Jakub Martyński
1998-09-11  9:13 ` Lars Magne Ingebrigtsen
1998-09-11 13:03   ` Hrvoje Niksic [this message]
1998-09-11 14:19     ` Lars Magne Ingebrigtsen
1998-09-11  7:33       ` François Pinard
1998-09-11 15:17       ` Hrvoje Niksic
1998-09-11 14:20     ` Kai Grossjohann
1998-09-11 15:14       ` Hrvoje Niksic
1998-09-11 20:59         ` Kai Grossjohann
1998-09-12  6:21           ` 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=kigemtiztqs.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).