Mail-enabled service-account to send alarms for unmaintained address

Sandro D'Incà 231 Reputation points
2025-09-08T12:46:44.9+00:00

hi folks

an internal alarming-solution should send e-mail-alarms over our onprem-exchange-server.

authentication for sending e-mails over the exchange-server is required (over TLS).

we would like to create a dummy-user just to send e-mails (like a "no-reply-address"). the sender-address is also not maintained (we don't want to check mails or clean-up sent messages etc.)

what is the best practice for this use case?

our exchange receive-connector does not allow anonymous users.

Thank you for some inputs :-)

Exchange | Exchange Server | Management
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Teddie-D 4,905 Reputation points Microsoft External Staff Moderator
    2025-09-09T00:42:07.74+00:00

    Hi @Sandro D'Incà 
    Thank you for posting your question in the Microsoft Q&A forum. 

    To ensure reliable and secure delivery of alarm notifications from an unmonitored address via an on-prem Exchange server using authenticated SMTP over TLS, the recommended best practice is to create a dedicated service account. Below is a step-by-step guide to help you implement this setup effectively: 

    1. Create a dedicated service account 

    Set up a dedicated mailbox-enabled user (e.g., [******@yourdomain.com]) in Active Directory and Exchange. This account will serve as the authenticated sender for alarm notifications. 
    -Mailbox type: Use a standard user mailbox, avoid shared or resource mailboxes and do not use mail-enabled users without mailboxes, as they cannot authenticate via SMTP AUTH. 
    -Authentication: This account will authenticate over TLS using SMTP AUTH. 
    -Permissions: Grant only the minimum permissions required to authenticate and send mail. 
    -Use a strong, non-expiring password, or manage credentials securely via a password vault or a managed identity solution to reduce operational risk.  

    1. Configure as a “No-Reply” Mailbox since this mailbox is not intended to receive responses: 

    -Use transport rules to auto-delete incoming mail. 

    -Or hide the mailbox from the Global Address List (GAL) to silently drop mail. 

    1. Ensure your Exchange server is properly configured to accept and relay messages from the service account: 

    -Authentication: Enable Basic Authentication over TLS or use Integrated Windows Authentication if the client is domain-joined. 

    -Permission Groups: Enable Exchange Users to allow authenticated users to send mail. 

    -TLS Enforcement: Require TLS and ensure the certificate is trusted by the client. 

    1. SMTP Client Configuration 

    -Server Address: Point your alarming solution to the Exchange server’s internal FQDN or IP address over port 587. 

    -Credentials: Use the dedicated account’s username and password. 

    -Encryption: Enforce STARTTLS or SSL/TLS depending on your Exchange configuration. 

    Additional considerations: 

    -Ensure SPF, DKIM, and DMARC records are correctly configured for the domain to avoid delivery issues. 

    -Avoid bypassing sender authentication unless absolutely necessary. 

    -Apply a retention policy to automatically delete sent items after a defined period or use transport rules to prevent saving sent items. 

    -Log and monitor the account’s activity to detect any misuse, misconfiguration, or unexpected behavior. 

    I hope this information is helpful. 


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.