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

    General pfSense email messages don't share hostname or originating information

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 112 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.
    • A
      atlassol
      last edited by

      I have a fleet of pfSense firewalls installed at client sites. We use noip as our DDNS service and mailersend.net as our SMTP gateway for outbound messaging. All fleet appliances are built from a templated XML file.

      Our own customized reports are templated to tell us what server is sending the report (eg. "This is a periodic report from pfSense at DanDream.clients.xxx.com") in both the Subject line and the message body. (xxx,com being a redacted value of our own domain).

      But we just discovered that the default pfSense template (for reboot announcements as an example) don't! We had an appliance send us the following email:

      Subject line: pfSense.clients.xxx.com

      with a body just containing the lines:

      Notifications in this message: 1
      ========================
      08:18:36 Bootup complete

      Hardly useful information to determine WHICH machine rebooted!

      Apparently the "Hostname" field from the System/General Setup page is not prepended to the Subject line by the system's default messaging, only the Domain field is included.

      Does anyone have a way to change this so we don't have to manually query the entire fleet for which machine has a new uptime that matches the reboot message?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The hostname is in the message subject, is that not sufficient?

        I'm sure the report could be patched to include it. I'm not sure if that would be accepted into the base though, that sort of change might impact others already parsing email.

        A 1 Reply Last reply Reply Quote 0
        • A
          atlassol @stephenw10
          last edited by

          @stephenw10

          Thanks for the response.

          In reviewing your response and looking through my configurations, this one firewall did NOT have a valid Client name set and was missed from my template configuration when the firewall went into service.

          I apologize for taking up yours and anyone else's time. I feel like a Newby today.

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