Skip to content
smtp365
How it works Pricing Guides Partners Sign in
it en fr de es
Free 30-day trial

Set up email notifications on a Synology NAS

Alerts about disks, backups and sign-ins from your Synology NAS, set up in DSM.

Configure Synology email notifications in DSM 7. Recent versions separate sender setup from recipient profiles; DSM 7.0 may show the fields directly on the email tab.

Before you start

Connect your Microsoft 365 mailbox to smtp365, then create a dedicated credential in the dashboard and keep its username and password. Use these details, not your Microsoft 365 password.

Use the sender address configured for the credential: the connected mailbox or a shared mailbox verified with a test message. Any other address is rejected.

For notifications only, you can turn off saving to Sent Items in the credential settings.

Settings

  1. Sign in to DSM with an administrator account and open notifications in the control panel, then the email tab.
  2. Open sender setup. In versions that show the form directly, enable email notifications and use that form.
  3. Choose a custom SMTP server as the service provider, rather than the Gmail or Outlook options.
  4. Enter mail.smtp365.it as the server and 587 as the port, and enable the secure SSL/TLS connection for STARTTLS. Enable authentication and enter the smtp365 credential's username and password. Enter the authorised sender in the sender email address field; the display name is up to you.
  5. Save the sender configuration.
  6. In recent versions, add a recipient profile, enable it and specify email addresses and event rules. If your version has recipient fields directly on the email tab, complete those and configure events in the rules section.
  7. Save the recipient and rule settings too.

Test

Use the command to send a test email to the configured recipient or profile, and check the sending log in the smtp365 dashboard. Then check the events you have selected: disk failures, low storage space and backup results. Package notifications, such as Hyper Backup, may also require settings within the package.

If the device reports an error

Many devices show the code they got from the server. You will also find it in the dashboard's sending log, next to the message.

535

Invalid credentials

Wrong user or password, or the credential has been disabled. Copy the user and password again from the dashboard: if you no longer have the password, generate a new one. If you use port 25, check that it is enabled for that credential.

553

Sender not allowed

Each credential can only send with its own address. On the device, set the sender to the address of the connected mailbox, or of the shared mailbox you have verified.

454

Mailbox needs reconnecting

Microsoft asked for a new sign-in, for example after a password change. Open the dashboard and reconnect the mailbox: the device credentials stay the same.

451

Limit reached, try again later

Microsoft 365 or the credential's limit slowed sending down for a few minutes. Almost every device retries on its own; if it keeps happening, check the log to see who is sending so much.

552

Message too large

The message exceeds the mailbox limit, usually 35 MB. Lower the scan resolution or format, or split it into several sends.

550

Sending refused

The monthly quota is used up, the subscription is not active, or Microsoft 365 refused the sender. The text next to the code says which: if it is not clear, write to us.

The device cannot connect to the server at all? Check that the office firewall lets the chosen port out and that the device supports encrypted connections: some very old models need a firmware update.