Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Cc: <ding@gnus.org>
Subject: Re: No newline at the end of the article with broken MIME message
Date: Wed, 14 Jun 2006 12:45:57 +0200	[thread overview]
Message-ID: <v9k67knhga.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mzmggxdpp.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 14 Jun 2006 18:56:34 +0900")

On Wed, Jun 14 2006, Katsumi Yamaoka wrote:

> I found the MIME messages[1] in the emacs-devel list that seem
> to have been broken.  Because there is no empty line between the
> contents of the last part and the last boundary delimiter line
> in those messages, Gnus shows them in the article buffer without
> terminating with a newline.  Although that might be indeed a
> right behavior[2], I've modified `gnus-display-mime' so that it
> might necessarily terminate an article with a newline.
>
> [1]
> <D27FF599-E025-4E3A-88CD-9A1E59890340@alastairs-place.net>
> <11C41C60-9F2B-418C-AD88-B9EA96CAD537@alastairs-place.net>
> <83A6DECE-2D65-4449-95E0-0C40AFFA30A7@alastairs-place.net>
>
> [2]
> RFC2046: 5.1.1. Common Syntax
> [...]
>    NOTE:  The CRLF preceding the boundary delimiter line is conceptually
>    attached to the boundary so that it is possible to have a part that
>    does not end with a CRLF (line  break).  Body parts that must be
>    considered to end with line breaks, therefore, must have two CRLFs
>    preceding the boundary delimiter line, the first of which is part of
>    the preceding body part, and the second of which is part of the
>    encapsulation boundary.

IMHO it would be good to post messages like this[1] to ding as well[2]
because it's by far more convenient to find an article in the archive
of gmane.emacs.gnus.general on Gmane than in gnus.gnus-bug.  WDYT?

Bye, Reiner.

[1] Or e.g. <news:b4mmzck8quc.fsf@jpl.org>

[2] Either only to ding or cc-ing ding.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



       reply	other threads:[~2006-06-14 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b4mzmggxdpp.fsf@jpl.org>
2006-06-14 10:45 ` Reiner Steib [this message]
2006-06-14 11:45   ` Katsumi Yamaoka

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=v9k67knhga.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.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).