outdated SSL ciphers

[fk519]

My email provider tech support suggested my problem with motion detection emails may be outdated SSL ciphers in Yawcam.
If this is case, can this be fixed?

[malun]

Yes, it looks like some email providers have decided to not support some older crypto ciphers that Yawcam still uses. So the ciphers needs to be updated in a new release of Yawcam.
There is however a workaround: To manually replace/update the mail library used in Yawcam.

Follow these steps for a fix:
0) Exit Yawcam
1) Download the file mail.jar from: https://www.yawcam.com/files/mail.jar
2) Copy mail.jar into Yawcam's lib directory. This would typically be: C:\Program Files (x86)\Yawcam\lib
3) Replace the old mail.jar in this folder. (You will probably need admin rights for this)
4) Start Yawcam and try to send mail again.

This fix has been confirmed to work with Yahoo's smtp server.

/malun

[franc]

Thanks! This worked

I didnt use Yawcam for a good while and re-opened it but noticed that email is not working.
So I found this thread and changed the mail.jar and now it works

The email server is my own, I guess I configured it to meet with the latest security requirements, so old cryptos are not accepted or so.
Dont know exactly, but much better to use actual crypt standards. So you could do an update to e.g. 0.7.1 with a fix on this?
Thanks!

By the way: Yawcam is a great application! Many many features and all free! Thanks for that!

frank

[lauryfriese]

Website browsers automatically check the SSL of the website every time you try to connect to it. It’s a way to prove that the accessed website is genuine and has implemented the correct protocol to secure your connection. Drift Boss

[malun]

Just to let you know... Yawcam version 0.8.0 has updated SSL ciphers and don't need the workaround described above.
/malun

[PaulYawcam]

19/04/2024

Hi all,

Great software btw!!!

I have a problem sending emails with last 0.8.0 version:
I have tried with 2 google accounts (1 pro, 1 personal) and 1 Hotmail account.
I have double cheeked the settings and reinstalled the software.

Both SMTP
smtp.gmail.com 465
smtp-mail.outlook.com 587
No flood control.
To and from both correct.

motion event report:
Actions taken:
E-mail sent to: xxxxxxx

This is fine but never got an email.
I have used 2 different networks (1 no firewall).
Any suggestion?

Take Care

Paul

[malun]

What does the log say? Do you get any error messages in the console?
/malun

[PaulYawcam]

Hi Malun,


Thanks for your reply.

My bad I did not set the log...
no error in the console.

windows version : Win10 Home 22H2
java 8 411 latest for my win build.
--------------------------------------
Yawcam log file, (2024-04-22 07:49)
--------------------------------------

[22/4 07:49] Yawcam started
[22/4 07:49] Settings loaded
[22/4 07:49] Language: English
[22/4 07:49] Warning: System Events not supported in this java version. Upgrade to java 9 or above!
[22/4 07:49] Mail: Could not connect to SMTP host: smtp-mail.outlook.com, port: 587
[22/4 07:50] Mail: Could not connect to SMTP host: smtp-mail.outlook.com, port: 587
[22/4 07:50] Mail: Could not connect to SMTP host: smtp-mail.outlook.com, port: 587
[22/4 07:52] Settings saved

i can ping it
C:\Users\Administrateur>ping smtp-mail.outlook.com

Envoi d’une requête 'ping' sur svc.ha-smtp.live.com [40.99.220.134] avec 32 octets de données :
Réponse de 40.99.220.134 : octets=32 temps=12 ms TTL=243
Réponse de 40.99.220.134 : octets=32 temps=12 ms TTL=243
Réponse de 40.99.220.134 : octets=32 temps=12 ms TTL=243
Réponse de 40.99.220.134 : octets=32 temps=12 ms TTL=243

Statistiques Ping pour 40.99.220.134:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 12ms, Maximum = 12ms, Moyenne = 12ms

C:\Users\Administrateur>ping smtp.gmail.com

Envoi d’une requête 'ping' sur smtp.gmail.com [142.250.110.109] avec 32 octets de données :
Réponse de 142.250.110.109 : octets=32 temps=16 ms TTL=105
Réponse de 142.250.110.109 : octets=32 temps=16 ms TTL=105
Réponse de 142.250.110.109 : octets=32 temps=18 ms TTL=105
Réponse de 142.250.110.109 : octets=32 temps=16 ms TTL=105

Statistiques Ping pour 142.250.110.109:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 16ms, Maximum = 18ms, Moyenne = 16ms

hope helps.

Take care

Paul

[PaulYawcam]

hoops i did it again!!!

console did reported the error.
I have confused the motion events report with the console ouput.

console output

Capture console.PNG (32.35 KiB) Viewed 100 times