Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3694

SMTP SSL Auth funktioniert nicht (Mail Alerts)

Details

    • Bug
    • Resolution: Not A Bug
    • Major
    • None
    • Community Edition
    • Alerting
    • Siehe oben.
      16 GB RAM
      12 vCores, 2 Sockets

    Description

      Version Information

      Observium CE 20.9.10731 (21st September 2020)
      OS Linux 4.19.0-14-amd64 [amd64] (Debian 10)
      Apache 2.4.38 (Debian)
      PHP 7.3.27-1~deb10u1 (OPcache: ENABLED) (Memory: 128MB)
      Python 2.7.16
      MariaDB 10.3.27-MariaDB-0+deb10u1 (extension: mysqli 5.0.12-dev)
      SNMP NET-SNMP 5.7.3
      RRDtool 1.7.1
      Fping 4.2 (IPv4 and IPv6)

      Sehr geehrte Damen und Herren,

      leider funktioniert der Mail-Versand von Alerts nicht. Aus irgend einem Grund authentifiziert sich Observium nicht am SMTP-Server. Das hat zur Folge, dass Mails im Spam landen, oder greylisted werden. Im Anhang finden Sie die derzeitige Konfiguration und einen Auszug aus Mailcow (ich habe bereits backend mail und sendmail probiert; Auf dem Mailcow Screen sieht man ganz am ende "unknown" - dort müsste der authentifizierte User stehen.).
      Ferner sehen Sie den Output des Test-Tools test_alert.php. Die Debug Option -d hilft mir leider nicht weiter, da dort nichts SMTP relevantes ausgegeben wird.

      Ist die Konfiguration als solche korrekt, oder gibt es einen offensichtlichen Fehler?

      Wenn ich mich bspw. mit den selben Credentials über Outlook authentifiziere, klappts. Also an Fehlerhaften Ports/Credentials kann es nicht liegen.

      Danke im Voraus


      Translated (please use English)

      Dear Sirs,

      Unfortunately, the mailing of alerts does not work. For some reason, Observium does not authenticate itself to the SMTP server. As a result, emails end up in spam or are greylisted. Attached you will find the current configuration and an excerpt from Mailcow (I have already tried backend mail and sendmail; on the Mailcow screen you can see "unknown" at the very end - the authenticated user should be there).
      You can also see the output of the test tool test_alert.php. Unfortunately, the -d debug option doesn't help me any further, as nothing relevant to SMTP is output there.

      As such, is the configuration correct or is there an obvious bug?

      For example, if I authenticate myself with the same credentials via Outlook, it works. So it cannot be due to faulty ports / credentials.

      Thanks in advance

      Attachments

        1. observium1.PNG
          observium1.PNG
          29 kB
        2. observium2.PNG
          observium2.PNG
          10 kB
        3. observium3.PNG
          observium3.PNG
          13 kB

        Activity

          [OBS-3694] SMTP SSL Auth funktioniert nicht (Mail Alerts)

          I understand that those x were not very helpful, but I didn't want to share sensible data.

          Fortunately you were right about the mail backend was misconfigured.

          Thank you

          jank04 Jan Kleefeld added a comment - I understand that those x were not very helpful, but I didn't want to share sensible data. Fortunately you were right about the mail backend was misconfigured. Thank you

          misconfiguration

          adama Adam Armstrong added a comment - misconfiguration

          also, putting loads of xxx all over the place makes things totally unreadable, what you pasted above is basically useless, as it's not clear what's trying to talk to what, xxx talking to xxx about xxx so maybe xxx is broken?

          adama Adam Armstrong added a comment - also, putting loads of xxx all over the place makes things totally unreadable, what you pasted above is basically useless, as it's not clear what's trying to talk to what, xxx talking to xxx about xxx so maybe xxx is broken?

          BTW, your mail backend is set to "mail", not "smtp".

          Mail uses a local MTA, this is why you got a new root email after you ran the test_alert.php script.

          adama Adam Armstrong added a comment - BTW, your mail backend is set to "mail", not "smtp". Mail uses a local MTA, this is why you got a new root email after you ran the test_alert.php script.

          Alerting officially doesn't exist in CE.

          You should use test_alert.php with the -d option to get some useful output.

          We recommend using a local MTA and not using SMTP.

          adama Adam Armstrong added a comment - Alerting officially doesn't exist in CE. You should use test_alert.php with the -d option to get some useful output. We recommend using a local MTA and not using SMTP.

          Has nothing to do with snmp.

          jank04 Jan Kleefeld added a comment - Has nothing to do with snmp.
          jank04 Jan Kleefeld added a comment - - edited

          Ich glaube ich habe etwas gefunden. In mail.info log sehe ich folgendes:

          observium sm-mta[2121]: 12PGZx5p002119: to=<xxx.xxx@xxx.de>, ctladdr=<root@observium.xxx.de> (0/0), delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=256672, relay=mail.xxx.de. [5.1xx.x.x], dsn=5.7.1, stat=User unknown.

          Die Frage, die ich mir stelle ist, wieso die ctladdr nicht observium@xxx.de ist? Es gibt nur ein Postfach für observium@xxx.de, nicht jedoch für root@observium.xxx.de. Es ist aber in den Observium-Einstellungen korrekt gesetzt.

          jank04 Jan Kleefeld added a comment - - edited Ich glaube ich habe etwas gefunden. In mail.info log sehe ich folgendes: observium sm-mta [2121] : 12PGZx5p002119: to=<xxx.xxx@xxx.de>, ctladdr=<root@observium.xxx.de> (0/0), delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=256672, relay=mail.xxx.de. [5.1xx.x.x] , dsn=5.7.1, stat=User unknown. Die Frage, die ich mir stelle ist, wieso die ctladdr nicht observium@xxx.de  ist? Es gibt nur ein Postfach für observium@xxx.de, nicht jedoch für root@observium.xxx.de.  Es ist aber in den Observium-Einstellungen korrekt gesetzt.

          People

            adama Adam Armstrong
            jank04 Jan Kleefeld
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: