It would be wonderful if this problem could be fixed. It now keeps happening to me several times a day and so I think it has to be a little more than an intermittent server problem. Even if the fault is with the server, Spami ought to time things out and simply give up this attempt.

It would be wonderful if this problem could be fixed. It now keeps happening to me several times a day and so I think it has to be a little more than an intermittent server problem. Even if the fault is with the server, Spami ought to time things out and simply give up this attempt.

Have recently run into this issue again and I cannot see any logical explanation for it. Quiter simply, the envelope in the tray keeps running and the only way to recover the situation is to Cancel the connect. Clearly the timeout isn't being activated but could that be because it is a transfer timeout and not an overall timeout? Even if there is a problem with the connection or the remote server it would surely make sense to timeout so that a new attempt is made rather than hanging everything up waiting for manual intervention.

Have recently run into this issue again and I cannot see any logical explanation for it. Quiter simply, the envelope in the tray keeps running and the only way to recover the situation is to Cancel the connect. Clearly the timeout isn't being activated but could that be because it is a transfer timeout and not an overall timeout? Even if there is a problem with the connection or the remote server it would surely make sense to timeout so that a new attempt is made rather than hanging everything up waiting for manual intervention.

thank you for your effort to find and quote the relevant lines from the client.log.

Possibly it's only a temporary problem with the server connection. But the trouble is, that Michel Krämer, the program author of Spamihilator, has not finished the programming of a timeout, as you proposed and as asked another user in the past. When you showed the log, I remembered that somebody else asked about a similar problem formerly, and the diskussion went a similar way: a timeout should solve the hang-up.

Does the timeout in the Spamihilator settings / "connection" solve the hang-up?

Sincerely, Chactory

Hi David,

thank you for your effort to find and quote the relevant lines from the client.log.

Possibly it's only a temporary problem with the server connection. But the trouble is, that Michel Krämer, the program author of Spamihilator, has not finished the programming of a timeout, as you proposed and as asked another user in the past. When you showed the log, I remembered that somebody else asked about a similar problem formerly, and the diskussion went a similar way: a timeout should solve the hang-up.

Does the timeout in the Spamihilator settings / "connection" solve the hang-up?

As you can see the password interaction didn't complete, hence the hangup. Isn't there a mechanism which should time this out?

To complete the information, the SSL icon is flashing during this period. I'm running spami 1.6.0 32-bit on a 64-bit version of Windows 10 Technical Preview but I've also had the same issue on a Windows 7 machine. The reason I run the 32-bit version is that I had an issue with the 64-bit version of spami (VB Runtime error - Win7 64 bit posted 16 August 2012) and found that the same problems didn't occur with the 32-bit and so I've stuck with the 32-bit version ever since.

David

Hi Chactory,

Well, the problem has happened again and it looks as though the problem is with completing the connection to the server. The log file has the following in it:

As you can see the password interaction didn't complete, hence the hangup. Isn't there a mechanism which should time this out?

To complete the information, the SSL icon is flashing during this period. I'm running spami 1.6.0 32-bit on a 64-bit version of Windows 10 Technical Preview but I've also had the same issue on a Windows 7 machine. The reason I run the 32-bit version is that I had an issue with the 64-bit version of spami (VB Runtime error - Win7 64 bit posted 16 August 2012) and found that the same problems didn't occur with the 32-bit and so I've stuck with the 32-bit version ever since.

Thanks for replying. Silly of me to not think of looking in the log files but I didn't and as I am not entirely sure when the problem occurred I can't be sure of finding the correct information. I will try to remember to look the next time I see this happening but it might be some time as this is definitely and intermittent problem.

David

Hi Chactory,

Thanks for replying. Silly of me to not think of looking in the log files but I didn't and as I am not entirely sure when the problem occurred I can't be sure of finding the correct information. I will try to remember to look the next time I see this happening but it might be some time as this is definitely and intermittent problem.

I've thought over this problem for a while, but I'm not finding a reason ... Could it be a server problem? Can you find any interesting information in the log files (client.log, server.log, they are in the folder C:\Users\Chactory\AppData\Roaming\Spamihilator)?

Chactory

Hi px03afk!

I've thought over this problem for a while, but I'm not finding a reason ... Could it be a server problem? Can you find any interesting information in the log files (client.log, server.log, they are in the folder C:\Users\Chactory\AppData\Roaming\Spamihilator)?

Sorry if this duplicates a known problem but I can't find it in the forum. Every so often I see the envelope in the tray running continuously for a lot longer than makes any sense. I've left it alone for minutes and still it continues running. I can click on it and bring up the box and cancel and then everything settles down again. It's not a major issue but I was wondering how I might be able to determine why it's happening.

Sorry if this duplicates a known problem but I can't find it in the forum. Every so often I see the envelope in the tray running continuously for a lot longer than makes any sense. I've left it alone for minutes and still it continues running. I can click on it and bring up the box and cancel and then everything settles down again. It's not a major issue but I was wondering how I might be able to determine why it's happening.