The tested use-case is the forgot password flow with a valid user that works with a mail server that requires credentials. The issue is around mail servers/relays that do not require authentication. ## Expected behaviour In Organization Coniguration -> SMTP Server Configuration an SMTP server "smtp.mylocalserver" is set without authentication or TLS/SSL and using port 25. The use case is a local SMTP relay that goes to the mail server. When an email is sent from GLUU, it connects over port 25 to the "smtp.mylocalserver" email server address to send the email. ## Actual behaviour In Organization Coniguration -> SMTP Server Configuration I setup the mail server or relay. When sending an email (Forget my password use-case) it looks like GLUU asks the DNS for an MX record of the target email domain (so if I have a gluu_user@gmail.com address it will look for GOOGLE.COM MX record) and try to send directly there, acting as the mail server. The network traffic never hits "smtp.mylocalserver" but instead "google .com" when trying to send. When authentication is turned on, GLUU instead goes to "smtp.mylocalserver" to send like it should, instead of acting like a mail server and trying to send directly to the email target domain.