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

    Notification: cannot connect SMTP-Host

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 5 Posters 1.3k 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.
    • B
      bzdega
      last edited by

      Hi,

      i want to use the notification feature but after configuring the SMTP settings, i am not able to sent a test notification. I get this error message in the system log:

      
      php-fpm[22385]: /system_advanced_notifications.php: Could not send the message to support@mydomain.com -- Error: could not connect to the host "mail.mydomain.com": ??
      
      

      But i can ping this hostname from within the pfSense.

      I use Port 587 like i do in all other mail clients. Tried other security settings, but they did not works as well.

      Is the notification thing working for someone?

      1 Reply Last reply Reply Quote 0
      • M
        muswellhillbilly
        last edited by

        Try ticking 'Enable STARTTLS' in your SMTP settings. What happens then?

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          You don't test mailservers with ping.

          1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan
            last edited by

            test a mailserver from pfSEnse.
            SSH into pfSense first - and then:

            telnet mail.mydomain.com 25

            or

            telnet mail.mydomain.com 587

            Be nice and talk to it.

            Note that many ISP block the '25' port to any destination EXCEPT their own mail servers.

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            1 Reply Last reply Reply Quote 0
            • F
              firewalluser
              last edited by

              An example of telnetting into a mailserver with different codes that might be shown by some mailservers, could also be tried from a lan side machine

              https://technet.microsoft.com/en-us/library/aa995718%28v=exchg.65%29.aspx
              https://www.port25.com/how-to-check-an-smtp-connection-with-a-manual-telnet-session-2/

              As its likely going to be coming from pfsense itself, you might need to create/allow a rule from ThisFirewall to your email server destination on which ever interface your mail server resides on. I only say this because you can see some things like DNS lookups in the fw logs and these are allowed by default, but mail server comms may possibly not be enabled/allowed by default on some/all interfaces from the firewall.

              Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

              Asch Conformity, mainly the blind leading the blind.

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