Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: indoor-footballer on August 19, 2004, 08:56:39 PM
-
Hi all,
Having a little problem with Avast home edition version 4.1 and wondered if you kind people could lend a hand please?
I'm using Outlook Express 6 and as you can see from the headers of an email, incoming em's are protected:
X-Antivirus: avast! (VPS 0434-1, 17/08/2004), Inbound message
X-Antivirus-Status: Clean
X-Filter-Result: Score: 0%, Threshold: 50%
BUT, the outgoing emails are NOT being protected ; - )
I use an smtp program called maildirect to send emails and it uses port 25 to send the emails.
Every time I reboot windows xp pro, I get an error message, which you can see here:
www.goodhorizons.com/avast
If it's any help, these are some of the settings in my avast ini file:
[MailScanner]
DefaultPopServer=127.0.0.1
SmtpListen=127.0.0.1:26
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
[VRDB]
Any urgent help on this much appreciated.
Dougie.
-
If you set avast to listen at port 26, you should set maildirect application to do the same, I suppose, into the email accounts properties... ;)
-
If I do that, the emails don't get sent.
-
If I do that, the emails don't get sent.
Why not? ::)
Did you left any other application on the port 25, for instance, Outlook Express, spam killers... ???
-
If I have all set to port 25, that should be ok, but it isn't.
-
If I have all set to port 25, that should be ok, but it isn't.
Can you use TCPView and see if any other application is using the port 25 and 26?
(http://www.sysinternals.com/files/tcpview.zip)
It should work...
How does maildirect work? Is there any help file available?
P.S.: Sorry, I'm leaving the forums now... Maybe tonight or tomorrow morning. Take care... ;)
-
Hasta Luego!
-
Hasta Luego!
Now, I'm back and you aren't :'(
Did that suggestion work?
Did you find help on the maildirect application webpage?
-
Yep, I had to go to bed at some stage in the day :( and that was that stage :D
That suggestion didn't work and there was no relevant info on the maildirect help page :'(
All I need is for avast and maildirect to both share port 25.
Any other ideas?
Are we the only 2 here?
-
Technical,
If mail direct doesn't want to cooperate, how about spmai?
-
I have no problem with maildirect, I just need avast to share the same port.
-
I just need avast to share the same port.
Not necesserily... Can you try using avast at 25 and your email program at 26?
Check if your email headers have the X line for avast (or a note added at the end).
-
Thanks to everyone whos sticking with this story - hopefully there's a happy ending!
Now, just tried what you suggested, I've got OE6 outgoing on port 26 and maildirect on port 26, and the good news is that I no longer get the 10048 error message from avast on starting the pc, BUT the bad news, is that the outgoing em's still aren't being scanned :'(
Here's the relevant bit from one of the headers:
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Antivirus: avast! (VPS 0434-2, 20/08/2004), Inbound message
X-Antivirus-Status: Clean
X-Filter-Result: Score: -100%, Threshold: 50%
Whats next?
-
Did you set avast correctly to scan Outbound emails (Internet Mail provider settings)?
Are you email settings changed to 127.0.0.1 with smtp authentication?
-
Yep and yep, but the relevany settings in my avast ini file is this:
[MailScanner]
DefaultPopServer=127.0.0.1
SmtpListen=127.0.0.1:25
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
[VRDB]
Is the problem here?
Your helps appreciated.
-
Yep and yep, but the relevany settings in my avast ini file is this:
[MailScanner]
DefaultPopServer=127.0.0.1
SmtpListen=127.0.0.1:25
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
Is the problem here? Your helps appreciated.
Seems ok...
Can you send me an email? ;)
-
Done
-
Done
Sorry, my spam killer caught your email... :'( I lost it...
-
Nope, when I tried to email you, I got this message:
Send mail directly failed.
Error: Can not connect host.
Mail delivered Failed.
20/08/2004 21:06:21
DNS Query: Try to get mail exchange host information...
DNS server: 80.58.0.33, 80.58.32.97
Get 1 MX host information.
10 mx.ig.com.br
Try to deliver message to mx.ig.com.br.
Message size: 517 Bytes.
But anyway, I've got about 20 email accounts on port 25, I would prefer them and maildirect to stay on that one, so do I need to change something in Avast?
[MailScanner]
DefaultPopServer=127.0.0.1
SmtpListen=127.0.0.1:25
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
-
indoor-footballer
If you put them all on one port, you'll get an error stating that the port is already in use.
-
I've got about 20 email accounts on port 25, I would prefer them and maildirect to stay on that one, so do I need to change something in Avast?
[MailScanner]
DefaultPopServer=127.0.0.1
SmtpListen=127.0.0.1:25
ShowTrayIcon=1
UseDefaultSmtp=0
AutoSetProtection=0
-
Try:
SmtpListen=127.0.0.1:26
and post what you get... ;)
-
Done that, but still not scanning outgoing em's :'(
-
Done that, but still not scanning outgoing em's :'(
Are you talking about the headers or the add notes into email body?
Aren't either of them present?
If you put avast and maildirect smtp port at 25, what happens?
Can you check with TCPView application what is using the port 25?
-
>Are you talking about the headers or the add notes into email body?
Both ;-(
>Aren't either of them present?
Nope ;-(
>If you put avast and maildirect smtp port at 25, what happens?
I get the error message that you see at the bottom of here:
www.goodhorizons.com/avast (Ignore the top image for now)
>Can you check with TCPView application what is using the port 25?
Just done that, the results are the 2nd and 3rd images from the top on here:
www.goodhorizons.com/avast (The entries kept jumping around a bit and they wouldn't fit onto one page, hence the 2 images)
The help is appreciated.
-
indoor-footballer, I'm reaching the end of my knowleage :'(
But, if you post a TCPView screenshot while you're trying to send the emails and list the ports by 'number' it would be easy...
If I understood well, you can send emails but you can't scan them...
-
Will this help?
http://forum.avast.com/index.php?board=1;action=display;threadid=6831;start=msg53637#msg53637 ::)
-
indoor,
Sorry I got into this post a bit late. I am Moderator over at the Off Topic and spend a lot of time reading over the posts.
Anyway, MailDirect and Avast CANNOT share the same port 25. Whichever program boots up first will grab the port and lockout the other as you have seen.
Can your send me the website link for MailDirect. I want to check into the Options or Preferences settings menu.
If you can, set MailDirect to redirect mail to server 127.0.0.1 on port 25. This may work, but I am getting the feeling that MailDirect is not capabale of "redirects" and must operate via a port assignment. In other words, it is acting as a "filter" proxy. As such, it MUST listen on a port for the "mail".
More information as to how MailDirect works may lead to a solution.
???
-
Many thanks for coming in here:
http://www.ocloudsoft.com
Also, many thanks to the previous poster, I'm now going to that thread.
-
indoor...
Quote from vendor: Mail Direct works with most e-mail programs, such as Outlook Express, The Bat, Eudora, Foxmail, and many more. It has a built-in SMTP server, which your e-mail client will use to send messages. It receives the messages from your client and then sends them directly to your recipient's mail server, bypassing your ISP's mail server. All you need to do is change the address of the outgoing mail server (SMTP) in your e-mail software from the name of your ISP's mail server to "localhost". Mail Direct will then be designated as your SMTP server
Ok, here is the way I see this. Mail Direct acts as its' own localhost receiving the email and sending it out directly which means to me that Avast cannot scan it in that manner.
Let's look at it like this. In the normal behavior, the email client sends the mail to the server for which it is configured.
When using MD, OE will send the mail to "localhost" which is MD. MD then sends it to the recipients server.
Avast does not do this. Avast MUST use your ISP server for routing.
So even if we can get MD to direct the email into 127.0.0.1, Avast will still send it to your ISP server address.
IN effect, we need to put the cart before the horse, and that can't be done. I don't know of any way to have Avast scan first, then send it to MD.
However, since I have a very curious nature (and don't give up easy, I am in contact with OC's Tech Support and asked them for a resolution....if any.
I will get back to you as soon as I hear something, but am not too optimistic at this point.
Sorry.
-
Very much appreciated - I'm a 'glass is half-full kind of guy', so I'm optimistic as well :)
Look forward to hearing back from you.