D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: MosaicPaul on December 31, 2008, 02:02:40 PM
-
I just purchased a DNS-323, updated its firmware to version 1.05 and started testing it, finding that email notification seemed to work fine. The next day I updated to version 1.06, which was just released on that day, and found that email notification no longer worked. After posting to forum.dsmg600.info I found that most others who have updated to version 1.06 have the same problem, and that the bug was recognized in beta version 1.06b65 and apparently not fixed for the release version 1.06.
You can find users' characterizations of the problem in the forums, on these threads:
http://forum.dsmg600.info/t3530-Email-problem-with-version-1.06.html
http://forums.dlink.com/index.php?topic=3221.msg17649#msg17649
http://forum.dsmg600.info/p24398-Today-10%3A09%3A10.html#p24398
My experience is that email notification doesn't work even though I've tried to send to two different outgoing email servers.
In one the account information is:
User Name="name@domain.net"
SMTP Server = "smtp.att.yahoo.com"
and sender and receiver email addresses are the same, "name@domain.net". In the other the account information is:
User Name="name"
SMTP Server = "xx.xx.xx.xx" (ie.e, the address of server on our business LAN)
and sender and receiver email addresses are the same, "name@domain.com".
For both these cases when I reinstall FW v1.05 it works, but v1.06 does not. I also tried different sender and receiver email addresses. Unfortunately, I don't have an anonymous-login SMTP server to check whether an anonymous login rather than account login works.
My choices appear to be either to:
1. forgo email notification,
2. roll-back to 1.05, or
3. try to work around the bug and get email notification working in v1.06.
I hope that someone has characterized the bug enough that it can be worked around. Maybe there's a secret to getting it to work? Maybe it depends on how the drives are configured (RAID1 in my case), or whether users and groups are set up (not yet for my box). Or maybe it's an authentication problem.
I can install fun_plug to start telnet so that maybe I can get more info out of the box about what really is failing. Is there an email log file that can be enabled and read? The "Test result: Failure" message couldn't be more uninformative!
-
I just purchased a DNS-323, updated its firmware to version 1.05 and started testing it, finding that email notification seemed to work fine. The next day I updated to version 1.06, which was just released on that day, and found that email notification no longer worked.
I'm having the same problem with 1.06. Email worked with 1.05 but won't with 1.06.
-
Me too
-
Yep - the same here and as the firmware has the same time stamp as the 1.06b65 (beta ;D ) I assume it is the same Firmware.
-
Have a look at this thread:
http://forums.dlink.com/index.php?topic=3425.0
I suspect there is an issue with the 'Account' E-Mail Notification option but I can't confirm for certain as there is no logging in the DNS without performing some kind of 'mod'.
Cheers,
-
Yep - the same here and as the firmware has the same time stamp as the 1.06b65 (beta ;D ) I assume it is the same Firmware.
Read this: http://forum.dsmg600.info/p24398-Today-10%3A09%3A10.html#p24398
and this: http://forums.dlink.com/index.php?topic=3221.msg17649#msg17649
-
Thanks Tilly, I don't know how I missed the other thread on this forum -- I should have posted to that instead of starting this one. I don't see a way to combine them; that would be a nice feature for this board.
In any case, I didn't see anything there that sheds enough light on the bug to characterize it well enough to get it working for me. For me, email notification doesn't work whether or not the user name contains a "@", whether I'm sending to an outside isp or to an internal ip address. The only thing I can't test is anonymous sending.
I hope D-Link understands the problem better than I do!
-
I tried setting up the DNS-323 to email me when certain events ahppen. After testing the vdevice I find that the device will fail in this respect. All the information is correct.
Cheers,
Lucid