Hi Rob, On Mon, 06 Sep 2010, Rob Browning wrote: > Jameson Rollins <jrollins@finestructure.net> writes: > > > Hey, Rob. I've never seen this error before. I wonder if these > > messages have some really long header names? If it's not too onerous, > > can you find the messages where this occurred? There's a verbose > > option, that might be useful. > > > > jamie. > > OK, it looks like this is the first message that caused the exception: > ... > References: <!~!UENERkVCMDkAAQACAGsAAAAAAAAAOKG7EAXlEBqhuwgAKypWwgAAbXNwc3QuZGxsAAAAAABOSVRB+b+4AQCqADfZbgAAAEQ6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcU3RlcGhlblxTYWZlLU1haWxcbXlvd24ucHN0ABgAAAAAAAAAKmWF8xrwOEqmERpDM8LmDaKAAAAAAAAAGAAAAAAAAAAqZYXzGvA4SqYRGkMzwuYNwoAAABAAAACBsx7lCzP5SIlwp4aMmuqaMgAAAFJFOiAtLXBhcnRpYWxsLWRpciBub3QgYmVoYXZpbmcgbGlrZSBpdCBvdWdodCB0b28A@Virgin.Net> please try the version from git. I do not have the problem you report with this message. It seems that it was fixed after 0.3.1 release in commit 7b78eb4af6e87532795d09bd82152002ab4a74b1 Author: Carl Worth <cworth@cworth.org> Date: Fri Jun 4 12:39:36 2010 -0700 Add support (and tests) for messages with really long message IDs. -Michal