Mime Validator?
sergey.rozhenoko
I beleive the mime message is broken/damaged, but haven't been able to
find a mime validator anywhere, so I'm not really sure if it's bad
data or bad code.
I'm looking for something similar to validator.w3.org, only for mime.
Anybody have any suggestions?
Thanks!
Jorgen Grahn
> I've been receiving mime messages that break (crash) horde/imp.
>
> I beleive the mime message is broken/damaged, but haven't been able to
> find a mime validator anywhere, so I'm not really sure if it's bad
> data or bad code.
It's bad code. A server should never crash on bad input.
> I'm looking for something similar to validator.w3.org, only for mime.
>
> Anybody have any suggestions?
Sorry, no -- although you could try other mail readers like Mutt.
But be sure to feed that bad message to the horde/imp developers. They
should be very responsive, since as you describe it, it is a security
bug (denial of service, or worse).
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
sergey.rozhenoko
That's why I was looking for a validator. They don't seem to have a
lot of free time and I don't want to drop a "something might be
broken" report on them without knowing more about it.
I run horde/imp and have users with huge mailboxes. Everything has
been flawless for a very long time, until a user received a couple of
email invoices sent by turbotax.com. This crashed something stone-cold-
dead (not sure if it's imp or apache, although apache is pretty
robust).
I was looking for a way to validate the mime message and find what the
problem is so I can report it to both the imp developer(s) and
turbotax, although from the way things look, I might have to do it by
hand (not my first choice).
sergey.rozhenoko
wrote:
OK, just so this doesn't become one of those "where can I find 'X'"
posts that never have a solution, I did find a MIME validator at :
http://tools.ietf.org/tools/msglint/msglint
It works nicely, however there's apparently nothing badly broken with
the message, so it means that it's a bug in horde/imp/php/apache/etc..
I'll have to crank up debugging and see what's getting killed.
Catch you later.
Jorgen Grahn
> On Apr 14, 8:58 am, "sergey.rozhenoko" <sergey.rozhen...@gmail.com>
> wrote:
>> On Apr 14, 4:29 am, Jorgen Grahn <grahn+n...@snipabacken.se> wrote:
Ah, good.
> It works nicely, however there's apparently nothing badly broken with
> the message, so it means that it's a bug in horde/imp/php/apache/etc..
> I'll have to crank up debugging and see what's getting killed.
Once again: if horde/imp/whatever crashes on a message, that's a
high-priority bug. They must survive *anything* the internet may
throw at them.