From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@ifi.uio.no
Subject: Re: Bug sending messages unplugged
Date: 23 Nov 1998 16:05:06 -0800 [thread overview]
Message-ID: <x7k90mj6q5.fsf@des.castles.com> (raw)
In-Reply-To: Markus Dickebohm's message of "24 Nov 1998 00:08:47 +0100"
>>>>> On 24 Nov 1998 00:08:47 +0100, Markus Dickebohm <m.dickebohm@Uni-Koeln.DE> said:
Markus> My tests revealed another bug in respect to news postings: two
Markus> Content-Type headers are generated when sending queued
Markus> postings and my articles were rejected by the newsserver.
I saw this when re-posting the articles that died from the previous
error. Mainly because I was submitting them with C-c C-c from the
mail buffer they died in, which caused the headers to get inserted a
second time. Gnus should, though, remove the old headers before
recreating new ones.
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-11-24 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 19:44 Markus Dickebohm
1998-11-23 19:58 ` Colin Rafferty
1998-11-23 21:53 ` Wes Hardaker
1998-11-24 10:03 ` Jan Vroonhof
1998-11-25 22:12 ` Wes Hardaker
1998-11-23 23:08 ` Markus Dickebohm
1998-11-24 0:05 ` Wes Hardaker [this message]
1998-11-24 10:11 ` 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=x7k90mj6q5.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
--cc=ding@ifi.uio.no \
/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).