Synology and Business Email — The Integration Pitfalls Most People Miss

Notifications that silently stop working

DSM sends email notifications for critical events: failed backup tasks, drives nearing failure, login attempts, storage warnings. These alerts are only useful if they actually arrive. SMTP configuration in DSM uses app passwords or relay settings that can break silently when a mail provider changes authentication requirements — and nobody notices until they check the logs months later and find a string of failed alerts they never received.

Microsoft 365 in particular has tightened its SMTP authentication requirements substantially. Synology devices configured with basic SMTP auth against Office 365 often stop delivering notifications after Microsoft enforces modern authentication policies — and there's no obvious error unless someone goes looking.

Active Backup for Business and email reporting

Active Backup for Business sends job reports and alerts via email. Getting these working properly requires the SMTP integration to be solid — which circles back to the same authentication issues. A misconfigured SMTP relay means backup failures go unreported, which means the first time someone notices a problem is when they try to restore something and discover the backups aren't there.

Synology MailPlus is a separate product

Some businesses run Synology MailPlus as their actual mail server. This is a legitimate setup but a complex one — and it comes with all the deliverability responsibilities of any self-hosted mail server. SPF, DKIM, DMARC, IP reputation, blacklist monitoring. A Synology that's acting as your mail server requires the same ongoing attention as any other mail infrastructure. It doesn't manage itself, and the default install is not hardened for production mail delivery.

Shared folder notifications and user accounts

DSM can notify users when shared folders change. This requires user accounts to have valid email addresses and the SMTP integration to be working. In mixed environments — where some users are on Microsoft 365, some on Google Workspace — the per-user configuration often gets partially set up and forgotten, resulting in some users getting notifications and others getting nothing.

The common thread

All of these issues have the same shape: a configuration that worked at setup time and then broke quietly as external dependencies changed. The Synology doesn't know the alerts aren't going anywhere. You don't know until something fails. A periodic check of notification delivery, SMTP authentication, and backup report delivery isn't optional — it's the only way to know the integration is still working.