I sniffed internal interface (DMZ) on firewall filtering packets of PRTG server during test 3, 4, 5 and 6 and catch this dump: 220 pod51028.Microsoft ESMTP MAIL Service ready at Mon, 0000 EHLO monitor.br 250-pod51028.Hello [1.228] 250-SIZE 36700160 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH 250-8BITMIME 250-BINARYMIME 250 CHUNKING QUIT 221 2.0.0 Service closing transmission channel Now, I sniffed interface a workstation with Mozilla Thunderbird and catch this: 220 pod51028.Microsoft ESMTP MAIL Service ready at Mon, 0000 EHLO [192.168.0.41] 250-pod51028.Hello [1.225] 250-SIZE 36700160 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH 250-8BITMIME 250-BINARYMIME 250 CHUNKING STARTTLS 220 2.0.0 SMTP server ready (continue...) What could I do to resolve this problem?notification-delivery office365 send-email smtp I'm having a very similar issue with the SMTP-IMAP Round Trip sensor. error:1408F10B: SSL routines: SSL3_GET_RECORD:wrong version". From my research it appears that PRTG may be trying to connect directly to port 587 when is expecting a STARTTLS command first before it begins encrypted communication.When creating the end-to-end authentication process by which a user (for example) will be authenticated, there are things to consider such as where the authentication process will be initiated, which authentication module(s) will be used in the process, and what, if any, post authentication steps will be implemented.The authentication type (where the authentication process will be initiated) is specified by appending an appropriate parameter to the login URL, or through the authentication API.ail Secure (all versions), M Guardian (all versions)The "authentication" settings in NMS (the authentication portion of a "mail route" policy) serves 2 purposes,1.to validate a user's credentials when they log in to access the quarantine.2.
Unlike validating users via SMTP where all we know is that the email address is valid or not, via LDAP we know that the email address is valid and also that it belongs to the same user!My email service is Office 365 (Exchange Online) and I get informations above with admin: Sender E-Mail: [email protected] SMTP Relay Server: pod51028.SMTP Relay SMTP Port: 587 Cryptographic method: TLS User: [email protected] Password: So, I configured on PRTG Server (Notifications Delivery): 1.Authentication "No authentication is required", SSL Method "TLS V1", Security "No encryption (use plain text)" 2.For the first purpose (validating credentials) there is no real advantage in using LDAP vs SMTP auth but for the second purpose (validating a user's existence) there are several reasons why we suggest using LDAP authentication.To understand the benefits, let's first make sure we understand what happens during user validation... Notice that for every command sent by the sending server the receiving server (NMS) returns a response.While it may have taken several minutes to reach this point in this article, the recipient validation process usually takes less than a second.Now that we understand how we validate recipients and that we will only accept mail for valid recipients, we can move on to explaining why we consider LDAP to be a superior method to validate users than doing so via SMTP.Most enterprise class email systems (Exchange, Group Wise, etc.) store user information in a directory in the form of user objects, a user object has various attributes such as a username, first name and last name, etc.Typically [email protected] the primary/default email address for the user but the mail system will usually allow for other common email address formats based on the user's first and last name or other custom email address formats.And that, my friends, is why validating users via LDAP is more desirable than doing so via SMTP.Greetings, I'm having problem sending email notifications to an SMTP relay with authentication.