|Subject:||Re: "uneven size in DecodeToStream"|
|Posted by:||Remy Lebeau (TeamB) (firstname.lastname@example.org)|
|Date:||Tue, 10 Feb 2004|
"Chris Lupton" <chr…@lupton3.freeserve.co.uk> wrote in message
> Is there a way of identifying this type of message
> before it raises the error?
You could attach a TIdLog component (TIdLogEvent or TIdLogFile) to the
TIdPop3 so that you can save the original message data that is transferred
over the socket before it is parsed by TIdMessage. Then you can show it to
Indy's developers so they can track down the problem (unless you want to try
your hand at it yourself).
"uneven size in DecodeToStream" posted by Chris Lupton on Tue, 10 Feb 2004