On Oct 17, 2013, at 3:31 AM, Andreas Meyer <anme...@anup.de> wrote: > Warren Baker <war...@decoy.co.za> wrote: > >> On Thu, Oct 17, 2013 at 11:43 AM, Andreas Meyer <anme...@anup.de> wrote: >>> I thougt if I set "Notification E-Mail auth username (optional)" >>> with the password, some kind of SASl is used. If I set it, the log says: >>> >>> php: /system_advanced_notifications.php: Could not send the message >>> to i...@anup.de -- Error: server does not require authentication >> >> This means the smtp server does not advertise SMTP AUTH. The smtp >> connection tests for this smtp extension and if it does not find AUTH >> it returns that error. >> That smtp username and password is then used in one of the supported >> authentication methods (eg login, plain, cram-md5 etc.). Its not for >> SASL. >> >> You can double check the server by doing a telnet to the port (25 or >> 587) and sending EHLO fqdn and see what smtp extensions are supported. > > allright, I guess the > 250-AUTH PLAIN LOGIN CRAM-MD5 DIGEST-MD5 > 250-AUTH=PLAIN LOGIN CRAM-MD5 DIGEST-MD5 > was not offered because of the smtpd_enforce_tls=yes and the MTA > awaited a starttls first. I'll check that again.
You can test after starttls with: openssl s_client -connect fqdn:25 -starttls smtp Then EHLO somefqdn _______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
