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

    SMTP Test Successful, But Error With "Real" Email

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 3 Posters 813 Views 3 Watching
    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.
    • U Offline
      urbnsr
      last edited by urbnsr

      Running pfSense CE v.2.6.0-RELEASE (amd64)

      I have email notifications setup and when clicking on Test SMTP Settings, pfSense claims "SMTP testing e-mail successfully sent" and I get the test message.

      Recently our secondary, tier 2, WAN went down and I did not get a message about it. Main WAN was up at the time. The sender and recipient are on this same server/domain. Looking in the logs and I find the entry:

      notify_monitor.php: Could not send the message to myemail@eserver.com -- Error: Failed to add recipient: myemail@eserver.com [SMTP: Invalid response code received from server (code: 451, response: Temporarily unable to process your email. Please try again later.)]

      At first, I thought this was an issue from our email server, but I find similar entries for previous events, so I am wondering what I may have setup wrong in pfSense.

      Is this problem only an issue outside of pfSense?

      Thanks.

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        SteveITS Rebel Alliance @urbnsr
        last edited by

        @urbnsr A response code means it connected. Do you have access to the mail server logs to find the entry on that end?

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
        Upvote 👍 helpful posts!

        U 1 Reply Last reply Reply Quote 0
        • U Offline
          urbnsr @SteveITS
          last edited by

          @steveits Thanks. I don't have direct access and will request more info. Since I have multiple errors in the pfSense log and no errors reported from users, I was leaning away from completely being the email server's fault.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            serbus @urbnsr
            last edited by

            Hello!

            A SMTP 451 response is typical from a server that is greylisting. I am not sure if pfsense will try to resend that message after a delay, like an MTA would. Check notifyqueue.messages
            and notices_lastmsg.txt in /var/db for the status of the notification.
            I always setup a local MTA for pfsense to relay through.

            John

            Lex parsimoniae

            U 1 Reply Last reply Reply Quote 0
            • U Offline
              urbnsr @serbus
              last edited by

              @serbus Thanks John. That's probably a better idea than what I am doing.

              I do have it working now, though. I had it testing successfully using port 465 SSL/TLS, but true notifications failed. I changed to 587 plain and notifications are being received.

              Thanks for the replies.

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