Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: charset problems with gnus-delay (was: Drafts feature-request/bug.)
Date: Thu, 12 Sep 2002 11:50:56 +0200	[thread overview]
Message-ID: <vaflm67fse7.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <v9ofb4icwv.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 11 Sep 2002 20:44:48 +0200")

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

> On Wed, Sep 11 2002, Reiner Steib wrote:
> [a b0rked message]
>
> I did some experiments with gnus-delay before sending this message. As
> you can see it lead to a posting without proper MIME-headers:

I see the same problem.  After the delayed article arrived, I saw the
following (received headers snipped):

/----
| X-From-Line: grossjoh@lothlorien.cs.uni-dortmund.de Thu Sep 12 11:18:41 2002
| To: Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
| Subject: testing delay
| From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai
|  =?iso-8859-15?q?Gro=DFjohann?=)
| Date: Thu, 12 Sep 2002 11:18:33 +0200
| Message-ID: <vafadmnh8gm.fsf@lucy.cs.uni-dortmund.de>
| User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50
|  (i686-pc-linux-gnu)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=utf-8
| Content-Transfer-Encoding: quoted-printable
| X-Content-Length: 79
| Lines: 6
| Xref: lucy.cs.uni-dortmund.de news.emacs.tramp:10755
| 
| Sch=C2=81=F6ner Test.
| 
| kai
| --=20
| ~/.signature is: umop 3p!sdn    (Frank Nobis)
| 
\----

So the utf-8 charset was used where it wasn't necessary, and the \201
appeared.

Does anyone have an idea what happened?  gnus-delay uses the
following sequence of statements to save the article:

  (set-buffer-modified-p t)
  (nndraft-request-create-group gnus-delay-group)
  (message-disassociate-draft)
  (nndraft-request-associate-buffer gnus-delay-group)
  (save-buffer 0)
  (kill-buffer (current-buffer))
  (message-do-actions message-postpone-actions))

And it uses the (gnus-draft-send article group) to send them.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)



      parent reply	other threads:[~2002-09-12  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 23:19 Drafts feature-request/bug Scott A Crosby
2002-09-11 10:06 ` Kai Großjohann
2002-09-11 10:19   ` Scott A Crosby
2002-09-11 11:09     ` Kai Großjohann
2002-09-11 16:19   ` Reiner Steib
2002-09-11 16:35     ` Kai Großjohann
2002-09-11 18:44     ` charset problems with gnus-delay (was: Drafts feature-request/bug.) Reiner Steib
2002-09-11 19:41       ` charset problems with gnus-delay Reiner Steib
2002-09-12  9:50       ` Kai Großjohann [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=vaflm67fse7.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).