Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot connect to SMTP host for notifications

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 1.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ?
      Guest
      last edited by

      I'm trying to setup Notifications in the Advanced settings, but logging shows the SMTP server cannot be contacted.
      This is with a iCloud account as well as a Outlook.com accounts.

      Messages in the logs are as follows:

      php-fpm[250]: /system_advanced_notifications.php: Could not send the message to address@me.com – Error: could not connect to the host "smtp.mail.me.com": ??

      php-fpm[249]: /system_advanced_notifications.php: Could not send the message to address@me.com – Error: could not connect to the host "smtp-mail.outlook.com": ??

      Both SMTP settings use port 587 and SSL/TLS. Using STARTTLS didn't matter.

      Outbound NAT is the default settings. Never touched those.

      Interface Source Source Port Destination Destination Port NAT Address NAT Port Static Port Description
      WAN  127.0.0.0/8 * * * WAN address * NO Auto created rule - localhost to WAN

      Anyone got an idea what I'm missing here?
      Don't need it for anything special other then for version upgrades mainly, but would be nice to have it working.

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Some mail servers (Microsoft-related mostly it seems) need authentication mechanism "LOGIN" rather than "PLAIN".
        PLAIN is hard-coded currently. I made a change to also support LOGIN with these 2 commits:
        https://github.com/pfsense/pfsense/commit/c4249322d922901862719cc2e4c269351ed2c82c
        https://github.com/pfsense/pfsense/commit/305856e8fb19495e0543e0d74216117aac1d4bd8

        Although they show 4 Jan 2015 (when I submitted them) I don't think they were actually committed until after 2.2-RELEASE.

        You could try applying those changes, then select authentication mechanism "LOGIN" from the Notifications tab - maybe you will get some joy?

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          I will give these a go later today or tonight.

          Thanks for the links. I will report back here on the results for both SMTP servers.

          1 Reply Last reply Reply Quote 0
          • V
            Videonisse
            last edited by

            @weust:

            I will give these a go later today or tonight.

            Thanks for the links. I will report back here on the results for both SMTP servers.

            Did you get this working?

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.