Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] preparing for 0.7
Date: Wed, 18 Mar 2009 14:11:05 -0700	[thread overview]
Message-ID: <a412e2a70903181411s388d2147l136b68f0a1fe7bd2@mail.gmail.com> (raw)
In-Reply-To: <1237383823-sup-8242@entry>

On Wed, Mar 18, 2009 at 6:49 AM, William Morgan
<wmorgan-sup at masanjin.net> wrote:
> I'm definitely interested in whether it holds up.

It's holding up very well; no crashes after two days.  This is wonderful!

I have encountered a few odd minor issues.  One is that
it seems not to recognize Message-ID headers that are
split over two lines.  For example, here's one that caused
it to generate a faked-up ID:

Message-ID:
 <72E99544C4530E4F92DCC03303F8CF820145EDC05D at PA-EXMBX01.widget.com>

There's a newline after the colon, and the message ID follows
on the next line, indented with one space.  I believe this one
was generated by Outlook, but I've also seen Alpine do this.

This is messing up threading.  Without delving into
the source, I am guessing this an rmail bug, not a sup bug.


  parent reply	other threads:[~2009-03-18 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 17:27 William Morgan
2009-03-17 18:29 ` Mark Alexander
2009-03-18 13:49   ` William Morgan
2009-03-18 15:39     ` Lee Hinman
2009-03-19 17:02       ` William Morgan
2009-03-18 21:11     ` Mark Alexander [this message]
2009-03-19 19:18     ` Mark Alexander
2009-03-19 19:25       ` William Morgan
2009-03-19 20:41         ` Mark Alexander
2009-04-15 17:29           ` [sup-talk] Lost Maildir Messages Iain

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=a412e2a70903181411s388d2147l136b68f0a1fe7bd2@mail.gmail.com \
    --to=marka@pobox.com \
    /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