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. SMTP - Notification has been enqueued

SMTP - Notification has been enqueued

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 41.2k 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.
  • D
    D
    deepb
    wrote on last edited by
    #1

    I'm using version 4.5.0

    I've created an SMTP notification channel with below parameters:
    Server=smtp.mailgun.org
    RetryCount=1
    Port=25
    TLSMode=NONE
    LocalHostName=localhost
    FromName= xxx.mailgun.org
    FromAddr=xxx.mailgun.org
    Password=<password given by Mailgun>
    MailEncoding=utf8
    IsHTML=no

    I get Status=Failure, Error message=Driver error in Send Notification test. Mailgun parameters are OK. I have tested email delivery using Windows PowerShell.

    Please help.

    1 Reply Last reply
    0
    • A
      A
      Alex Kirhenshtein
      wrote on last edited by
      #2

      Increase sever debug to level 6 (either globally or for tag ncd.smtp), then check server logs for errors. SMTP driver logs with tag "ncd.smtp".

      1 Reply Last reply
      0
      • D
        D
        deepb
        wrote on last edited by
        #3

        Log:
        2025.08.01 12:09:09.879 *D* [nc                ] SendNotification: sending message to "[email protected]" via channel "Mailgun"
        2025.08.01 12:09:09.879 *D* [nc                ] Message to "[email protected]" via channel "Mailgun" dequeued
        2025.08.01 12:09:09.879 *D* [ncd.smtp          ] Sending mail with url="smtp://smtp.mailgun.org:25", to="[email protected]", subject="subject4", login="[email protected]"
        2025.08.01 12:09:53.415 *D* [ncd.smtp          ] Call to curl_easy_perform("smtp://smtp.mailgun.org:25") failed (56: response reading failed (errno: 0))
        2025.08.01 12:09:53.415 *D* [nc                ] Driver error for channel "Mailgun", retrying in 30 seconds, 2 retries left
        2025.08.01 12:10:23.415 *D* [ncd.smtp          ] Sending mail with url="smtp://smtp.mailgun.org:25", to="[email protected]", subject="subject4", login="[email protected]"
        2025.08.01 12:11:04.017 *D* [ncd.smtp          ] Call to curl_easy_perform("smtp://smtp.mailgun.org:25") failed (56: response reading failed (errno: 0))
        2025.08.01 12:11:04.018 *D* [nc                ] Driver error for channel "Mailgun", retrying in 30 seconds, 1 retries left
        2025.08.01 12:11:34.019 *D* [ncd.smtp          ] Sending mail with url="smtp://smtp.mailgun.org:25", to="[email protected]", subject="subject4", login="[email protected]"
        2025.08.01 12:11:35.754 *D* [ncd.smtp          ] Call to curl_easy_perform("smtp://smtp.mailgun.org:25") failed (67: Login denied)
        2025.08.01 12:11:35.754 *D* [nc                ] Driver error for channel "Mailgun", message dropped

        Driver configuration:
        Server=smtp.mailgun.org
        Port=25
        LocalHostName=localhost
        TLSMode=NONE
        [email protected]
        [email protected]
        Password=<password>
        MailEncoding=utf8
        IsHTML=no

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

          (56: response reading failed (errno: 0)) - this means that we did not get some response from the mail server that we expected. "we" is actually libcurl that is used in NetXMS to work with SMTP. 
          Since you use TLSMode=NONE which means that communication is unencrypted, you can install Wireshark and check what exactly communication is happening with the server. But it could be that server expects TLS, you can try other settings of TLSMode (and port)

          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