email notification not working

[dave1892]

Hi,

I am trying to set this up with a 239 pro II.

I just upgraded to firmware 3.2.3

I try and set up email notification and send a test email just says failed - check your settings. Are there any better error messages than that?

There's no auth on my smtp server, it's a simple setup, works from windows. And to exclude a load of other possible problems, telnet from the qnap command line to port 25 on the smpt server works fine, including dns lookup.

There are a lot of posts about the notification not working. I haven't seen any solutions that work yet though.

Any ideas?
thanks
Dave

[schumaku]

I just upgraded to firmware 3.2.3...

Hi Dave,

v3.2.3 requires an interface selection for the default gateway! Are you convinced there is no connectivity issue ? Resolving the SMTP server IP from the FQDN works? -> Test using ping FQDN from the NAS shell.

Some mail servers reject e-mails if the sender e-mail is not a useable address, or there is no MX record. Some SMTP servers do not like AUTH requests if they are switched to open relays from some IP or sub-networks.

Notification is not that a difficult set-up, but must be done in accordance to the SMTP server maintainer.

-Kurt.

[dave1892]

Hi,

Thanks for the reply.

I have a static IP, and the gateway setup.

If I run ssmtp from the command line, I get

553 <admin@QNAP239> Invalid mail address, must be fqdn

So that appears to be the problem. The thing is, there are only three settings on the smtp server config screen - server port and sender. You'd think the sender would override admin@QNAP239, but no matter what you put in that sender box, it fails.

I also edited the ssmtp.conf file and set the rewrite domain to my domain, and sent from the command line, that works. The only thing it looks like to me is a bug in the generation of the email message and the overriding of the sender address/domain.

Dave

[dave1892]

Has anyone else found this problem with 3.2.3?

This looks like a bug right?

thanks
Dave

[QNAPRobert]

I. check the primary DNS server setting on NAS is a working one.

II.
Sending notification emails via a SMTP server that doesn't require authentication would fail.
That we had replicated and been working on.

[terratec]

I can confirm.
FW 3.2.3 Breaks e/mail notification on my 219Pro, 239Pro & 439Pro
FW 3.2.1 works
Have reported this by mail 2 weeks ago and have not heard anything from QNAP support.
Not good.

[jrandall]

Has there been any official response from Qnap on this problem? Is it a confirmed bug?

I have also reported this problem using the online support form (4th March) and elsewhere in this forum (viewtopic.php?f=50&t=27175) but with no response.

Other than the TS-439U systems on the latest firmware (v3.2.3 Build 0209T), I have a TS-239 Pro on an earlier version (3.1.0 Build 0627T) which works ok. My belief is that a bug has been introduced with this latest build.

For the investment our business has made in Qnap products in the last few months, isn't it reasonable to expect at last an acknowledgement when reporting a problem and to know that someone is working on the issue. So please Qnap, I would appreciate your comments.

[Don]

QNAP has confirmed this bug. It is fixed in the next release. Before you ask I don't have a date.

[dave1892]

I. check the primary DNS server setting on NAS is a working one.

I don't wish to appear rude, but I've already pointed out twice on this thread that the DNS lookup is not a problem.

II.
Sending notification emails via a SMTP server that doesn't require authentication would fail.
That we had replicated and been working on.

That presumably includes the bug when you check the auth box and fill in a random name in the user, then click on test email, and it says that it's sent it successfully but it hasn't.

Frankly, it's a pretty easy piece of code on Linux that also clearly wasn't tested before releasing the firmware. I expect a lot more from such a professional sounding/priced piece of kit. It should never have been broken so badly in the first place.

It's all very well saying there's no eta, but this is simple and urgent. I've had no emails from my data critical box since I bought it. Should I send it back as being not fit for purpose?

[terratec]

It's all very well saying there's no eta, but this is simple and urgent. I've had no emails from my data critical box since I bought it. Should I send it back as being not fit for purpose?

What can I say, I have 8 non working units !

[P3R]

For what it's worth I have email notification working consistently on a TS-410 with firmware 3.2.3 Build 0212T.

I have a SMTP server configured, port 25 and a valid email address as sender. No authentication and no SSL/TLS.

Since it does work for me, perhaps there is a workaround that could help you guys get it going in some way? To further investigate this path it would probably be helpful if Qnap could explain what the bug they've found is about?

[dave1892]

Well, that is a different build. I have 3.2.3 Build 0209T

If I don't have authentication checked, it never works. That is supposedly the bug QNAP have specified. I think there may be others, but there's little info or communication from them so who knows?

[Don]

As I have already posted. QNAP is aware of the problem and it is fixed in the next release. No eta yet.

[dave1892]

As I have already posted. QNAP is aware of the problem and it is fixed in the next release. No eta yet.

And is this

"That presumably includes the bug when you check the auth box and fill in a random name in the user, then click on test email, and it says that it's sent it successfully but it hasn't. "

the same bug, or a new one?

[Willem_K]

I have the TS459 Pro with firmware 3.2.3 Build 0209T and e-mail notification with authentication is working when I enter a valid e-mail address.

Regards.