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

    SMTP E-mail Notification Error

    General pfSense Questions
    3
    4
    968
    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.
    • K
      kiekar
      last edited by

      Hello,

      I am unable to use the SMTP E-mail notification as I am receiving an error in system logs. Could not send the message to karl@mydomain.com – could not connect to the host "mail.mydomain.com": ??

      Currently I have a mail server on my DMZ network were I can receive and send mail with no issues using port 25. The setup looks to be straight forward but I may be missing something.

      Any help would be much appreciated.

      Thanks in advanced.

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

        I guess that mail.mydomain.com resolves to the public IP of your pfSense, which is forwarded in to the DMZ.
        That loop is likely the issue.
        You could do "split DNS" - in DNS Forwarder add a domain override for mail.mydomain.com (and maybe also mydomain.com) that resolves directly to the private IP in the DMZ. Then pfSense will send its mail direct to the server in the DMZ.

        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
        • M
          muswellhillbilly
          last edited by

          Is 'mail.mydomain.com' the genuine name of your mail server? You could always try entering the IP address of your mail system instead of relying on DNS (System/Advanced/Notifications tab). The notification email address (recipient) could just remain as 'karl@mydomain.com' - or whatever the actual address really is. You also might want to check to be sure that your mail server is set to allow inbound messages from your firewall from a trusted domain - otherwise, the mail server might reject the message as spoofed.

          1 Reply Last reply Reply Quote 0
          • K
            kiekar
            last edited by

            I tried using the DNS forwarder and using the public address for mail.mydomain.com but unfortunately this did not resolve the error but when adding the private address (172.16.0.4) in the E-Mail server textbox for notification all worked fine.

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