Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] possible mbox "initial From" fix
Date: Mon, 04 May 2009 07:35:20 -0700	[thread overview]
Message-ID: <1241447393-sup-7632@entry> (raw)
In-Reply-To: <6bb609560904291751n3cc62f46g6a4edcba1f97d6f7@mail.gmail.com>

Reformatted excerpts from Bart Schaefer's message of 2009-04-29:
> We found that in most cases this failed at (1) or succeeded very
> quickly at (6a).  Only obscure cases proceed to (7), but if you're
> dealing with anything like old USENET news archives or folders written
> by '80s-era mail clients you need either step (4) or step (7) to get
> past the cruft.
> 
> Note that the key is finding "From ... DATE" rather than "From ADDRESS
> ..." if you really want to distinguish message separators from stuff
> people type in a message body.  I'm not sure you can do this with a
> regular expression.

Thanks! This is really helpful. I am a little worried about the current
fix, since there's no real requirement that an email address have an @
sign in it for local users, and that will result in false negatives,
and there's a non-trivial potential for false positives.

If we went this route (which wouldn't require a big changeset), I may
punt on parsing the date myself and just rely on Time.parse. Speed
shouldn't really be affected (except in weird pathological cases) since
the date parsing will be a second step. I like it.
-- 
William <wmorgan-sup at masanjin.net>


      reply	other threads:[~2009-05-04 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 18:02 William Morgan
2009-04-30  0:51 ` Bart Schaefer
2009-05-04 14:35   ` William Morgan [this message]

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=1241447393-sup-7632@entry \
    --to=wmorgan-sup@masanjin.net \
    /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