Print

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

[mobne]

I don't know what to do any more.

I have tested all firmwares i can find. same in all of them.
I have tried yahoo, gmail and my ISP bahnhof. Non of them can complete the test.

I have followed instructions carful from the providers on how to set it up. Nothing works.

On my dcs-933L it works but not on my dcs-2230
Why is that? Is my camera broken? Sounds so strange.

Followed this guide also:

Procedure: Gmail
SMTP Server Address        smtp.gmail.com
SMTP Server Port           587 or 465
Sender E-mail Address      myname@gmail.com
Receiver E-mail Address    myname@gmail.com
User Name                  myname
Password                   my e-mail account password

[RYAT3]

Try full email as username? Just a guess

Joeblow@Gmail.Com
Etc

[mobne]

Try full email as username? Just a guess

Joeblow@Gmail.Com
Etc

Yes of course i use that.
I actually found the issue today.

With Gmail its compleetly necessary to use (StartTLS) and the only port that works is 587.

took me like 7 hours of testing before finding this out Yahoo never worked and not my ISP either. The strange is that yahoo worked on my dcs-933l camera, and the exact same settings it had did not work with the dcs-2230. Thats confusing.

So for some other ppl with troubles:
My setup now is:

Sender email address: emailname@gmail.com
Recipient email address: differentemailname@hotmail.com
Server address: smtp.gmail.com
User name: emailname
Password: gmail email password
Port: 587
This server requires a secure connection (StartTLS): startls ON

[Hard Harry]

FYI, here are some additional methods of configuring to send through Gmail's SMTP server. Each have their specific requirements. Might come in handy for those devices that aren't compatible with TLS.

[FurryNutz]

Setting up email on DCS series cameras FAQ - http://forums.dlink.com/index.php?topic=63536.0

[zzyzxx_x]

This is so weird.
My cam was working just fine with gmail, with the settings described.
For some unknown reason, without changing anything at all, it doesn't work any more.
And I cannot get it to work, no matter what I try! All I get is "Test error".
What really bugs me, is that I didn't change anything with the cam or the router!
Yipes.

[FurryNutz]

If it had been working and you haven't changed anything on your side of the ISP services, it could possibly be something on the ISP side of things.

This is so weird.
My cam was working just fine with gmail, with the settings described.
For some unknown reason, without changing anything at all, it doesn't work any more.
And I cannot get it to work, no matter what I try! All I get is "Test error".
What really bugs me, is that I didn't change anything with the cam or the router!
Yipes.

[zzyzxx_x]

Agreed. But how to troubleshoot that?
I know from (painful) experience speaking with anyone from Comcast is only a waste of time...

[FurryNutz]

Might try a different email account and set up from scratch and see.

[Hard Harry]

Agreed. But how to troubleshoot that?
I know from (painful) experience speaking with anyone from Comcast is only a waste of time...

I feel your pain. Both as a customer and a former employee of a similar ISP; Cox. Did Comcast customer service also get a lot worst in the last 2 years?

Anyway, what settings were you using? Also, is your camera on your Comcast home network?

Something I notice is Comcast says to use port 465 for SMTPS . This makes me think they have started using STARTTLS vs TLS on that port. The whole thing is super confusing though, if your curious, and want to know more, see this blog post.

[FurryNutz]

Harry, Let me know if any troubleshooting information needs to be added to the FAQ. I'd like the to be a central place users can go to get help on email issues. Email has been a roller coaster ride for many.

Agreed. But how to troubleshoot that?
I know from (painful) experience speaking with anyone from Comcast is only a waste of time...

I feel your pain. Both as a customer and a former employee of a similar ISP; Cox. Did Comcast customer service also get a lot worst in the last 2 years?

Anyway, what settings were you using? Also, is your camera on your Comcast home network?

Something I notice is Comcast says to use port 465 for SMTPS . This makes me think they have started using STARTTLS vs TLS on that port. The whole thing is super confusing though, if your curious, and want to know more, see this blog post.

[zzyzxx_x]

OK, so I whipped out the Wireshark to see what's going on in the cam's network segment, and...surprise!
Absolutely NOTHING. Despite the motion detection on, the cam does not send any email.  I'm not sure (yet) if the cam is not detecting motion OR it's detecting the motion but not sending the email. I'll have to figure a way to troubleshoot that next.
The video over the network works fine...

[GreenBay42]

Old thread but this still comes up. The correct way to configure your camera for email (using gmail as sender):

Sender email address: emailname@gmail.com
Recipient email address: any email address
Server address: smtp.gmail.com
User name: emailname  (do not use @gmail.com)
Password: gmail email password
Port: 465  (NOT 587)
This server requires a secure connection (StartTLS): startls ON  (SSL-TLS)

Also in most cases you will need to turn on "less secure apps" on the sender gmail account --> click here

[FurryNutz]

Updated the forum FAQ as well:
Setting up email on DCS series cameras FAQ

[marekb]

I just coinfigured 2330 camera email notifications after a long battle. The settings are:

Sender email address: emailname@gmail.com
Recipient email address: any email address
Server address: smtp.gmail.com
User name: emailname  (do not use @gmail.com)
Password: gmail email password
Port: 587 (pay attention to 587 in use for StartTLS, 465 does not work, 465 is used for SSL)
This server requires a secure connection (StartTLS): On

When this was configured, gmail sent me an alert about less secure app trying to access my email account. I then enabled less secured apps to access it and ... bingo , it works now.