Gnus development mailing list
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Gnus <ding@gnus.org>, emacs-devel@gnu.org
Subject: Re: gnus inserts headers in body
Date: Mon, 27 Aug 2007 07:11:35 +0200	[thread overview]
Message-ID: <85y7fxa7eg.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uk3ay5rcd8.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun\, 26 Aug 2007 21\:32\:19 -0400")

Glenn Morris <rgm@gnu.org> writes:

> Reiner Steib wrote:
>
>> No, I've never seen this happen for me (and I don't recall reports
>> about it neither) and I edit and send drafts quite often.  Ideas
>> anyone?
>
> It has happened to me several times.
>
>>> I've always suspected it may be some Gnus/VM interaction with
>>> different settings for some message header separator...
>>
>> Are you saying that you use VM?  I don't know how VM may interact here
>> as I don't know it.
>
> Yes, I use VM as well as Gnus. I have the impression the problem
> occurs when I: start Gnus, compose a message, save as draft, start VM,
> do some stuff, return to Gnus, edit draft, send.
>
> I realize it was a vague complaint, I'll try to track down more
> details when I can. It may well be my fault somehow.

Perhaps related:  News servers have occasionally rejected articles of
mine because they consisted of only headers (or something like that).
Inserting a blank line after the "--text follows this line--" line has
solved this problem when it occured.

The strange thing is that this blank line is not always needed.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-08-27  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fc339e4a0708182017g62f24f66q5688ae9466c6069a@mail.gmail.com>
     [not found] ` <200708211523.l7LFNnVl000876@oogie-boogie.ics.uci.edu>
     [not found]   ` <buo3aycknp8.fsf@dhapc248.dev.necel.com>
     [not found]     ` <200708220820.l7M8KbIt026014@oogie-boogie.ics.uci.edu>
     [not found]       ` <fc339e4a0708220237v3b90ec6fwde90eba1ca936e91@mail.gmail.com>
     [not found]         ` <fc339e4a0708220455r4ee90438waf1416c505f294a4@mail.gmail.com>
     [not found]           ` <jwvir77io0q.fsf-monnier+emacs@gnu.org>
     [not found]             ` <87lkc3qe2z.fsf@jurta.org>
     [not found]               ` <E1IOJlV-0003k8-PZ@fencepost.gnu.org>
     [not found]                 ` <m3absh4azj.fsf@kurono.home>
     [not found]                   ` <m2hcmpcob9.fsf@cam.ac.uk>
     [not found]                     ` <m36435484z.fsf@kurono.home>
     [not found]                       ` <E1IOmw2-0001pd-Tm@fencepost.gnu.org>
     [not found]                         ` <m3mywf3hqi.fsf@kurono.home>
     [not found]                           ` <E1IP7Xp-0006V6-6P@fencepost.gnu.org>
     [not found]                             ` <7s1wdr2g6g.fsf_-_@fencepost.gnu.org>
2007-08-26  7:45                               ` Reiner Steib
2007-08-27  1:32                                 ` Glenn Morris
2007-08-27  5:11                                   ` David Kastrup [this message]
2007-09-17  1:16                                   ` Glenn Morris

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=85y7fxa7eg.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.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).