I've been digging around in rfcmsg.c, and see where the message is failing, but have not been able to understand why the message is failing.
I realized that we don't have a dump utility! I think I may write one to quickly dump a specific message out to mbox format and post the failing messages to the list as attachments so that others can insert them and try to reproduce the errors. Aaron Ilja Booij <[EMAIL PROTECTED]> said: > > Aaron, > > have you been able to find any clue to the cause of the parser problem? > It seems like quite a show stopper, so I'd like to resolve it as quickly > (and cleanly) as possible > > Ilja > > > Ilja Booij wrote: > > Aaron Stone wrote: > > > >> This is a message from the sieve-php mailing list, which apparently > >> DBMail did > >> not like very much... I'm using LMTP delivery. > >> > >> My hunch is that the current mime code is choking because of the \n or > >> \r\n > >> lines breaks no longer being guaranteed. > > > > > > Can you send a log trace to narrow down the search? > > > > Ilja > > > > _______________________________________________ > > Dbmail-dev mailing list > > [email protected] > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
