Mailwasher with avast 4 home

[nanette]

Please can anyone help, I have just downloaded avast4home, Its good but can,t configurate mailwasher with avast, mailwasher does not like numbers, as avast
puts numbers in your outlook express in the smtp and incoming mail mailwasher can only recognize letters.
I have mailwasher pro.
anyone got any tips how to get round this as I now have to delete every email.
I would be most grateful.

[w0mbat]

Hi Nanette,

I too use mailwasher, and you do not need to cnfigure it to work with Avast.
Mailwasher does not download you emails to your computer, it only allows you to view the text or/and the email headers, not to "Open" the email or any attachments.

It's only your email program IE outlook express, that needs to be configured to allow Avast to scan the mail before you can "open it"

Hope that helps

w0mbat

[S.Z.Craftec]

Mailwasher works just perfect with avast! They love each other, actually they adore each other...

No problems at all. There is nothing you have to configure in your Mailwasher except your pop3 server names, login name and password for each account you want to be checked. After that, just run Mail Protection Wizard (it's in your START menu / Programs, under avast@ antivirus... Let him autoprotect all your accounts and it will work just like it should work.

Avast! must change your pop3 and SMTP server names into 127.0.0.1 in order to take over over your mail client... otherwise, no point to use antivirus mail protection, right ? Same story with account name: yourname@youraddress.com#pop.youraddress.com

In avast! On-Access Scanner, did you start INTERNET MAIL PROVIDER ? If not, you should do that, 'cause that provider is for Outlook Express and all your WEB mail related accounts. If you don't use MS Outlook/Exchange (big difference between Outlook and Outlook Express), you can disable OUTLOOK/EXCHANGE provider without having any problems...

Cheers !

[DavidR]

Mailwasher doesn't need to interact with avast as it doesn't download email, that is handed to your email program when you click process.

Provided you had setup/installed MailWasher before you installed avast everything should be fine.

However, if you were to set it up after avast had run the Mail Protection Wizard abd changed the settings within your email program, it could cause a problem.

Mailwasher imports email account details, server, username, etc. (from your email program) that you select on installation. if the server setting has been changed to 127.0.0.1 then mailwasher will try to connect/check for that server on your local host and won't find it.

If this is what is happening let us know and we can give a solution?

HTH David

[nanette]

Thankyou to all your replys.
I discovered although mailwasher said it could not recognize numbers, it was in fact my user name which
was wrong, norton was still there after my name,I deleted norton and it worked.
As I had norton before , Internet exployer was scripted I see avast does not script the web for viruses, What does everyone else do about this.?

[S.Z.Craftec]

Yes, avast! has SCRIPT BLOCKER... but, you have to buy pro version to have that feature. All those features can't be included in freeware version, don't you think so ?

See attachment...

[DavidR]

I use AnalogX.com Script Defender.

[bob3160]

On my system, Avast is apparently checking e-mail handled by Mailwasher Pro.  I see the checking icon in the tray and also have the message that it's been checked by mailwasher.......... ::)

Should I be changing my e-mail addresses back to what they where before the 127.0.0.1 ?????

[S.Z.Craftec]

No, why Bob ? Just leave everything like it is... to be sure, just run avast! Mail Protection Wizard one more time. Be sure to put checkmarks on Automatically protect all my accounts and all accounts that I create in the future.

That's all...

[DavidR]

On my system, Avast is apparently checking e-mail handled by Mailwasher Pro.  I see the checking icon in the tray and also have the message that it's been checked by mailwasher..........

Should I be changing my e-mail addresses back to what they where before the 127.0.0.1 ??

Yes, that would appear to have the effect of mailwasher doing its checking on the local host 127.0.0.1 (HDD) rather than at the mail server.

This would happen if you installed pro after avast (or imported an email account into MW Pro after avast) as it copies the account information from your email program and that has had its server, username settings changed by avast.

EDIT: The whole point of MailWasher is that it doesn't download full emails to check them, only headers and xx number of lines to help classify as spam, etc. This is done as plain text (not in your email program) and no script activation.

So, I believe the overhead of checking with avast is not required.

[bob3160]

David R  that's what I thought to.  The whole Idea of Mailwasher is to check e-mail from the source before it gets to my computer  but since it's going thru Avast, that's not what's happening.
When I re-installed XP, the first program I installed was Avast and since Avast is set up to check all future e-mail account, it treated mail washer's accounts as new account......  Logical   very Logical

[DavidR]

David R  that's what I thought to.  The whole Idea of Mailwasher is to check e-mail from the source before it gets to my computer  but since it's going thru Avast, that's not what's happening.
When I re-installed XP, the first program I installed was Avast and since Avast is set up to check all future e-mail account, it treated mail washer's accounts as new account......  Logical   very Logical

It's not so much avast treating mailwasher accounts as new accounts, but mailwasher importing the details from the accounts that have already had their details changed by Mail Protection Wizard.

Otherwise when I re-installed avast it would have changed the account details within mailwasher (as part of MPW's protect all accounts and new accounts, etc.), it didn't. It wouldn't have been able to cope with the fact I have a hotmail account set up (in mailwasher) to check and delete spam at source.