From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mbox date fail
Date: Sun, 01 Nov 2009 10:46:33 -0800 [thread overview]
Message-ID: <1257101109-sup-4117@masanjin.net> (raw)
In-Reply-To: <2aeb4e149305569502f106c7e54ae107@localhost>
Reformatted excerpts from Mike Kelly's message of 2009-10-23:
> Is there much of anything that I can do to mitigate this problem,
> aside from manually altering every offending message?
I've fixed this in master. Can you try again, please?
> It seems like the messages' Content-Length header should be used to
> skip past the body and ignore the offending Froms?
This is an option, but I'm avoiding it, because Content-Length is not
guaranteed to be there, and not guaranteed to be correct.
> Or, at least, if that sort of
> ArgumentError is thrown, maybe it should be caught and handled better?
Yep, that's what I've done. I couldn't get my local system to throw
ArgumentError, even with your example, but if it's possible, it's
possible, and should be caught.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-01 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 21:13 Mike Kelly
2009-11-01 18:46 ` William Morgan [this message]
2009-11-01 23:30 ` Mike Kelly
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=1257101109-sup-4117@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@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