Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: sijgs on November 25, 2004, 01:16:30 AM
-
I run my own e-mail server (MDaemon) which is on ports 110/25 (POP3/SMTP) and so I have Outlook Express changed to send/receive on ports 26/111 and Avast default listening ports set to those as well.
After today's update... in Outlook Express, the SMTP server was changed from 127.0.0.1 to 127.0.0.1:25 ????? Of course, that didn't work, so I removed the :25.
Well, everything seems o.k. now EXCEPT, Avast is not only scanning my mail when it's sent from Outlook Express to MDaemon, but....
Somehow, it has it's hooks into MDaemon SENDING the E-Mail and scans it again as it is sent......
Any clues as to why this might be happening now???
I scanned the Avast4.INI file and there is no apparent reason in there for the action....and I can't fathom how it got it's hooks into outgoing mail.... yes the mail goes to the recipient o.k.
Any thoughts?
Regards,
JGS
-
The new version of Avast works transparantly on Nt based systems. Setup the mail as if Avast isn't there. Does this solves the problem?
-
Are you saying that it can figure out that there is an "onboard e-mail system" and I no longer have to have OE feed Avast who feeds MDaemon??????
Errrr.... how did "They" accomplish that????
JGS
-
Are you saying that it can figure out that there is an "onboard e-mail system" and I no longer have to have OE feed Avast who feeds MDaemon??????
Avast should work that way now.
Errrr.... how did "They" accomplish that????
With a lot of work ;D
-
cute.... o.b.k.b. I'll remove the double routing and check....
I'll post it here so everyone can read it (???? and weep?)
Tnx, Gracie, Danke Schoen, etc.
JGS
-
??? I changed OE to port 25/110 and the outgoing e-mail did not get scanned AT ALL.
Changed it back, and it scanned it twice.....
Thoughts?
Regards,
JGS
-
Can you try this:
- Create a backup of Avast4.ini
- Than change the mail section part in avast4.ini so that these settings are there:
[MailScanner]
Log=20
DefaultPopServer=
DefaultSmtpServer=
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
PopListen=
SmtpListen=
ImapListen=
- Setup the mail as if Avast isn't there.
- Check if the mail is working
Let us know if it helps.
-
as they say in Chinese, Voila' ... er or is that Korean.. (snick)
Thanks, that did the trick.... it now scans just one time... upon sending from MDaemon....
Now just HOW did you hook in there.....???? and what????
Regards,
JGS
-
I studied for magician ;D
I (and others) where helping someone with a problem with Avast, we tried all kinds of things. That ruled out a lot of things. Suddenly I thought "What if for some reason the update from 4.1 to 4.5 doesn't handle the settings in Avast4.ini correctly?" The person we where helping was willing to try it and it worked.
That's how I came up with this solution. I now hope that Alwil will look into this because it seems that on certain systems the upgrade isn't exactly going like it should.
ps: The line Log=20 is for extended logging. You can safely remove that if you don't want an extended lof file.
-
;D HA! mine is log=100 (so I just left it.....)
Thanks much for the "steppin' in there..." great to know there is such a willing set of support help in the community...
Regards,
JGS
-
Whoa! belay that "IT'S WONDERFUL" line I just passed...
NOW,
No incoming mail is scanned.....
HOLY MACKEREL!!!!
Whas' up now????
JGS
-
Are you using a NT based system? If not, run the mail protection wizzard.
-
I guess I have to presume that W2K is an NT based system.... no? ..... yes, I am then....
Again Regards,
JGS
-
Yes, 2K is NT based.
Can you retry the procedure we did to see what happens?
Also check Avast's log file for an error.
And what is telling you that the mail isn't scanned?
-
Normally (.... er before this "erpdate?")
it would show me the little title bar above the toolbar on the bottom whenever it "scanned" an e-mail coming in from MDaemon, and also insert the text that it was scanned by Avast and clean....
:-( no such bar now or item inserted in the message
I am not sure of what else you are asking .... as in "try it again...." can you elaborate or is it just too late here and I don't comprehend.....(sorry if so...)
Regards,
JGS
-
Open the on-access control panel and click on the internet mail provider. Note the number of things scanned. Send yourself a email. Than receive that email in OE. Does the scan count increase?
-
No, count prev=1, post=1
JGS
-
ok, put back the original avast4.ini (the one you had backuped) It should now be back as it was in the beginning.
ps: bedtime here, will catch up later.
-
o.b.k.b... since I did that ... you are absolutely correct... we are back at the first problem...
It now scans e-mail twice on the way out.....
Uhhhhmmmmm... what exactly are we doing here... trying to prove reality=reality or .....????
JGS
-
I think the problem is that you are using non standard ports in OE. I am not sure but adding autoredirect=0 to the mailsscanner section and than setup the mail protection manually could work. Use the search option on this board, keyword "autoredirect"
-
Sijgs, default values for avast4.ini file can be found in 'Settings' on my signature.
I can't reliase your actual situation, can you rephrase?
I can see that avast can scan both inbound/outbound mails and you just don't have the notes inserted into the body of the messages. Am I right?
-
I'll try to state the whole case simply:
MDaemon E-Mail Server sits on ports 25/110
Avast.ini is set to:
PopListen=127.0.0.1:111
SmtpListen=127.0.0.1:26
ImapListen=127.0.0.1:144
DefaultPopServer=127.0.0.1:110
DefaultSmtpServer=127.0.0.1:25
OE sends on port 26 and receives on port 111
Everything was fine until today's update.
Now,
outgoing e-mail is scanned twice (and two clean messages inserted)
incoming e-mail is scanned once (and "sporadically" clean messages are inserted but not always)
If I put everything back to normal, outgoing e-mail gets scanned only one time, but incoming does not get scanned at all.
That's it in a nutshell....
JGS
-
OK I have "temporarily" solved the problem by:
1) changing SMTPListen parameter to
SMTPListen= (nothing)
2) putting SMTP port in OE back to 25
3) but to get the inbound scanned, I have to leave the 111/110 "switch-a-roo" like I posted in the previous message.
So it seems that Avast4 has now somehow hooked itself into the outgoing message handling, but still needs a re-direction on the inbound side.
???
JGS