Popman Stalls
Moderator: Christian
Popman Stalls
Sometimes a particular email wll stall popman so that it stops responding, I have to log into my mail account with a different email header checker and delete the message that stalls Popman before I can get past that message with popman.
I will need to have a look into the log file to investigate this issue.
Please verify that you have logging enabled: In the menu choose "Tools" > "Options" and check the option "Enable logging" on the "Logging" tab.
Reproduce the problem and send me the log file "PopManLogFile.log".
Thank you
Please verify that you have logging enabled: In the menu choose "Tools" > "Options" and check the option "Enable logging" on the "Logging" tab.
Reproduce the problem and send me the log file "PopManLogFile.log".
Thank you
Christian Hübner
Mine Stalls as Well.....
I'll send you the log file.... all the ones it stalls on, seem to be empty emails... When I check them through webmail, there's nothing there but the header, don't know whether this has anything to do with it or not.
Re: Mine Stalls as Well.....
Because the program froze, it wiped out the changes I'd made to recording the log file. Will have to remember to send it next time.Kaysea wrote:I'll send you the log file.... all the ones it stalls on, seem to be empty emails... When I check them through webmail, there's nothing there but the header, don't know whether this has anything to do with it or not.
![Surprised :o](./images/smilies/icon_surprised.gif)
I've received your log file and was able to reproduce the problem.
There was a bug in PopMan's message body extraction routine, that caused an infinite loop due to a boundary mishandling under very special conditions (the boundary string was part of the message header).
I will include the fix with the 1.3 Beta 7 release in the next days...
![Smile :)](./images/smilies/icon_smile.gif)
There was a bug in PopMan's message body extraction routine, that caused an infinite loop due to a boundary mishandling under very special conditions (the boundary string was part of the message header).
I will include the fix with the 1.3 Beta 7 release in the next days...
Christian Hübner