Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Help : Unable to get SMTP service to work

Help : Unable to get SMTP service to work

Scheduled Pinned Locked Moved Support
9 Posts 5 Posters 68.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    A
    augusteDOUAMBA
    wrote on last edited by
    #1

    Hi !! need help for smtp service monitoring!! I first tried to monitor the service as an object, I got the value 4 internal error in the dci section.
    Afterwards I tried to monitor the service like a DCI but I got a value of 5.
    unable to find the problem.

    Can you give me examples of creating an SMTP monitoring service via object and  via dci? THANKS

    1 Reply Last reply
    0
    • Z
      Z
      Tatjana Dubrovica
      wrote on last edited by
      #2

      We do not have SMTP service monitoring. Usually Node with SNMP is just created and credentials are correctly configured and then NetXMS is automatically detects if SNMP is no more responsing.
      If we are talking about service - we do not have special service for SMTP. But you can use telnet. I tested this approach by creating next DCI on my management node with IP of SNMP device:
      NetworkService.Status(telnet://10.5.5.11:22)

      As for the service I've just created service object under the node with SNMP with telnet + 22 port options and it is working.

      1 Reply Last reply
      0
      • A
        A
        augusteDOUAMBA
        wrote on last edited by
        #3
        thanks for the feedback.
        actually this approach with the telnet scheme on the port works.
        however there is a functionality in the network service monitoring that I was able to test before it stopped working: on a node, I created an SMTP network service and provided an email address. a test message was sent to check the status of the SMTP service. Recently this approach no longer works I have a result 4.
        I also tried with your approach by creating a dci with the curl smtp scheme and I got result 5.
        
        SMTP scheme is no longer supported?
        
        1 Reply Last reply
        0
        • Z
          Z
          Tatjana Dubrovica
          wrote on last edited by
          #4

          Sorry it's my bad. I read SNMP instear of SMTP. SMTP is supported and should work.
          DCI configuration should look like: NetworkService.Status(smtps://domain.org, [email protected], [email protected])

          From is optional named parameter, default value is taken from subagent configuration and with no changes will be "[email protected]".
          In order to debug problem you should increase debug level to 6 on agent that collects this value. You can increase debug only for "netsvc" debug tag. In my case I had error like this, having 5 as a result of DCI:
          2024.08.26 17:39:01.212 *D* [netsvc            ] NetworkServiceStatus_SMTP(smtps://domain.org): call to curl_easy_perform failed (55: RCPT failed: 554)

          In Service configuration as an object you should set destination e-mail as Request data. And you can debug errors in the same way as with previous one by increasing debug level on the agent. You will get errors like: 
          2024.08.26 18:06:52.008 *D* [netsvc            ] CheckSMTP(smtp//127.0.0.1:465): call to curl_easy_perform failed (7: Failed to connect to 127.0.0.1 port 465 after 0 ms: Couldn't connect to server)

          1 Reply Last reply
          0
          • A
            A
            augusteDOUAMBA
            wrote on last edited by
            #5

            thanks for the feedback!!  
            I have the same error as you described (call to curl_easy_perform failed + Couldn't connect to server). 
            do you know how I could solve it? 
            I'am unable  to find   the problem . the SMTP server is accessible and I even receive email  from netxms SMTP notification channel .

            thank

            1 Reply Last reply
            0
            • F
              F
              Filipp Sudanov
              wrote on last edited by
              #6

              Note that there are two options:

              NetworkService.Status(smtp://domain.org:port)
              NetworkService.Status(smtps://domain.org:port)

              Try specifying port in the metric, e.g. NetworkService.Status(smtps://domain.org:465), make sure you can connect to that port using telnet from your netxms server's command line, e.g.:

              telnet domain.org 465

              1 Reply Last reply
              0
              • A
                A
                augusteDOUAMBA
                wrote on last edited by
                #7

                HI,
                the telnet request goes through without a problem and I had already tried adding the port but nothing happened, the returned value is 5.

                Debugging for SMTP and SMTPs gives this: 
                CheckSMTP(smtp//x.x.x.x:25): call to curl_easy_perform failed (28: Operation timed out after 10001 milliseconds with 0 bytes received)
                NetworkServiceStatus_SMTP(smtps://x.x.x.x:465): call to curl_easy_perform failed (60: SSL: no alternative certificate subject name matches target host name '10.165.23.151').

                telnet on 25 and 465 port of smtp server Works

                1 Reply Last reply
                0
                • V
                  V
                  Victor Kirhenshtein
                  wrote on last edited by
                  #8

                  Hi,

                  from error message for checking smtps on port 465, looks that you have to provide server DNS name instead of IP address.

                  for port 25 - when you do telnet on that port, do you receive initial SMTP response?

                  Best regards,
                  Victor

                  1 Reply Last reply
                  0
                  • U
                    U
                    uldis
                    wrote on last edited by
                    #9

                    Hi Auguste
                    Just further on my colleagues feedback above - those " call to curl_easy_perform failed (28: Operation timed" error messages seem to be pretty notorious for resolving and there are several steps suggested, very much trial and error approach. Is there a firewall of any kind between netxms server and your mail server or on either of node themselves? If yes, please try to disable it and perform a new test. If it still fails then you may wish to set up concurrent tcpdump on server and also on mail server, then perform another test and see with Wireshark if any packets are reaching and where the delay is.

                    1 Reply Last reply
                    0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    Powered by NodeBB Contributors
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Users
                    • Groups