Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: A (very short) independent opinion of Gnus MIME
Date: 05 Jul 1999 20:15:21 +0200	[thread overview]
Message-ID: <87r9mnotdy.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "05 Jul 1999 14:20:06 -0400"

François Pinard <pinard@iro.umontreal.ca> writes:

> The nice thing is the reply from the list maintainer:
> 
> > The problem is that my current software isn't smart enough to tell
> > modestly messy MIME like yours from really awful mime like HTML and base64.
> 
> I much like this "modestly messy" to quality Gnus MIME works.  Maybe
> Lars could start use it as a kind of trademark in Gnus descriptions? 
> :-)

Let me guess: the software in use was Listar?  Today I got this mail
from a friend of mine who happens to be a Listar groupie:

    Bok,

    Cuj, ne kuzim se do kraja u MIME and stuff...  Uglavnom, ovo je bilo u 
    changelogu od listara.  El to u redu ako je i tako, ili to gnusi krivo 
    rade?

      -- Rewrote another portion of the multipart handler to allow for the
         fact that Gnus allows you to have the first MIME attachment have
         no content-type and expects you to assume it's text/plain.  Fooie!

(The Croatian part says: "Hi!  I am not really into MIME and stuff...
Anyway, this was in listar's changelog.  Is that OK, or is Gnus doing
something wrong?")

Someone hasn't read rfc2046!


  reply	other threads:[~1999-07-05 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-05 18:20 François Pinard
1999-07-05 18:15 ` Hrvoje Niksic [this message]
1999-07-05 22:14   ` Michael Harnois
1999-07-06  4:26     ` Hrvoje Niksic
1999-07-06  4:58       ` Michael Harnois
1999-07-06 15:15         ` Hrvoje Niksic

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=87r9mnotdy.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).