Page 1 of 1

Email bug

Posted: Sat Mar 19, 2011 11:44 am
by johngood

When using the email option during motion detection, the port is hardwired to 465 and can't be changed. The only way for emailing to work (that I can find) is to use gmail, where the port is 465. My local ISP uses port 25, but when I enter this, console reports an error saying I tried to use 465.

A google search (yawcam 465) shows a couple of other users have encountered this problem.

Easy workaround (use gmail), but I think my local ISP would be faster.

Thanks for a great piece of software,


Posted: Sat Mar 19, 2011 5:23 pm
by z3r0c00l12
Port 465 is usually the default port when you use SSL encryption, do you have that option checked?

Port 25 is used when you connect without an SSL encrypted connection, so I'm guessing in your version you have to uncheck the "SSL encryption" option in order to be able to set the port to 25.

In version 0.3.3 that I am running, I can change the port even when the option is checked, what version are you running?

Posted: Sat Mar 19, 2011 8:19 pm
by johngood
There are apparently 2 ways to do SSL encryption of SMTP sending. Use port 25 (or 587) and then send the STARTTLS command to start the SSL encryption (what my ISP wants to do), and using SSL port 465 which is already set up for SSL. My guess is yawcam switches to 465 when SSL is checked rather than issueing STARTTLS if port 25 (or 587) is specified.

SMTP AUTH over SSL on port 465


STARTTLS on ports 587 or 25

I'm not at my home PC to check, but I downloaded yawcam today, so I'm using the latest version.

Posted: Sat Mar 19, 2011 8:22 pm
by z3r0c00l12
That's what my initial guess is too, I've seen applications like Outlook, where as soon as you check SSL, it changes the port from 25 to 465, which is probably what Yawcam does like you said.

Posted: Sun Mar 20, 2011 1:56 pm
by johngood
This answers a few questions for me. I have a new ISP that uses this new technique (of SSL over port 25 using starttls). SMTP doesn't work in outlook 2003, but will work in outlook express. After this experience with Yawcam, I now understand the outlook problem. I downloaded the latest updates from microsoft update, and now outlook 2003 works.

So it would seem that yawcam will work fine with SSL over port 465, but this (newer) approach (of ssl over port 25 by using starttls has not been incorporated into yawcam as yet. The workaround is very easy: just use gmail.

Not only is yawcam great software, but it helped me figure out a separate problem in outlook 2003. This is good.

Posted: Sun Mar 20, 2011 4:23 pm
by z3r0c00l12
Thank you for letting us know, I'll ask Malun to give a look into it, he might ask you for a few debugging logs in order to fix the issue, but as you said, gmail is a good solution.

Posted: Sun Mar 27, 2011 6:34 pm
by malun
Yawcam don't change port number if the SSL-checkbox is selected. It will always use the port number specified in the "Port" text field.

I'm not familiar with how to run STARTTLS over port 25 or 587. This is something I will have to look into. But it will have to wait for some time later...

Anyhow, thanks for your feedback!


Re: Email bug

Posted: Tue Mar 11, 2014 9:56 am
by secarica
Any news on this ? I also need to authenticate with StartTLS on port 587, else the authentication fails (SSL on SMTP is not supported by my server and the nature of this application makes encryption somewhat required).

Thank you,

Re: Email bug

Posted: Mon May 07, 2018 2:25 pm
by secarica
(bump) Still nothing on this ?