Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Shaeric]

For some odd reason, my settings for my email notification does want to work on this device. I have 2 other devices (phone system, server) that gives me email notification without issues. It uses port 25, typed in my username, password multiple times but no go...Upgraded to Firmware 1.01 and thinking of using GMail instead to see if I get any luck. Anyone tried it with GMail? If so what are the settings?

[D-Link Multimedia]

I have used Gmail

smtp.gmail.com

username: your_name@gmail.com
password: yourpassword

That is it.

[Rex Kramer]

I had E-mail Alerts working fine under Firmware ver 1.00.  Were you having trouble under ver. 1.00 ??

I upgraded to Ver. 1.01 and using the exact same settings E-mail Alerts wouldn't work.  I just get the Test Result: failure message.

After hours of monkeying with it, Tech Support had me downgrade back to ver 1.00 and it works again.

Anyone else having E-mail Alert problems?

[thattallguy]

I have firmware version 1.01 and I have the following settings set and working.

ACCOUNT METHOD:  Account
USERNAME:  <my username without @gmail.com attached>
PASSWORD:  Your normal password
SMTP SERVER:  smtp.gmail.com
SENDER EMAIL AND RECEIVER EMAIL:  username@gmail.com <in this case you use the @gmail.com suffix>

Then test it.  It took me a few times to get the settings correct, but those worked for me.

[Rex Kramer]

Thanks for the info thattallguy.  Doesn't gmail use port 465 for its SMTP server?  Does that mean the 321 now (ver 1.01) uses port 465 for SMTP for Email Notification?  It used to use port 25.

My SMTP server on port 25 worked in ver 1.00 but wasn't working in ver 1.01, I will upgrade the firmware again and see if Gmail works as an SMTP server.

[nscott]

Same problem here.  When I configure email notification to use my gmail address, it work just fine.  When I configure it for my ISP's smtp server, the test fails.  I'm running firmware v1.01.

I checked my router logs.  When configured for gmail, the outbound connection goes to port 587.  Gmail normally uses port 465 for smtp.  Apparently port 587 works too.  When configured for my ISP's smtp server, the outbound connection goes to port 25.

There is obviously some logic under the covers in the DNS-321 which determines what port to use based on the smtp destination. I also wonder about the authentication schemes.  My ISP uses ID/password authentication, but does not use SSL.  Gmail uses both server authentication and SSL.  No of these items appear in the browser interface for the DNS-321.  So, it's trial and error to see if you can get email alerts to work.

One other oddity - I also have a DNS-323.  The email notification GUI looks the same as the DNS-321.  However, when I use my ISP's email configuration, the alert emails work!

Sounds like the DNS-321 team should go have a look at the DNS-323 code and do a firmware update.

[czhower]

E-mail is failing for me in 1.01 as well. I havent debugged it too closely, but the few times I tried with settings that should have worked, they didnt..

[peridoc]

I run my own remote mail server and I have it running on a non port 25 port.  My home ISP blocks all port 25 traffic to any mail server other than their own.  It would be nice if the email interface let the user specify a custom port to use either in the format "mailserver.com:xxxx" or as a separate entry blank so that I could use my own mail server.

[czhower]

Many ISPs block 25. You can tunnel a port.

Would be nice if DLink added it, but given DLink's history especially on models they consider older like the 321 we are lucky if we'll see more bug fixes let alone simple needed features.

[fordem]

Would be nice if DLink added it, but given DLink's history especially on models they consider older like the 321 we are lucky if we'll see more bug fixes let alone simple needed features.

Talk about mis-information.

Just so you're aware of it - the DNS-321 is not that old.  It's been on the market for a mere six months now, and D-Link is still providing firmware upgrades which both fix bugs and add features to the older DNS-323, which was released in 2006 - so it's been on the market for over two years now.

The current release for the DNS-323 is 1.05, with 1.06 about to be released any day now, and there is a request list for 1.07 - if you're sufficiently interested in knowing what bug fixes and new features are contained in the 1.06 release, take a trip over to the DNS-323 forum and look at the stickies.

Edit - actually - it seems I misspoke - the 1.06 release came out today - it doesn't materially change the point I was making, firmware development for the older models is quite obviously an ongoing process.

[nrf]

while that is great, it does not help those of us who are underwhelmed by this product. does it mean we can expect it to take years to have the weaknesses addressed? I was hoping not to have to run a media server and itunes server once I got this but find I would have to reformat my whole collection for it to do the advertised function. others can't get their 1.5tb drives to work, etc. mine also loses several minutes of time each day. etc.

you can't blame us for being antsy as to the level of seriousness on the part of the manufacturer given how long it took for the first firmware update and its lack of delivering on the advertised fixes.

nrf

[czhower]

The 323 is getting focus and the 321 has a recent update. Yet DLink has a long history of ignoring products and support and the 321 apparently get some, but don't expect much. I've been through this with a DLInk Media center and other products. DLink focuses on maintaining a few core products and the others are lucky if they get table scrap bug fixes.

Lets forget the bugs - just essentials like non port 25 email, ability to add users to more than on group, name a share, etc... Even for a budget NAS these are all features that should be there or addressed. They are not there now and based on DLinks history its unlikely they will add these or other such items.

[Freeman]

I had the same issue with the SMTP notifications. I had a DNS 323 and when my storage was filled, RAID 1 with two 1TB drives, I bought a DNS 321 with two 1.5TB drives. I didn't need the USB port or bit torrent client and the DNS 321, at the time, was the only inexpensive NAS with firmware support for 1.5TB drives.

So far I've encountered with the DNS 321 the 94% formatting issue, a recurring issue where my DNS 321 just powers down suddenly and without warning, the email alert test failed issue and the disappearing All Accounts check box when creating shares.

I found that the SMTP issue does work but behaves differently. I use my ISP SMTP server and they permit anonymous SMTP relaying. With the DNS 323 these web fields are displayed the same way as those on the DNS 321:

Login Method :   (*) Account   ( ) Anonymous
User Name : firstlast
Password : emailpassword
SMTP Server : SMTP.isp.com
Sender E-mail :   firstlast@isp.com
Receiver E-mail : firstlast@gmail.com

and it worked with these settings for the DNS 323 with firmware 1.05 so I thought, incorrectly, that it would work the same way with the DNS 321 if I just entered them that way as well. I had already updated the DNS 321 to firmware 1.01 so my 1.5TB drives were supported... Finally I found by playing around with the settings I had to check Anonymous to get it to work.

Login Method :   ()Account  (*) Anonymous
SMTP Server : SMTP.isp.com
Sender E-mail :   firstlast@isp.com
Receiver E-mail : firstlast@gmail.com

This does cause other issues, though, as I use the Gmail Checker 1.3 Vista Sidebar for email alerts. The email alerts from the DNS 321 arrive as (Unknown Sender) and do not show up in the Gmail RSS feed. So, though my Vista gadget displays 1 new message it does not show any additional information. I have to click on the 1 New button on the gadget to open a browser window to see who sent the email. It's a nuisance.

Hope this helps those of you with an ISP that permits this kind of relaying. D-Link should add this to their bug list, though, the ability to add a sender display name even though the authentication itself doesn't require a username / password.

I'd also like to note that I've recently updated to the new 1.06 firmware for the DNS 323 and it has this issue as well. I had to set it to anonymous to get it working just like I did with the DNS 321 and just like the DNS 321 the emails sent to the destination address do not contain anything in the FROM: field.