The forum address has changed, you have been automatically redirected. Please update any bookmarks to use the new URL.

Subscribe

Popfile + Nod32 2.0 b2

  1. 2003-03-24 14:05:07 UTC
    Has anyone had a problem using Popfile with Nod32 2.0 Beta 2?

    It works fine with 1.xx but with Nod32 2 I can't get either a telnet session to the pop port or the web interface to display.

    Help please!
  2. 2003-03-25 02:22:28 UTC
    Try changing both to a non-standard port, e.g., make pop3 111 and the ui 8081 and see if it works.

    Scott
  3. 2003-03-25 03:29:44 UTC
    I've done that, pop3 on port 112 and ui on 9090 at the moment. I've tried different combinations as well. Note that If I go back to Nod32 1.x, it works fine, but stops working when I go to 2.0b2. wperl.exe does show in the task list and I can not telnet to the pop3 port either.
  4. 2003-03-25 04:21:26 UTC
    Well, I just downloaded their manual on the pop3 filtering. It mentions that a 'new winsock layer' filter is being tested and will be released in the near future. I suspect that you are seeing that new feature in Nod32 2.0 b2 and they are now mucking around with the protocol stack.

    You'll have to get with them to see how to disable their product from interfering....

    Scott
  5. 2003-04-22 20:00:35 UTC
    Did anyone ever resolve issues with NOD32 2.0 and Popfile? I've been using Outclass but miss the history and stats from using Popfile.
  6. 2003-09-23 03:09:10 UTC
    To solve this, change the port NOD32 listens on, from the default of 110, to whatever your PopFile and client use to talk.

    This puts the AV inbetween the two, and works just fine..

    PopFile(110)---Nod32(120)---MUA(120)
< Previous | 1 | Next >

Add a Reply

This forum does not allow anonymous participation.

Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.