Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: forwarding as text rather than MIME?
Date: 26 Feb 1999 12:48:19 +0100	[thread overview]
Message-ID: <87ww15fksc.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "26 Feb 1999 08:14:18 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> 1) Forwarding things as message/rfc822 allows automatic extraction by
>    MIME-compliant news/mail readers.

...and many news readers are not MIME compliant, Gnus <= 5.8.x
included.

> 2) A typical complaint when forwarding using the old scheme was that
>    not all headers were included, which meant that when people
>    forwarded things to complain about spam, none of the important
>    headers (Path/Received/etc) were included.
> 
> 3) A typical complaint when forwarding message/rfc822 messages is that 
>    all the headers are included, which means that when people forward
>    mail to each other, they get a bunch of useless headers
>    (Path/Received/etc) they have to scroll through (if their
>    news/maill reader don't handle that).

These two complaints were easily solved by `S o p' doing "nice"
forwards and `C-u S o p' doing "complete" forwards.  This worked
nicely.

> To sum these considerations up, I think that message/rfc822 is the
> right thing to do, and perhaps more importantly, it's The Thing Of
> The Future.  And I think that perhaps by pushing this, we might make
> the future happen a bit sooner.

Uh-oh.


  reply	other threads:[~1999-02-26 11:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-15 18:20 Bill White
1999-02-15 20:36 ` Hans de Graaff
1999-02-19 14:23   ` Lars Magne Ingebrigtsen
1999-02-20  9:44     ` Hans de Graaff
1999-02-21  7:21       ` Chris Tessone
1999-02-21 10:38         ` Lars Magne Ingebrigtsen
1999-02-21 19:37           ` Chris Tessone
1999-02-21 19:40             ` Hrvoje Niksic
1999-02-22 12:54               ` Toni Drabik
1999-02-22 17:43                 ` Hrvoje Niksic
1999-02-22 17:58                   ` Robert Bihlmeyer
1999-02-22 18:26                     ` Hrvoje Niksic
1999-02-23 18:32                       ` Per Abrahamsen
1999-02-24 15:52                         ` Robert Bihlmeyer
1999-02-24 16:17                           ` Hrvoje Niksic
1999-02-24 16:30                             ` Chris Tessone
1999-02-24 16:43                               ` Alexandre Oliva
1999-02-24 16:52                                 ` Chris Tessone
1999-02-24 17:01                                 ` Kai.Grossjohann
1999-02-24 17:10                               ` Robert Bihlmeyer
     [not found]                           ` <m3678rtieo.fsf@serpent.laymusic.>
1999-02-25 17:17                             ` Kai.Grossjohann
1999-02-25 10:39                         ` Russ Allbery
1999-02-26  7:14                   ` Lars Magne Ingebrigtsen
1999-02-26 11:48                     ` Hrvoje Niksic [this message]
1999-02-26 12:30                       ` Per Abrahamsen
1999-02-26 14:45                       ` Lars Magne Ingebrigtsen
1999-02-27 12:38                         ` Russ Allbery
1999-02-27 13:15                           ` Lars Magne Ingebrigtsen
1999-02-27 14:13                           ` Hrvoje Niksic
1999-02-28 19:21                           ` Per Abrahamsen
1999-02-22 22:13               ` Aaron M. Ucko
1999-04-03  7:28       ` Hans de Graaff

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=87ww15fksc.fsf@pc-hrvoje.srce.hr \
    --to=hniksic@srce.hr \
    /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).