Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] Patch for message-id problem
Date: Fri, 20 Mar 2009 10:11:37 -0700	[thread overview]
Message-ID: <a412e2a70903201011p5ff990ccn6e74fad3cee60648@mail.gmail.com> (raw)

Here's a patch for the message-id problem I mentioned
earlier, where the header line was split into two lines:

Message-ID:
 <D3C12B2AD838B44DA9D6B2CA334246D011E72A73A4 at PA-EXMBX04.widget.com>

I've also seen other header lines that were split in this way,
so this patch works for them too.

I've added a somewhat large test case to the unit test
that is an exact copy of a message that was causing
me problems, but with the company name changed to protect
the innocent.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: msgid.patch
Type: application/octet-stream
Size: 4830 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090320/9debd13d/attachment.obj>


             reply	other threads:[~2009-03-20 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 17:11 Mark Alexander [this message]
2009-03-22 16:59 ` William Morgan

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=a412e2a70903201011p5ff990ccn6e74fad3cee60648@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