Stuck at "Evaluating Message"

[alanrwood]

Hi

The problem has not re-occurred since I switched off First Alert so it pretty much confirms your diagnosis.

Rgds Alan

[rusticdog]

OK great. We've got a new version coming this week that should hopefully address this.

[nobodyspecial]

Hi all

I had the same problem with MWP stuck on evaluation.

In my case the problem is my Modem's firewall...

Sun, 2010-07-25 10:07:00 - TCP Packet - Source:192.168.0.2,1427 Destination:209.213.221.162,4088 - [Any(ALL) rule match]
Sun, 2010-07-25 10:07:01 - TCP Packet - Source:192.168.0.2,1448 Destination:209.213.221.161,4051 - [Any(ALL) rule match]
Sun, 2010-07-25 10:07:03 - TCP Packet - Source:192.168.0.2,1427 Destination:209.213.221.162,4088 - [Any(ALL) rule match]
Sun, 2010-07-25 10:07:04 - TCP Packet - Source:192.168.0.2,1448 Destination:209.213.221.161,4051 - [Any(ALL) rule match]

the above are ports being blocked when MWP is trying to connect to FirstAlert!

Even if I open ports 4088 and 4051 that does not solve the issue - I have to completely open the firewall to get MWP to connect to FirstAlert! - my logs don't give me anymore clues as to which other ports are being used.

I don't want my firewall fully open so I disable FirstAlert! and MWP works OK.

It would be great if Firetrust could give a definitive list of ports that must be open in order to get MWP to reliably connect to FirstAlert!. I searched Firetrust and Googled in vain to find the port list. Perhaps it's out there somewhere, but I couldn't find it.

[rusticdog]

Those are the only two non standard ports, 4088 is Registration, 4051 is FirstAlert.

The issue however is more complicated than just FirstAlert connectivity, it relates to the internal queuing MailWasher has. For some reason it seems as though MailWasher thinks there are emails in a queue waiting to process against FirstAlert however the queues are empty, so MailWasher just sits there waiting....

[nobodyspecial]

Hmm, interesting.

But how does opening all ports solve the problem? - as everything definitely works OK "when your shields are down" ;-)

[rusticdog]

We've been seeing the issues on machines where the communications appears all fine, so I expect just coincidental.

[mindmagic]

Disabling First Alert solved this problem for me too.

[rusticdog]

<removed, while we work on fixing a problem>

[anniebrion]

WARNING V1.0.5 might be broken!!!

RD Please see thread in Beta Forum!

[alanrwood]

Hi

Just leaving home for a couple of weeks so my internet access is via Vodafone and only GPRS at that (5-6KB/s) so I will have to leave this till I get back by which time it may no longer be a Beta anyway.

[michaelkenward]

WARNING V1.0.5 might be broken!!!

RD Please see thread in Beta Forum!

For those of us without access to the beta forum, can we have a bit more than this?

After all, the beta link is here.

As the person who started this one running, I am interested in the resolution. But with conflicting advice like this, I don't know if it will break other things if I install the new version.

[rusticdog]

Works for us, don't know what else to say until programmer takes a look. If it crashes on startup after install you'll know it's not working and can go back to 1.0.4

[rusticdog]

Will take it down, while we fix whatever it is causing this :/

[michaelkenward]

Works for us, don't know what else to say until programmer takes a look. If it crashes on startup after install you'll know it's not working and can go back to 1.0.4

Thanks. Installed and started just fine.

I have turned on FirstAlert to see if that still hangs.

Interestingly, the installation does not, unlike some other installers, read and respect my previous settings. (It wanted to plonk itself in the startup folder for example, which is not how I work.)

Sadly, my installation still starts with no status line visible. But I guess I will have to live with that small eccentricity.

Hold on, one message shows:

The email was empty
account = Acct-1621182401
uid = 52d7b7773a6a83c112e3258374150952
file name = C:\Users\MK\AppData\Roaming\Firetrust\MailWasher\cache\crypto\52d7b7773a6a83c112e3258374150952Acct-1621182401.0001

The email in question is far from empty.

Screens and logs available if it helps. But maybe best to wait to see if it happens again.

[anniebrion]

Have you tried restarting MWP as I got it to run 2 times out of 4 installs but a restart made it fail