SMTP Service Issue with Notification Center

English
1

I’m having a hard time tracking down what could be causing the email notifications to fail with the following error:

Warning 2026-07-30 17:32:06 — — localhost — Notification Center Service Account and Device Pairing [Notification Center] Failed to send a test message using SMTP Service.

I removed all my previous email server settings.
I added Google and autheticated. It fails
I added a local Mailrise docker SMTP server on the host machine. It fails.

Anyone know what’s going on and how I can track this problem down?

TS-453Be / QTS 5.2.9.3499

2

Is the Docker SMTP server getting any connection attempt from Notification Center? What do its logs say?

3

Nothing is being logged.

4

OK. So let’s trace some connection error issues then.

1.) Can you open an SSH shell to the NAS and ping or log onto the SMPT server manually?

2.) Do you have the correct DNS sever settings applied? I had an issue with emails not working from a container app and it turns out my YAML code had an incorrect IP address for my DNS server. I know your issue is different but still let’s check that the NAS has DNS correct.

5

Pinging works, no issues.

[~] # ping smtp.gmail.c0m
PING smtp.gmail.com (74.125.26.109): 56 data bytes
64 bytes from 74.125.26.109: seq=0 ttl=102 time=45.573 ms
64 bytes from 74.125.26.109: seq=1 ttl=102 time=43.193 ms
64 bytes from 74.125.26.109: seq=2 ttl=102 time=38.472 ms
64 bytes from 74.125.26.109: seq=3 ttl=102 time=44.500 ms
^C
— smtp.gmail.c0m ping statistics —
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 38.472/42.934/45.573 ms
[~] # ping 192.168.0.90:8025
PING 192.168.0.90:8025 (192.168.0.90): 56 data bytes
64 bytes from 192.168.0.90: seq=0 ttl=64 time=0.506 ms
64 bytes from 192.168.0.90: seq=1 ttl=64 time=0.619 ms
64 bytes from 192.168.0.90: seq=2 ttl=64 time=0.467 ms
64 bytes from 192.168.0.90: seq=3 ttl=64 time=0.472 ms
^C
— 192.168.0.90:8025 ping statistics —
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.467/0.516/0.619 ms
[~] #

There’s no dns settings in the yaml config file of Mailrise. But like I said, it’s not just the docker smtp server, its also googles server which is causing the same error.

6

No, I mean in the DNS settings on the NAS.

So the IP address is reachable from the NAS.

Hmm.. Why are you pinging port 8025 on address 192.168.0.90 - Is that the IP of the container or of the NAS? What port is being used for SMTP traffic? Do you have that set up correctly?

7

8025 is the smtp port for mailrise.

I solved this issue by resetting Notification Center:
/etc/init.d/nc.sh force-stop
rm /etc/config/nc/db/nc/event*
/etc/init.d/nc.sh reset

Sucks because I have to setup notifications again, but it beats chasing my tail around the SMTP failures.

New issue now is that even with “Send as text” ticked off, the emails are still being sent with HTML and causing problems with Mailrise.

WARNING:mailrise.skeleton:Notification failed: address: [ discord@mailrise.xyz ➤ discord@mailrise.xyz ] subject: [ [QNAP-NAS] Test Message ] body: [ <!DOCTYPE html PUBLI (22.6K) ]

8

Regarding the sending format error you mentioned, we’d like to look into it further to assist you. Please open a support ticket and our Support Team will help investigate. Thanks!

9

I have one open already and haven’t gotten a response.

Ticket Q-202607-44105