Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Fix problem with time parsing
Date: Tue, 10 May 2011 19:47:10 +0100	[thread overview]
Message-ID: <1305053133-sup-4055@whisper> (raw)
In-Reply-To: <1305049400-sup-4316@masanjin.net>

Excerpts from William Morgan's message of Tue May 10 18:45:23 +0100 2011:
> Reformatted excerpts from Hamish's message of 2011-05-02:
> > If a message has a date with month first and day second, then if the
> > day is greater than 12, heliotrope crashes. This patch catches the
> > error, and tries again after swapping the day and month.
> 
> Is this a legitimate email message? Producing rfc2822-compliant date
> headers is one of the few things that everyone seems capable of doing
> besides spambots. I'm tempted to take the Sup approach of forging a date
> header, or giving up on the email, if it's unparseable.

Sadly it was not spam, but an email from staples (UK) about some stuff I
bought from then online. So sup should not barf on it, but forging a
date header would be fine by me. Though "now" might be better than date
zero, which I think is what sup normally does otherwise ...

Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-05-10 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 22:02 Hamish
2011-05-10 17:45 ` William Morgan
2011-05-10 18:47   ` Hamish [this message]
2011-05-11  0:34     ` William Morgan
2011-05-22 22:03       ` Hamish

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=1305053133-sup-4055@whisper \
    --to=dmishd@gmail.com \
    --cc=sup-devel@rubyforge.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