> That is how Indy is designed to work. It uses blocking sockets and blocking
> operations. To prevent the freeze, you can either drop a TIdAntiFreeze
> component onto the form, or else move the Connect() to a separate worker
> thread. Otherwise, use a different component library, such as ICS or
> Synapse, that supports asynchronous operations.
Thank you Remy for your assistance.
Actually, I have decided to give Indy a try after the synapse TPOP3Send, because as it also uses a blocking soket and don't have anything like OnWork.
For now i have decided a separate thread workaround and it seems fine.
In other posts you have suggested to use TIdConnectionIntercept or TIdLogEvent to gather the progress information. Could you provide more information or code example on using this components. The purpose is to feed the user with information on the progress of body retrieval.
