Common errors

Message or observation	Check and remedy
Mail server sign-in rejected	Check the SMTP username and password. Make sure the account is permitted to sign in over SMTP.
Mail server connection failed	Check the port, encryption type and relay authorization. A direct TLS port requires TLS, a STARTTLS port requires STARTTLS.
Mail server rejected the recipient/sender	Check the address and SMTP relay authorization. A previously successful connection test has not yet checked this delivery.
Server certificate is not trusted or does not match the server name	Use the DNS name matching the certificate and, for an internal CA, add its PEM certificate.
Qisutu rejected the access key	Copy the key for the selected connection again; check its validity in Qisutu.
Access key does not match this connection or lacks permission	Use the connection address and key from the same connection.
Qisutu connection not found	Check the complete event address, the connection’s active state and support for Qisutu Monitoring in the add-on.
Connection does not belong to system type Qisutu Monitoring	Use a connection of the appropriate type in the Qisutu add-on.
Qisutu is limiting requests	The event remains queued and is transmitted again later.
Connection test successful, but no notification	Save the settings, enable the delivery channel and check the device scope. Then test an actual state change. No recurring notification is generated for an unchanged problem.
Qisutu accepted the event, but no new ticket is visible	Check processing and rules in the separate Qisutu add-on. Accepted events may also be ignored or suppressed there.