Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: Gnus doesn't understand its own message/rfc forwarding
Date: 12 Apr 2000 08:44:05 +0200	[thread overview]
Message-ID: <whln2j7r9m.fsf@viffer.metis.no> (raw)

Version: Gnus v5.8.4 (CVS checkout from march 17), XEmacs 20.4 (linux)

Gnus doesn't quite seem to understand its own message/rfc forwarding
these days.  When I do a C-d, this is what I see:

   [  94: Steinar Bang        ] <* mixed> fest med "baikerscømmet"
       [   2: Steinar Bang        ] <1 text>
       [  81: Steinar Bang        ] <2 rfc822>
           [  72: nobody              ] <2 text>

The rfc822 part looks like this at the start:

From: Steinar Bang <sb@dod.no>
Subject: fest med "baikerscømmet"
To: Bjørn Olav Listog <blistog@c2i.net>, Tore Reimers <treimers@c2i.net>
Date: 12 Apr 2000 08:21:52 +0200
Organization: Denizens of Doom, Norway Chapter

From: Steinar Bang <sb@dod.no>
Subject: innflyttingsfest
To: doders-announcements@math.uio.no
Cc: doders@dod.no
Date: 09 Apr 2000 21:32:36 +0200
Reply-To: sb@dod.no, tlf@dod.no
Organization: Denizens of Doom, Norway Chapter

ie. I don't get to the forwarded message in such a way that I can
reply to it, and as far as I can remember, this used to be possible.

The headers for the message/rfc822 part, looks like this:

Content-Type: message/rfc822; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

(BTW the charset parameter on this MIME type, seems to make problems
for the exchange server)

Does anyone know if this is fixed in the most recent CVS sources?

Thanx!


- Steinar



             reply	other threads:[~2000-04-12  6:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-12  6:44 Steinar Bang [this message]
2000-04-12  9:23 ` Kai Großjohann
2000-04-12  9:32   ` Steinar Bang
2000-04-12 10:04     ` Steinar Bang
2000-04-15  2:34       ` Carey Evans
2000-04-28  3:07     ` Shenghuo ZHU
2000-04-28  9:52       ` Steinar Bang

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=whln2j7r9m.fsf@viffer.metis.no \
    --to=sb@metis.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).