Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: csturnbull on April 27, 2004, 04:11:28 PM
-
I am a new user to Avast and I use Mailmate Antispam & Outlook 2000. Basically Mailmate collects my mail and allows the good ones to go on to Outlook 2000. Mailmate holds back spam in a folder of its own until I wish to deal with it.
Outlook is configured to collect with pop server changed to 127.0.0.1. I have also had to use this setting in Avast Home so consequently the spam is not checked unless it is done manually by checking the spam folder.
Can anyone help me with this? Even better does anyone use Mailmate Antispam and Avast Home together?
Thanks
Clive
-
There is no need to use mailmate to filter the spam. You can create rules in Outlook that will filter it and send the spam directly to the recycle bin (removed items).
-
There is no need to use mailmate to filter the spam. You can create rules in Outlook that will filter it and send the spam directly to the recycle bin (removed items).
how?...is it as reliable as spam filter?...do you mind giving us a short review...
thanks in advance.. :)
-
Actually it is very simple. With the build in rule wizzard you can set rules on what to with incomming emails. You can set them so that when a mail is received from a certain sender it goes to folderA when it is from another sender it goes to folderB. You can do the same by checking the subject and/or text of a mail.
Esample:
If mailtext has the word viagra in it, direct the mail to the removed items folder.
You can find the rule wizzard under the 'extra' menu (in English versions it is called tools menu)
Here are some nice sites explaing a bit more:
http://help.bnsi.net/mailrules/otmlrls.php
http://www.slipstick.com/rules/
I use Avast Pro in combination with ZoneAlarm Pro and created rules in Outlook 2002. Sure in the beginning spam would still come through the filters/rules. But after some time when I got to understand the functioning of the rules better, and adjusting the rules, no spam comes trough anymore. It takes a while to set it up correctly and I'm not saying you shouldn't use a 3rd party spam filter, just saying it can be done without one. The choice is all yours my friends.
-
thanks artras.. :)
so i guess the only difference is a manual learning process to identify spam as compared to spam filters...
-
Basicly, yes. A benefit of setting the rules manually imo is that you don't need to have another prog running all the time, which can slow down a system or at least is using some cpu time.
-
Can't say I agree altogether, I struggled with rules for ages and just dropped on Mailmate Antispam(Don't confuse with Mailmate Express) I was really impressed with this so I paid up and apart from the poor support I am really pleased. It does not slow anything noticeably and I now only get real emails in Outlook Inbox.Heaven! also works fine with Outpost firewall.
Problem, yes! All the spam with virus's etc are in the Spam Folder in Mailmate! Avast doesn't see this unless checked manually.
Both Mailmate and Avast use 127.0.0.1 which I wonder about.
Don't really feel like scrapping a programme I have just bought that works so well to go backwards wih Outlook Rules.
I am only a novice really and would like all the advice I can get. I like Avast and really want to keep it going.
Cheers all
Clive
-
Many antispam programs work as mail proxies (just like avast) These proxies generally use the same ports but can be configued to work together. I use Spampal (an antispam mail proxy) in conjunction with avast!
I am not familiar with Mailmate but I expect that if they are like most antspam proxies they will have support and documentation for setting it up with antivirus programs at their site. If not you may get some ideas on how to do it by perhaps visiting the Spampal site (www.spamplal.com) and review their documenation on setting Spampal up with various antivirus programs. The general concepts should (and do work) for most mail proxies when you want to "chain" them together.
If you want avast to filter all mail (including the spam) I think you need to chain your proxies this way:
Outlook ---> Mailmate ---> avast! --->pop3 server
Chained this way avast will have disinfected all the mail before Mailmate gets it.
Sean D
-
I have been thinking about this issue and based on a search of these forums there have been a number of threads concerning "chaining" mail proxies that have been quite informative. A search on "spampal" or "popfile" will give some good information.
While the following (based on the excellent avast! help file) does NOT address the issue with Mailmate (because in that case the "chain" needs to have avast! be the last in the chain, the following "generic" modification to the avast4.ini allows a user who already has a working antispam proxy configued in their mail client and is now installing avast! and would like to keep the benefits of the existing application while adding antvirus services from the avast! Internet Mail Provider.
Assuming the mail client is now configured and working with an antispam client (using standard port of 110 listening on local host 127.0.0.1) e.g.:
mail client ---->127.0.0.1:110 (antispam proxy)----->pop3 server
By adding the following lines to the avast4.ini and making a single change of a port number in the mail cleint avast will be inserted in the proxy "chain"
[MailScanner]
PopListen=127.0.0.1:8110
Trust=127.0.0.1
DefaultPopServer=127.0.0.1:110
Now by changing only the pop server port number in the mail client to 8110 and without changing the user id or mailserver entries in the mail client, avast! can be inserted in the "chain" and will process any mail downloaded to the mail client inbox. i.e.
mail client ---->127.0.0.1:8110(avast!)---->127.0.0.1:110(antispam proxy)--->pop3 server.
This scenario should work for multiple accounts if the antispam proxy supports that feature (the only caveat being that the antispam client does not use the "#" in its parsing of the user id to extract the destination pop3 server.)
For those who would prefer or need to have avast! as the last proxy in the chain (because for example Mailmate apparently does not pass spam back to the client but apparently puts it into its own chest and the user wants that disenfected also, if I understand correctly, then it gets a little bit more complicated and I would need to know exactly how the antispam proxy requires the user id to be set up. The mail client would need more changes then just a simple port number being modified.
Sean D
-
Sean
Many thanks for your input, I did have SpamPal and found it really good and only changed because of the problem that Outlook was telling me I had new mail every time spam arrived. Of course this doesn't happen with Mailmate as it never reaches Outlooks Inbox.
I have tried altering port as you suggested and the ini file for Avast but I just get a mail delivery error as you expected I would. I'm afraid I'm no whizz kid so really I am stumped. but I am sure I need Avast to check the mail before it gets to Mailmate. I am loathe to part with Avast or Mailmate although I could go back to SpamPal if I could get rid of mail notification evey time I get spam. Be grateful to supply you with any details you might need to help.
Many thanks again
Regards
Clive
-
Clive,
I tried going to the Mailmate site, checked the FAQ and clicked on the link for configuring mail clients but got a 404 error so could not get what I needed. I wonder if you can post a working client config for Mailmate (without putting in your personal information) and I will give it a shot on figuring out how to set this up. Also, do you use it for multiple accounts or just one?
Sean D
-
Sean
Thanks for your assistance. I think you may have been to the site of Mailmate Express which is a different animal. I am quite willing to send you config but see if this helps first. http://www.brezosoft.com/config.htm
It is 1.40am here so I may not be able to view the forum till tomorrow.
I am grateful for your help as I really want to get these working together.
I am afraid I do have multiple accounts but if I can configure one I will be able to work from there.
Regards
Clive
-
seand, very thanks for your post...
Can you see this forum? http://forum.avast.com/index.php?board=9;action=display;threadid=3413
Can you teach us how to configurate Spamihilator and avast in a chain...
I mean: I want 'first' getting rid of spam and then scan the other messages (the ones really downloaded) with avast. I'll earn time and money. Other users will be happy too. Thanks. ;)
-
Clive,
I checked out the Mailmate link you posted, thanks.
Please try this:
Step 1.
Modify the avast4.ini so that avast listens on a different port than 110. In the example I have picked 8110
[MailScanner]
PopListen=127.0.0.1:8110
Trust=127.0.0.1
Setup Outlook and Mailmate to work together as they have in the past. (without avast!)
Verify that the setup is working before going to the next step. Outlook should be able to connect to and collect mail from all your pop servers. Avast is not in the chain yet.
If you can collect your mail and Mailmate is detecting spam make sure the Internet Mail Provider in avast is running (not complaining about port conflicts etc.) go to the next step:
Assuming for your Mailmate config your current pop user name in Outlook looks like jsmith@yourisp.com, modify your pop user Name to be:
jsmith#yourisp.com@127.0.0.1:8110
Do not change the pop server in Outlook (which should be 127.0.0.1)
Now try collecting your mail (assuming you have new mail already, if not send yourself some mail)
If all goes well Outlook should collect your mail and while it is being downloaded it will first be scanned by avast and them by Mailmate. The spam retained by Mailmate should be disinfected or clean and the mail in your inbox also.
This all depends on whether or not Mailmate recognises the :8110 at the end of the 127.0.0.1 as being the pop port to use.
I am operating on NY (US-EST) Time so will not be back unitll late tomorrow your time. Hope this works.
Sean D
-
Technical,
I will be glad to help if I can. I will check out the thread now but it is quite late here and I have to be up early in the AM for a meeting, so probably will not be back on the forum untill about 11 AM tomorrow (US EST time) -0400
Sean D
-
Sean
I did try quickly last night but it was late. No joy but I did try different ways. I also tried altering the ports on Outlook and Mailmate but got confused in the end. There is a facility for specifying which port to use so that is easy also one under Advanced tab in Properties.
Can't quite be sure you meant to alter Outlook when you said
"
Assuming for your Mailmate config your current pop user name in Outlook looks like jsmith@yourisp.com, modify your pop user Name to be:
jsmith#yourisp.com@127.0.0.1:8110 "
Whowever I have tried all ways and everything is OK until I make this alteration. I have probably got something wrong around this area.
Aplogies for not grasping this immediately but as I said I am no expert with computers, but need to keep trying
Working till about 6pm GMT.
Thanks again
Regards
Clive
-
Clive,
Sorry it is so difficult. Debugging multiple proxies gets difficult.
Best way to start is get one of them working and tested before trying to chain a second one.
So if you dont mind please start with configuring Outlook and Mailmate to work and ignore avast for now. Given that you can change the pop server port that Mailmate works on, the first step I would ask is the you pick an unused port (like 7110) for Mailmate to listen on and then config your Outlook to work with Mailmate by changing your pop server port in Outlook to 7110 and the pop user name to YourPopName@YourISP.com e.g. you@pipex.com (whatever worked for Mailmate before you tried chaining avast)
Once this is done and tested to be working we are ready to go to then next step.
I am just leaving for work now and should be able to get back on about 11 AM NY time -0400 hours. If possible send me email and let me know if you get Outlook and Mailmate working along with the port and pop user name in Outlook and when I sign back on I will figure out the config changes to insert avast in the chain so that all mail is filtered before getting to Mailmate.
Sean D
edit: Please double check the Mailmate docs and make sure it does not use the '#' as part of the seperator char when you set up the pop user name in Outlook. (The online docs says it uses the '@' char but it may use a secondary one.). Also when changing the port for Mailmate to listen on you may have to reboot for it to take effect (I dont know).
-
Sean
I tried as you suggested with 7110 but got an error mesage saying another programme was using this port. I then changed both ports to 8110 and everything seemed to go through the sequence fine with no error message.
Mailmate only appears to change pop settings to 127.0.0.1 and alters my username to my email address. This is not the same as my pipex username which is a combination of letters and numbers. I remember SpamPal as being more complicated and using two @ chars.
I suppose Maimate picks up the mail using my Pipex settings and then Outlook picks it up from MailMate using my email address and 127.0.0.1
Am I correct? All we have to do now is to link in Avast ???
Well that's me lost!!!
Cheers
Clive
-
Clive,
OK, based on your post I "think" that Outlook and Mailmate are now running correctly and avast is not scanning your mail yet, is that right?
Now if you dont mind please post just what the settings are for each of the following:
Outlook: what is the pop3 port number?
Outlook: what is the pop server?
Outlook: what is the pop user name?
Mailmate: what pop port is it listening on?
With that info we should be able to put avast in the loop and handle multiple accounts (hopefully)
If you can please take a look at the avast4.ini and tell me what the PopListen and DefaultPopServer entries are right now (before we change them)
Sean D
-
Sean
Incoming Mail Port 8110
Incoming Pop3 Server 127.0.0.1
Pop username csturnbull@dsl.pipex.com
Avast4.ini I will email this for you
Is that OK
Cheers
Clive
-
Sean
Forgot to say Outlook & Mailmate working fine.
Cheers
Clive
-
Clive, From looking at your avast4.ini it appears you have not yet configured the Internet Mail Provider in the avast! On Access scanner. The complication going on here is that I suspect you have enabled the Exchange/Outlook Plugin and what we are doing here is trying to treat Outlook as a "generic" Internet mail client since that is how it is behaving with Mailmate.
Let's try faking it out by putting this section in the avast4.ini
[MailScanner]
ShowTrayIcon=0
UseDefaultSmtp=1
AutoSetProtection=0
PopListen=127.0.0.1:110
Trust=127.0.0.1
DefaultPopServer=dsl.pipex.com
Once you have done this save the file and try starting the Internet Mail Provider in the avast! On Access scanner.
If it starts and there are no port conflict messages shown by anything then the last thing to do is to go back into Outlook, change pop user name from csturnbull@dsl.pipex.com to ----> csturnbull#dsl.pipex.com@127.0.01
This should now put avast! in the chain. I imagine that with the Exchange/Outlook plug-in enabled you will actually have your mail in Outlook scanned by avast twice, once on the way in from the server (by Internet mail Provider before it is scanned by Mailmate) and the second time when it arrives in your Inbox by the Exchange/Outlook Provider. You probably can/should disable the Exchange/Outlook Provider-in but I do not know what additional services it provides Outlook users so lets check with avast! Tech Support on that.
I hope this works for you now. Hang in there, its a learning experience for me too and I am enjoying it, hope you are.
Sean D
-
By the way Clive, I owe you an apology. I completly missed the fact that with Outlook installed you were probably running the Exchange/Outlook plugin. I don't run Outlook anymore and had chosen not to install that feature weeks ago.
I dont know how the Exchange plugin works, but suspect it does not act as a proxy but rather scans the outlook.pst file as mails are added during the download. If it does act as a proxy there might be a port conflict on 110 but for the proxy filtering to work with Mailmate we need the Internet Provider to use that port, so whether we like it or not the Exchange plugin may have to be disabled for any of this to work. Your mail will be scanned by the Internet Mail Provider in the proxy chain so I dont think you lose any protection by doing it this way.
Again, sorry for not paying full attention.
Sean D
-
Sean
No problem, I am really forced into the Outlook thing as My PDA & Notebook both sync with it. I used to use Poco Mail which was fine but it seemed a bit silly to not go along with the integration.
Update
All went well until I pressed send & receive on Outlook where I am prompted for a password because of altering the username, I presume
anyway.
Sorry for the delay someone called.
Regards
Clive
-
Clive,
Yes, when you change the user name Outlook will/may prompt you the first time for a password but you should be able click on the "remember" option and not have to do that again.
Besides all that does the chain work now (I am dying to know)
You can verify by checking the headers of the emails, you should be able to find two avast headers at the bottom of the header section. If Mailmate inserts headers those should be below the avast ones, demonstrating that the mail was filtered by avast them by Mailmate.
Sean D
-
Sean
I don't know yet as this password will not be accepted and just gives a mail delivery error which pops back up everytime I ok it
Cheers
Clive
-
If I remember correctly Outlook pops up that Password Prompt on most errors but when you click on cancel and then view the details of the failed session you may see a better explanation of the problem e.g. "Cannot connect to server", etc.
Debugging multiple proxies in a chain is troublesome but you do know ithat Mailmate was working before you put avast in the chain so the next thing to do is to take Mailmate out of the chain and test with Outlook and the avast proxy alone (no spam filtering by Mailmate).
To do that you would change the Incoming Mail Port in Outlook back to 110 (should be 8110 before the change) and change the pop user name to csturnbull#dsl.pipex.com (should be csturnbull#dsl.pipex.com@127.0.0.1 before this change)
This config will cause Outlook to bypass Mailmate completly (Mailmate is listening on 8110, and the avast Internet Provier is listening on 110)
Try collecting mail (it will not be filtered for spam, but you will be testing the avast Internet Mail Provider.
To summarize:
If all proxies are setup and running correctly all the following tests shoud work:
Outlook using Maimate only:
Incoming Mail Port 8110
Incoming Pop3 Server 127.0.0.1
Pop username csturnbull@dsl.pipex.com
Outlook using Avast Internet Mail only:
Incoming Mail Port 110
Incoming Pop3 Server 127.0.0.1
Pop username csturnbull#dsl.pipex.com
Outlook using Mailmate chained to avast Internet Mail
Incoming Mail Port 8110
Incoming Pop3 Server 127.0.0.1
Pop username csturnbull#dsl.pipex.com@127.0.0.1
Things to look for.
Is the Internet Mail Provider running in the avast On-Access Scanner?
Is there any port conflict on 110 preventing avast from running?
After entering the password and clicking OK at the Outlook Password prompt if the password prompt reappears immediately click on Cancel and view details of the error.
Sean D
-
Sean
Well test 1 works fine but not test 2 which I think points to a problem with Avast and Outlook. I have shutdown mailmate altogether, still an error which reads "unable to connect to server 127.0.0.1 err 0x800ccc0e"
Couple of things I would like to mention.
It is Mailmate that changes my popserver name to csturnbull@dsl.pipex.com which is usually ****90@dsl.pipex.com given to me by Pipex also we have changed the avast4.ini from how it was. I have altered these back and to try but still the same error so I feel that it is something to do with Avast setup. Would like to mention that as it was originally after installing Avast and already having Mailmate, Avast was scanning my inbox ok.
I feel I am putting you to a lot of trouble but it would be really good to see it setup to work. Sorry I am not a bit more savvy! That way I could be more help.
Regards
Clive
-
Clive,
I am willing to hang in there if you are!
Just to backtrack a bit. If you revert to the original settings and just use Outlook and Mailmate is the avast Exchange/Outlook plugin still scanning you inbox? (sure hope so!)
The error reported by Outlook might mean something else already is listening to port 110 which means avast cannot open it and get in the chain.
Avast needs your real user name to be used in order to work so using the test scenario #2 (Outlook with avast only) that I outlined above you should try putting ****90@dsl.pipex.com#dsl.pipex.com in the user name and port 110 for testing Oultook with avast only,
This assumes that your pop user name is ****90@dsl.pipex.com and pop server is dsl.pipex.com
If this is the case and the test works, the problem we are experiencing is that Mailmate cannot deal correctly with an "@" in the user name because it is using the "@" as a seperator. The only other alternative is to ask Mailmate if it can be configured to use a different seperator char.
Sean D
-
If there is an "@" in your pop user name there is another alternative that might work but only for your main account, not multiple, so if that is the case I can figure out the avast settings to do that if you want to try. This all depends if the test2 with Outlook, your real pipex user name and avast only, worked based on the previous post.
edit: Actually if you get test2 to work with the new settings, there may be a way to insert avast in the Mailmate chain for ALL accounts at dsl.pipex.com but not for other isp's
Sean D
-
Yes I am willing to keep going!
I can use original settings and port 8110 in Mailmate & Outlook and Avast scans inbox. Works fine!
Can't get test 2 to work with:
Incoming Mail Port 110
Incoming Pop3 Server 127.0.0.1
Pop username ****90@dsl.pipex.com#dsl.pipex.com
Still get the same error can't connect to 127.0.0.1 this is using port 110 as you suggest.
Cheers
Clive
-
Clive, I am very glad that nothing has broken the original setup and that avast is still able to scan the Outlook Inbox <sigh of relief>
From here on please keep a copy of the current avast4.ini as a back up just to be safe.
OK, back to the drawing board: We need to get avast Internet Mail Provider working iwith Outlook.
Before we assume something else is running on port 110 please check that the Internet Mail Provider status is running in the avast Resdient Shield. If it is try clicking on the Terminate button, wait for it to stop then try starting again (Start button) to look for any errors or messages.
Then try the following test:
Outlook using Avast Internet Mail only:
Incoming Mail Port 110
Incoming Pop3 Server 127.0.0.1
Pop username ****90@dsl.pipex.com#dsl.pipex.com
If we get the same "cannot connect error" then we should try another port. This requires editing the avast4.ini (make a backup)
To change the port to 29110 use the following:
[MailScanner]
ShowTrayIcon=0
UseDefaultSmtp=1
AutoSetProtection=0
PopListen=127.0.0.1:29110
Trust=127.0.0.1
DefaultPopServer=dsl.pipex.com
*Remember to save the changes, avast monitors for any changes to the ini file, but it probably would not hurt to stop and start the Internet Mail provider again.
Then try a new test with the following settings:
Outlook using Avast Internet Mail only:
Incoming Mail Port 29110
Incoming Pop3 Server 127.0.0.1
Pop username ****90@dsl.pipex.com#dsl.pipex.com
If we get the same error then we probably have avast setup problems.
If an error does occur, please read the details in Outlook, it may be a different error which means we are making progress.
After testing change please let me know, then change back to the origial so you dont have to deal with all that spam.
Outlook using Maimate only:
Incoming Mail Port 8110
Incoming Pop3 Server 127.0.0.1
Pop username csturnbull@dsl.pipex.com
Sean D
-
Sean
Followed that to the letter and still the same error. I reckon maybe the setup is incorrect for Avast in some way. I have even shutdown Mailmate just to be sure so it isn't even in the equation. Can I have done something incorrect when installing? Most of it looked straightforward
Thanks
Clive
-
Reverted to Mailmate settings and running ok.
Cheers
Clive
-
Clive,
Before doing the following back up your ini file.
Would you mind running the Avast Mail Protection Wizard and choose "Setup Protection manually", then select "I dont use Outlook" then select" my Account is not on the list", ignore the Hellp file popup and select "next" where you will be prompted to enter a default smtp and pop server, then on the next screen accept defaults on the resident settings.
After the service starts, verify that your Exchange/Outlook plugin still works with Outlook and Mailmate and then we can try debugging from there.
One question: Are you running Outlook on the same PC that avast is running?
Sean D
-
Ignore the last message, couldn't find the wizard! Found it and done all that. It said it wasn't running :-[ Although it was checking the inbox.
Where next???
Cheers
Clive
-
Clive, what was not running, Exchange or Internet mail Provider. I am online now ...wanna do this on private message for effecinecy?
-
Whew, problem fixed! Gotta give you a lot of credit for hanging in there Clive!
Was an interesting experience and I will post a summary of what the solution was a little later today (gotta get back to work now)
Sean D
-
Outlook, Mailmate and avast finally working together.
The specific need was to have all mail scanned by avast for viruses. Using the avast! Exchange/Outlook provider all mail downloaded by Outlook was being scanned but the spam captured by Mailmate was not.
This appeared to be a simple proxy chaining issue with the need to have the mail first filtered by avast, then Mailmate and finally delivered to Outlook or retained by Mailmate in its spam folder.
After several attempts to "chain" the proxies we learned that actually Mailmate does not act in the normal fashion of a pass-thru transparent antispam proxy (like Spampal). Insead Mailmate acts as a mail client to download mail from all accounts and then acts as a POP server to distribute non spam mail to Outlook and retain all spam mail in a quarantine folder.
Once we realized this, it was relatively simple to put the avast! Internet Mail provider in front of Mailmate so that when it collected email from all accounts (as a standard mail client) the mail was scanned for viri while being downloaded.
The avast [mailscanner] section in avast4.ini was configured to listen to port 29110 since it appeared that another unknown application was already usuing 110. After that it was simply a matter of modifying the pop user name and pop server and port in the Mailmate account config using the standard instruction in the avast! help file for configuring the Internet mail provider.
Step one: changing the file AVAST4.INI
Open avast4.ini file in Notepad editor. You will find this file in the folder Data in your avast! installation folder, e.g. C:\Program Files\ALWIL Software\avast4\Data.
Find the section named [MailScanner]. Write these lines into this section (if they already exist, change them):
DefaultSmtpServer=smtp.server.com
DefaultPopServer=pop.server.com
DefaultImapServer=imap.server.com (only if you are using IMAP server for incoming mail).
Replace smtp.server.com by the address of the SMTP server you are using, e.g. smtp.tiscali.com. Do the same for POP (and IMAP) server (e.g. pop3.tiscali.com).
If your e-mail program supports SMTP authentication, and also makes it possible to set a different login name for SMTP than for POP, insert the line: UseDefaultSmtp=0.
If your e-mail program does not support SMTP authentication, insert the line: UseDefaultSmtp=1.
Save the changes and close the Notepad editor.
Step two: modifying the account properties in your mail program
Launch your mail program.
Let the program display the account settings.
If you want to check outgoing messages, change the address of SMTP server to the address of the local computer, i.e. 127.0.0.1.
If you want to check incoming messages, change the address of POP (IMAP) server to the address of the local computer, i.e. 127.0.0.1.
Change user (login) name this way: append the character # (double hash) and the address of your POP (IMAP) server (the same as you specified in the avast4.ini file in Step one). Login name should then look like this:
Ann.Jones#pop3.tiscali.com
If your e-mail program supports SMTP authentication and also makes it possible to set a different login name for SMTP than for POP
If the SMTP authentication is enabled, append the character # and the address of your SMTP server to the login name (e.g. annie2#smtp.tiscali.com).
If the SMTP authentication is disabled, enable it and use the character # together with the address of your SMTP server as the login name (e.g. #smtp.tiscali.com).
Save your changes.
The manual setting of the Mail scanner is now complete.
Now all mail downloaded by Mailmate is scanned by avast! and both spam and non-spam is disinfected if they contain viruses.
I am real glad you hung in there Clive, I think it was well worth while. Avast! is a superb program and I am delighted we solved this problem together.
Thanks,
Sean D
-
Sean
Worth every minute and of great benefit to me!
Thanks once again
Clive