Mailwasher Pro 2010 problem with bellsouth/att POP accounts

[claykin]

I can see where in the logs things went south, no idea why though. Programmers in bed

Basically a command failed around 00:30, put things in a spaz, the UI recovered and kept firing commands to the engine, which hadn't recovered....

Things I would personally do at this point is enable PIPELINING back, purely for speed and I don't think that was the problem to begin with. You also want to consider how important DNSBLs (origin of spam) are to you, if they aren't I would disable, again purely for speed.

We need to look at what command failed, why, and why the engine didn't recover.....

I turned on Pipelining for all POP accounts. Believe I previously turned it off when trying to troubleshoot what you call the Base64 issue.

I have the Spamcop and Spamhaus DNSBL lists enabled. One thing I was wondering, seriously, is that with MWP2010 so far the thing finds nearly no spam that it offers to auto delete. I didn't want to mix the issues and figured maybe I needed to look further into things I turned off while trying to fix the Base64 issue. Its weird though that when I check an account that I know has a few common spam mails, they aren't auto tagged for delete. Hmmmm.

[rusticdog]

By chance did you clear the grid around 00:30 while MW was downloading ?


It also depends what value you have AutoDelete enabled for, the different Spam Tools assign scores to emails, and AutoDelete runs off the total.

[claykin]

By chance did you clear the grid around 00:30 while MW was downloading ?


It also depends what value you have AutoDelete enabled for, the different Spam Tools assign scores to emails, and AutoDelete runs off the total.

Did not clear grid @ 00:30AM. I quit working on the PC just before midnight I recall.

I'm not using Autodelete (i assume you mean autodelete checkbox in the SPAM TOOLS > SPAM RATINGS). I like to look through the list of recommended deletes and then click WASH on my own. Am I doing this wrong??

[rusticdog]

No that's fine, just when you used the wording I thought you had enabled the specific AutoDelete feature.


Bayesian takes time, though you have a crap load of emails too, so it should get there very quickly. What I would personally do is process one account at a time, each time you Wash Mail, any emails you train are added to the corpus and the Bayesian is rebuilt. In theory looking at that email volume you should only need to do that once....

If you click View >> Sidebar >> you can get a summary, basically anything -50 or greater is spam, +50 or more is good.

Untitled.png (39.04 KiB) Viewed 12286 times

[stan_qaz]

I find having the total and Bayesian scores in the grid is handy, faster than having to select each message and look to the sidebar.

columns-1.png (7.66 KiB) Viewed 12283 times

You can pick up a bit of speed by bumping the source of spam and first alert caches up to a few days. I got a nice speed improvement by selecting a faster DNS server, that helped the DNSBL checking a lot.

Enabling the local cache for e-mails is a big speedup for me when I find myself clearing the grid and rechecking or if I exit MW before washing and restart it with the old mail still on the server.

[rusticdog]

Enabling the local cache for e-mails is a big speedup for me when I find myself clearing the grid and rechecking or if I exit MW before washing and restart it with the old mail still on the server.

Or if you have 6000 emails and MailWasher hangs

[claykin]

Enabling the local cache for e-mails is a big speedup for me when I find myself clearing the grid and rechecking or if I exit MW before washing and restart it with the old mail still on the server.

Or if you have 6000 emails and MailWasher hangs

Actually, my GMail account has over 7000 in the inbox and I'm too lazy to move them out.

BTW, MWP V6 has the same Base64 issue with Bellsouth.net accounts. Maybe you can patch that version too for those who don't wish to go with your new subscription model? BTW, I plan to purchase MWP2010 upgrade once I see the issues are fixed.

[rusticdog]

Yeah, trying to get my hands on a copy of one of these emails. I think I might even have one at home.....somebody somewhere sent me a message that was dodgy in 6.x as well, but my memory is shot to shit right now

[claykin]

Yeah, trying to get my hands on a copy of one of these emails. I think I might even have one at home.....somebody somewhere sent me a message that was dodgy in 6.x as well, but my memory is shot to shit right now

I'll help you out, but I have no idea what to send you?

[rusticdog]

The Base64 problem is an email formatted a certain way and I need the full email causing problems in original form. The ones I've seen in the logs all had the subject similar to "Individual & Family Health Insurance as LOW as $99!"

Once the FA tech gets in I was going to get him to scan our FirstAlert database for the email, as we may have a copy in there.

[claykin]

The Base64 problem is an email formatted a certain way and I need the full email causing problems in original form. The ones I've seen in the logs all had the subject similar to "Individual & Family Health Insurance as LOW as $99!"

Once the FA tech gets in I was going to get him to scan our FirstAlert database for the email, as we may have a copy in there.

I have that email in one of my bellsouth.net accounts. The other bellsouth account does not have that email but was still trashing MWP before your V1.0.2 patch. So, apparently there's other people sending Base64 emails.

Can I simply forward the "Individual & Family Health Insurance as LOW as $99!" email to you? or do you need access to my account to see it in its original form? I can give you access if you need it.

[rusticdog]

If you can download the email and forward it as an attachment that should work.

[claykin]

If you can download the email and forward it as an attachment that should work.

Support case updated. Base64 emails added as attachments. I sent you four different ones to look @.

When I click WASH MAIL in V1.02 it says "washing mail" for close to 30 seconds before it starts deleting. Why does it take so long? This is one of my bellsouth accounts that had less than 200 emails in it. I'm on Win 7 x64, i5-750 8GB RAM and cable modem with 20+Mb/s down and 4Mb/s up so I don't think its me. I don't recall V6 taking this long (though I didn't use it much).

Separately, I left V1.02 running overnight only checking my 2 bellsouth accounts. Today when I went to WASH MAIL it wouldn't do it. Showed "washing mail" in lower left and it kept animating the green bar for 10 minutes before I finally closed MWP and reopened it. Argh!!

[rusticdog]

OK, I'll try and look at this soon. There's an All Black game (Rugby) then a NZ Warriors game on after that (Rugby League), so I'm on a go slow tonight.

In response though to the Wash Mail, I think it's possibly a case of our own timing. When you Wash, the UI sends the details to the engine, the engine in turn does all the work and sends back to the UI events that detail what's going on. So it's possible the engine has done many of the deletes by the time the UI indicates, I'd need to check.

Another cause could be PIPELINING, as this sends delete commands in batches and doesn't wait for a reply from the server inbetween, which is something the old version never did.
So when you have 200 emails to delete, the engine will logon, get the list of 200 emails, compare those emails in the list to delete and send 10 delete commands, it's not until it gets replies from that first batch that it can tell the UI, so there's a decent amount of processing time going on there. In your Account settings under Advanced, you could try disabling PIPELINING when deleting and see if that makes a difference, as that will get a reply for every deleted message. The only side effect is it's slower to delete email in general.

[rusticdog]

These MSG files came from Outlook right ?

Nevermind : I realised I could check your settings file and saw you had Outlook configured.


I don't have Outlook at home, so will test these in the office next time I'm in.