Bottom line: Name the recipient for each notification path. Keep the nightly health message separate from the configured alert-service threshold, and require the actual response owner to confirm delivery.
\nThe TrueNAS system-email guide says that from 25.10, system emails use a configurable recipient list rather than automatically using local administrator email addresses. After the system send method is configured, those recipients receive a nightly or morning system-health email. The Email Alert Service separately specifies its Email Address and Level, whose default is Warning. The guide provides Send Test Mail to verify the system email setup. It separately provides Send Test Alert to generate a test alert and confirm the alert-service email configuration.
\nThis article addresses the two documented notification configurations, not a guarantee of mail delivery or incident response. A successful test does not establish that every future event will cross the configured severity threshold or reach an attended mailbox.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends a notification map with one row for system health and another for the Email Alert Service. Record the recipient owner, configured address, intended severity and response duty. Review the actual system recipient list after a version transition rather than assuming that an administrator account’s email field still defines it.
\nChoose a proposed controlled test recipient with the mail owner, then have the intended operational recipients confirm their own delivery after the approved configuration is saved. Keep the system-email test and alert-service test separately labeled so one successful message cannot hide an untested path.
\nReview the alert threshold against the owner’s response requirement. Do not lower it merely to generate activity without considering the resulting notification workload. Keep SMTP or OAuth credentials and authorization details in the approved secret-handling process rather than the notification evidence.
\nPreserve the previous recipient and threshold settings. Assign an owner to maintain the list when staff or response duties change. Treat a distribution list, individual mailbox and unattended service address as separate operational choices requiring a clear recipient and escalation owner.
\nProposed verification: run the documented system-mail test and the separate alert-service test under the approved plan. Record which action was used, its configured destination and whether the named recipient observed the message. Preserve a missing message as a delivery investigation instead of assuming the storage alert condition was wrong.
\nCompare the saved recipient list and alert level with the notification map. Where an actual approved alert-condition rehearsal is required, record that event separately from the test-message actions. Keep successful delivery and demonstrated human response as distinct conclusions, and leave unperformed response checks visible.
\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Name the recipient for each notification path. Keep the nightly health message separate from the configured alert-service threshold, and require the actual response owner to confirm delivery.\nSource fact: what the authority says\nThe TrueNAS system-email guide says that from 25.10, system emails use a configurable recipient list rather than automatically using local administrator email addresses. After the system send method is configured, those recipients receive a nightly or morning system-health email. The Email Alert Service separately specifies its Email Address and Level, whose default is Warning. The guide provides Send Test Mail to verify the system email setup. It separately provides Send Test Alert to generate a test alert and confirm the alert-service email configuration.\nWhat the source does not establish\nThis article addresses the two documented notification configurations, not a guarantee of mail delivery or incident response. A successful test does not establish that every future event will cross the configured severity threshold or reach an attended mailbox.\nApplicability questions\n\nWho must receive the nightly system-health message?\nWhich address and severity are configured for the Email Alert Service?\nWho actually monitors those recipients during the required hours?\nWhat separate mail-service restrictions and response procedures need review?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a notification map with one row for system health and another for the Email Alert Service. Record the recipient owner, configured address, intended severity and response duty. Review the actual system recipient list after a version transition rather than assuming that an administrator account’s email field still defines it.\nChoose a proposed controlled test recipient with the mail owner, then have the intended operational recipients confirm their own delivery after the approved configuration is saved. Keep the system-email test and alert-service test separately labeled so one successful message cannot hide an untested path.\nReview the alert threshold against the owner’s response requirement. Do not lower it merely to generate activity without considering the resulting notification workload. Keep SMTP or OAuth credentials and authorization details in the approved secret-handling process rather than the notification evidence.\nPreserve the previous recipient and threshold settings. Assign an owner to maintain the list when staff or response duties change. Treat a distribution list, individual mailbox and unattended service address as separate operational choices requiring a clear recipient and escalation owner.\nVerification and evidence\nProposed verification: run the documented system-mail test and the separate alert-service test under the approved plan. Record which action was used, its configured destination and whether the named recipient observed the message. Preserve a missing message as a delivery investigation instead of assuming the storage alert condition was wrong.\nCompare the saved recipient list and alert level with the notification map. Where an actual approved alert-condition rehearsal is required, record that event separately from the test-message actions. Keep successful delivery and demonstrated human response as distinct conclusions, and leave unperformed response checks visible.\nOfficial references\n\nTrueNAS — Setting Up System Email — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Name the recipient for each notification path. Keep the nightly health message separate from the configured alert-service threshold, and require the actual response owner to confirm delivery.\n\n## Source fact: what the authority says\n\nThe [TrueNAS system-email guide](https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/general/settingupsystememail/) says that from 25.10, system emails use a configurable recipient list rather than automatically using local administrator email addresses. After the system send method is configured, those recipients receive a nightly or morning system-health email. The Email Alert Service separately specifies its Email Address and Level, whose default is Warning. The guide provides Send Test Mail to verify the system email setup. It separately provides Send Test Alert to generate a test alert and confirm the alert-service email configuration.\n\n## What the source does not establish\n\nThis article addresses the two documented notification configurations, not a guarantee of mail delivery or incident response. A successful test does not establish that every future event will cross the configured severity threshold or reach an attended mailbox.\n\n## Applicability questions\n\n- Who must receive the nightly system-health message?\n\n- Which address and severity are configured for the Email Alert Service?\n\n- Who actually monitors those recipients during the required hours?\n\n- What separate mail-service restrictions and response procedures need review?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a notification map with one row for system health and another for the Email Alert Service. Record the recipient owner, configured address, intended severity and response duty. Review the actual system recipient list after a version transition rather than assuming that an administrator account’s email field still defines it.\n\nChoose a proposed controlled test recipient with the mail owner, then have the intended operational recipients confirm their own delivery after the approved configuration is saved. Keep the system-email test and alert-service test separately labeled so one successful message cannot hide an untested path.\n\nReview the alert threshold against the owner’s response requirement. Do not lower it merely to generate activity without considering the resulting notification workload. Keep SMTP or OAuth credentials and authorization details in the approved secret-handling process rather than the notification evidence.\n\nPreserve the previous recipient and threshold settings. Assign an owner to maintain the list when staff or response duties change. Treat a distribution list, individual mailbox and unattended service address as separate operational choices requiring a clear recipient and escalation owner.\n\n## Verification and evidence\n\nProposed verification: run the documented system-mail test and the separate alert-service test under the approved plan. Record which action was used, its configured destination and whether the named recipient observed the message. Preserve a missing message as a delivery investigation instead of assuming the storage alert condition was wrong.\n\nCompare the saved recipient list and alert level with the notification map. Where an actual approved alert-condition rehearsal is required, record that event separately from the test-message actions. Keep successful delivery and demonstrated human response as distinct conclusions, and leave unperformed response checks visible.\n\n## Official references\n\n- [TrueNAS — Setting Up System Email](https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/general/settingupsystememail/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/", "url": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Cybersecurity", "item": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "ListItem", "position": 3, "name": "Verify TrueNAS system-email recipients and alert delivery separately", "item": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/#article", "identifier": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/", "url": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/", "headline": "Verify TrueNAS system-email recipients and alert delivery separately", "description": "TrueNAS 25.10 uses configured system-email recipients rather than automatically choosing local administrators.", "abstract": "TrueNAS 25.10 uses configured system-email recipients rather than automatically choosing local administrators. Its Email Alert Service has a separate destination, severity level and test action.", "articleBody": "Bottom line: Name the recipient for each notification path. Keep the nightly health message separate from the configured alert-service threshold, and require the actual response owner to confirm delivery.\nSource fact: what the authority says\nThe TrueNAS system-email guide says that from 25.10, system emails use a configurable recipient list rather than automatically using local administrator email addresses. After the system send method is configured, those recipients receive a nightly or morning system-health email. The Email Alert Service separately specifies its Email Address and Level, whose default is Warning. The guide provides Send Test Mail to verify the system email setup. It separately provides Send Test Alert to generate a test alert and confirm the alert-service email configuration.\nWhat the source does not establish\nThis article addresses the two documented notification configurations, not a guarantee of mail delivery or incident response. A successful test does not establish that every future event will cross the configured severity threshold or reach an attended mailbox.\nApplicability questions\n\nWho must receive the nightly system-health message?\nWhich address and severity are configured for the Email Alert Service?\nWho actually monitors those recipients during the required hours?\nWhat separate mail-service restrictions and response procedures need review?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a notification map with one row for system health and another for the Email Alert Service. Record the recipient owner, configured address, intended severity and response duty. Review the actual system recipient list after a version transition rather than assuming that an administrator account’s email field still defines it.\nChoose a proposed controlled test recipient with the mail owner, then have the intended operational recipients confirm their own delivery after the approved configuration is saved. Keep the system-email test and alert-service test separately labeled so one successful message cannot hide an untested path.\nReview the alert threshold against the owner’s response requirement. Do not lower it merely to generate activity without considering the resulting notification workload. Keep SMTP or OAuth credentials and authorization details in the approved secret-handling process rather than the notification evidence.\nPreserve the previous recipient and threshold settings. Assign an owner to maintain the list when staff or response duties change. Treat a distribution list, individual mailbox and unattended service address as separate operational choices requiring a clear recipient and escalation owner.\nVerification and evidence\nProposed verification: run the documented system-mail test and the separate alert-service test under the approved plan. Record which action was used, its configured destination and whether the named recipient observed the message. Preserve a missing message as a delivery investigation instead of assuming the storage alert condition was wrong.\nCompare the saved recipient list and alert level with the notification map. Where an actual approved alert-condition rehearsal is required, record that event separately from the test-message actions. Keep successful delivery and demonstrated human response as distinct conclusions, and leave unperformed response checks visible.\nOfficial references\n\nTrueNAS — Setting Up System Email — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-29T19:49:32+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/verify-truenas-system-email-recipients-and-alert-delivery-separately/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Verify TrueNAS system-email recipients and alert delivery separately" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 521, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "TrueNAS — Setting Up System Email", "url": "https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/general/settingupsystememail/" } } ] } }