From: "David Kågedal" <davidk@lysator.liu.se>
Subject: Re: bug: sgnus inserts blank lines in headers
Date: 18 Apr 1996 17:44:30 +0200 [thread overview]
Message-ID: <jp91ftzgdd.fsf@tindra.lysator.liu.se> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 18 Apr 1996 13:35:48 +0000
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Hallvard B Furuseth <hallvard@solva.ifi.uio.no> writes:
>
> > Here is an article I just posted:
> >
> > > From: Hallvard B Furuseth <hallvard@solva.ifi.uio.no>
> > > Subject: test igjen
> > > Newsgroups: uio.test
> > > Date: 04 Apr 1996 01:45:25 +0200
> > > Organization: Dept. of Informatics, University of Oslo, Norway
> > > Path: ifi.uio.no!usenet
> > > Lines: 5
> > > Message-ID: <ydbwx3w3m96.fsf@solva.ifi.uio.no>
> > > NNTP-Posting-Host: solva.ifi.uio.no
> > >
> > > Lines: 2
> > > X-Newsreader: September Gnus v0.63/Emacs 19.30
> > >
> > > a
>
> It seems like message.el sometimes generate headers after the
> `mail-header-separator' line. I have been unable to reproduce this
> bug. Has anybody else seen similar behavior?
Sgnus 0.63 doesn't use message.el, does it?
I have seen the behaviour quite a lot. But not that it inserts headers
after the separator, but that it inserts an empty line before it. The
problem I hav seen are really long Message-IDs in the In-reply-to:
line, which were wrapped like this:
In-reply-to:
<REALLY_LONG_MESSAGE_ID@FOOBAR>
----- Separator line here --------
This made sendmail.el put many of the headers in the body instead.
I never bothered to track it down or report it, though.
--
David Kågedal Lysator Academic Computer Society davidk@lysator.liu.se
http://www.lysator.liu.se/~davidk/ +46-13 17 65 89
prev parent reply other threads:[~1996-04-18 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-03 23:58 Hallvard B Furuseth
1996-04-18 13:35 ` Lars Magne Ingebrigtsen
1996-04-18 15:44 ` David Kågedal [this message]
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=jp91ftzgdd.fsf@tindra.lysator.liu.se \
--to=davidk@lysator.liu.se \
/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).