NOd32 v.2 and Becky Mail

Hello,

First off let me say I tried looking thru all the help file and I even wrote down all the setting from version 1 before I installed version 2. And Version 2 seem to be working fine as far as updates, NOD32, AMON and everything else.

But when I try to check email I get the old "failed to connect to mail server" error. I went did a system restore which reset it back to version 1 and I can check email fine. So I installed version 2 again. Still no email.

Under version 1 had it set as "account listens on 10700 and a redirect address. Under email scanning in IMON I put the same number (10700). It still does not work.

I also saw this in the logs:

Time    Module   Event   
6/12/2003 18:10:55 PM   Kernel   Failed to initialize scan support for archives. Email and archive scanning will not work.   


Anyone using Becky mail and NOD32 v.2 who could tell me how to set this part up?

Thanks
Logan

 

I may not have your answer, but until someone more knowledgeable comes along have a look at the below links from the Eset web-site:

http://www.nod32.com/support/ans/v1tov2.htm

and

http://www.nod32.com/support/ans/mail_srv_chg.htm


Basically in my Outlook Express program I had to revert back to my pre-NOD32 configuration for the mail incoming server and port number (Now that was me - may not be you).

I'm not familiar with Becky e-mail. I'll have to give it a look see sometime.

 

I am using it now with all betas with Becky

You have to change the pop server back to the original one - its not localhost anymore, but pop........

As far as I know it will work using port 110 but I think it should do so with 10700 too.

Please check if you have changed your popserver - the emailcheck is not via proxy anymore

Ruben

 

Alaska / tosbsas

Hey thanks for the help I read the links ( a bit confusing on the 2nd one).

I did change my pop server name and I can now receive email again. Only problem is it seems I must use 110 and not 10700 as I was able to before.

I was using 10700 as a few folks in the old Becky Forums suggested doing that as a security measure. If anyone can get something other than 110 to work I would sure like to know.

Again thanks for the help.

 

The new IMON doesn't work as a proxy, so it doesn't open any port on your local computer, so there is no such thing to change. You will connect to your mail provider at port 110, and IMON will monitor that traffic (it monitors the port specified in IMON, and it's VERY unlikely that you'll ever get POP3 traffic over another port).

Best regards,
Anders

 

anders,

Thank you. I'll just leave it at 110 as it is working and that is what matters most

Logan

 

Hey how abou using spampal too --)) than you set your port in becky on 10700 and let spampal check there --))

I know its not what you want - but ... --))

Ruben

 

tosbsas,

Not sure what spampal is. And are you saying you could then put Becky at 10700? I have no problem leaving it at 110 if that is what most folks do. Again I only changed it because some folks at the Becky Forums suggested it (I also believe Mickey The Man shows a port number like that in his NOD32 set up examples on his web page and I think he also uses Becky).

Logan

 

spampal is one of the best antispam tools I have seen. Works like a charm with Becky, there is even a plugin.

http://www.spampal.org/

Is the url - you can use the betas - they work just fine. There is a page on how to set it up with becky. If you need help - let me know - best send me an email (its in the profile)

Ruben

 

tosbsas,

Sent you an email on spampal.

Thanks again,
Logan

 

sure --))

Plugins

http://www.spampal.org.uk/plugins.html

I use Regex, bayesian and html modify

For set up with Becky

http://www.spampal.org.uk/usermanual/becky/becky.html

I have set Becky to use 1110 and the spampal too - that way I don't get twice - your mail has
been checked by nod32