Announcement

Collapse
No announcement yet.

Eset Nod32 cannot send email alerts trough exchange 2003.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Eset Nod32 cannot send email alerts trough exchange 2003.

    Hello everybody.

    I have eset nod32 antivirus version 4.0.437. And exchange 2003
    There has a module to send email notifications if any virus is found. You can see the screenshot.

    The problem is that i no recieve any alert mails. The settings are correct because when i put them into outlook express i can send mails perfectly.

    I also try with other smtp server that i install on my local computer. It works.

    Where can be the problem ? I think nod and exchange don't communicate correctly each other. But don't know what to change.

    Thank you.
    Attached Files

  • #2
    Re: Eset Nod32 cannot send email alerts trough exchange 2003.

    My guess is, it have something to do with the authentication settings.

    Did you tried to send without authentication?

    You can also enable the logging option at your Virtual SMTP Server to check after a test at which step the communication goes into error status.

    Comment


    • #3
      Re: Eset Nod32 cannot send email alerts trough exchange 2003.

      Yes i try with no authentication. Don't work. But i want to be with authentication, because i don't want my server to be open relay for spam


      Unfortunately there is nothing in smtp log.
      I keep trying do things.

      Comment


      • #4
        Re: Eset Nod32 cannot send email alerts trough exchange 2003.

        SMTP by design is not an authenticating protocol, things like authentication were added later as SPAM started to become an issue. If you are concerned about open relaying check this technet article.

        If the NOD32 computer is not the same box as Exchange then you probably need to configure Exchange to allow that machine to relay mail through Exchange. Go to the properties of the Default SMTP Virtual Server, and click on the Access tab. Select Relay and you will see which internal machines are permitted to relay mail through Exchange and can change the settings if required. I've had to do this before for programs like Backup Exec which couldn't (in older versions) provide credentials.
        BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
        sigpic
        Cruachan's Blog

        Comment


        • #5
          Re: Eset Nod32 cannot send email alerts trough exchange 2003.

          If you are sending to an external account, then simple solution is to simply configure the application with a valid email address and then point it at your ISPs SMTP server.

          If you are sending to an internal account, then no authentication is required at all, because it is just like any other email being sent to the server - unless you have SMTP locked down - because you are using an antispam service. However I have seen some AV software block the sending of internal emails because they block local access to the port, which might be the cause of the problem. I am not familiar with Nod32 to know if it does that.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Eset Nod32 cannot send email alerts trough exchange 2003.

            Originally posted by cruachan View Post
            SMTP by design is not an authenticating protocol, things like authentication were added later as SPAM started to become an issue. If you are concerned about open relaying check this technet article.

            If the NOD32 computer is not the same box as Exchange then you probably need to configure Exchange to allow that machine to relay mail through Exchange. Go to the properties of the Default SMTP Virtual Server, and click on the Access tab. Select Relay and you will see which internal machines are permitted to relay mail through Exchange and can change the settings if required. I've had to do this before for programs like Backup Exec which couldn't (in older versions) provide credentials.
            I have success when added that test computer in relay tab.
            But if i allow relaying in my network, will i open the door from viruses to send themselves and spam if the computer is infected ?
            Also i want some outside computers to use that mail server to sending reports to me.

            @sambee.
            I have own exchange server, dont use my ISP's one. (You give me an idea to ask my ISP if they have mail server to create that special mailbox for me. )
            I create a new one mailbox and put it in nod32 settings. Dont work, i dont know why for now. But if i put that settings in outlook express i can send mails with no problems.

            Comment


            • #7
              Re: Eset Nod32 cannot send email alerts trough exchange 2003.

              Originally posted by lg911 View Post
              I have success when added that test computer in relay tab.
              But if i allow relaying in my network, will i open the door from viruses to send themselves and spam if the computer is infected ?
              Also i want some outside computers to use that mail server to sending reports to me.
              That's why the relay tab is there, to specify ONLY the machines internally that are allowed to relay via Exchange. If that list only contains the Nod32 server then only that server can relay mail via Exchange, so a virus infected workstation will not have relay permission.
              BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
              sigpic
              Cruachan's Blog

              Comment


              • #8
                Re: Eset Nod32 cannot send email alerts trough exchange 2003.

                If you are sending to an internal address you shouldn't need to configure relaying at all.
                It isn't clear if you are sending to an external or internal email address.

                For most ISPs you do not need to have a mailbox to use their SMTP servers for outbound email.

                Simon.
                --
                Simon Butler
                Exchange MVP

                Blog: http://blog.sembee.co.uk/
                More Exchange Content: http://exchange.sembee.info/
                Exchange Resources List: http://exbpa.com/
                In the UK? Hire me: http://www.sembee.co.uk/

                Sembee is a registered trademark, used here with permission.

                Comment

                Working...
                X