Unfortunately, your patch did not work for me. I found another email which was causing our client to stick.
The good news is, it did have the "Content-Transfer-Encoding: plain" header. I think I will just write a matcher to filter these emails for now. Thanks. Ted On Tuesday 24 May 2005 05:12, Hes Siemelink wrote: > Theodore Watson wrote: > > I am running 2.2.0. I did not find any exceptions in the logs. > > > > Yes, the bug listed does seem to be what I am experiencing, although it > > is not minor from my perspective. > > I don't think that field can be changed by us non-committers :-( > > > Unfortunately, I lost the email it was getting stuck on so I'm not sure > > if it contained "Content-Transfer-Encoding: plain". I will start saving > > them from now on. > > I suspect it is something like that. I can see in the source where the > problem is and I'll attach a proposed diff to the bug report. > > The problem is that the bug is unassigned, so it can take a while before > someone decides to look into it and apply the patch... > > Cheers, > > Hes. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
