I upgraded from 1.2.7 to 1.3.0 and my email reminders no longer work. When I create a new calendar entry and hit save the web page eventually errors out and looks like this:
2018-01-31 01:55:58 SERVER -> CLIENT: 220 mail.myserver.com ESMTP Postfix 2018-01-31 01:55:58 CLIENT -> SERVER: EHLO
webcalendar.myserver.com 2018-01-31 01:55:58 SERVER -> CLIENT: 250-mail.myserver.com 250-PIPELINING 250-SIZE 20480000
250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-DSN 250 SMTPUTF8 2018-01-31 01:55:58 CLIENT -> SERVER:
STARTTLS 2018-01-31 01:55:58 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS 2018-01-31 01:55:58 SMTP Error: Could not
connect to SMTP host: 2018-01-31 01:55:58 CLIENT -> SERVER: QUIT 2018-01-31 01:55:58 SERVER -> CLIENT:
2018-01-31 01:55:58 smtp_connect_failed
When I try to run reminders I get something similar. Any suggestions please? 1.2.7 was working fine.
I have resolved the issue. Rather than using a LAN IP address, or the loopback (127.0.0.1) for the mail server in Webcalendar's system settings, I entered the FQDN (fully qualified domain name) that is in the TLS certificate used on my mail server (the SAN / subject altnernative name) and now it works fine.
I swear I used to use 127.0.0.1 and/or 192.168.2 before, both without having any issues, so I'm not quite sure what changed to cause my problem but it's probably best practice to use the matching host name in TLS certificate anyway.
I'd like to add SOLVED to the subject of this post but I don't see how to do that. Hopefully this helps anyone else with the same issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I upgraded from 1.2.7 to 1.3.0 and my email reminders no longer work. When I create a new calendar entry and hit save the web page eventually errors out and looks like this:
2018-01-31 01:55:58 SERVER -> CLIENT: 220 mail.myserver.com ESMTP Postfix 2018-01-31 01:55:58 CLIENT -> SERVER: EHLO
webcalendar.myserver.com 2018-01-31 01:55:58 SERVER -> CLIENT: 250-mail.myserver.com 250-PIPELINING 250-SIZE 20480000
250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-DSN 250 SMTPUTF8 2018-01-31 01:55:58 CLIENT -> SERVER:
STARTTLS 2018-01-31 01:55:58 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS 2018-01-31 01:55:58 SMTP Error: Could not
connect to SMTP host: 2018-01-31 01:55:58 CLIENT -> SERVER: QUIT 2018-01-31 01:55:58 SERVER -> CLIENT:
2018-01-31 01:55:58 smtp_connect_failed
When I try to run reminders I get something similar. Any suggestions please? 1.2.7 was working fine.
2018-01-30 09:01:01 SERVER -> CLIENT: 220 mail.myserver.com ESMTP Postfix
2018-01-30 09:01:01 CLIENT -> SERVER: EHLO perdignus
2018-01-30 09:01:01 SERVER -> CLIENT: 250-mail.myserver.com
250-PIPELINING
250-SIZE 20480000
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 SMTPUTF8
2018-01-30 09:01:01 CLIENT -> SERVER: STARTTLS
2018-01-30 09:01:01 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS
2018-01-30 09:01:01 SMTP Error: Could not connect to SMTP host:
2018-01-30 09:01:01 CLIENT -> SERVER: QUIT
2018-01-30 09:01:01 SERVER -> CLIENT: MIAt�w��S�M|- @C�Kʂ_�&FҔo���1dJ!�d2E:�=2]�B�$��?Pi�s3ff��^Fa�X�qƳ�[�֑w�fl�
A|p��_�=e ;�E�c �<�sD�j%��b����~�������X��֬�Zg��#������x �J����c��f�W�Xh�(���e��l��e�#��&���[6�]�Yл'n�L�g�Jo�FEk��;>�;!]�E�1����C���j�G����+Ṣt�n0݃ ��n���9��d��N�$���]qMoS=�z���V �= � 2018-01-30 09:01:01 SMTP ERROR: QUIT command failed: MIAt�w��S�M|- @C�Kʂ_�&FҔo���1dJ!�d2E:�=2]�B�$��?Pi�s3ff��^Fa�X�qƳ�[�֑w�fl�
A|p��_�=e;�E�c
�<�sD�j%��b����~�������X��֬�Zg��#������x �J����c��f�W�Xh�(���e��l��e�#��&���[6�]�Yл'n�L�g�Jo�FEk��;>�;!]�E�1����C���j�G����+Ṣt�n0݃
��n���9��d��N�$���]qMoS=�z���V �=
�
2018-01-30 09:01:01 smtp_connect_failed
I have resolved the issue. Rather than using a LAN IP address, or the loopback (127.0.0.1) for the mail server in Webcalendar's system settings, I entered the FQDN (fully qualified domain name) that is in the TLS certificate used on my mail server (the SAN / subject altnernative name) and now it works fine.
I swear I used to use 127.0.0.1 and/or 192.168.2 before, both without having any issues, so I'm not quite sure what changed to cause my problem but it's probably best practice to use the matching host name in TLS certificate anyway.
I'd like to add SOLVED to the subject of this post but I don't see how to do that. Hopefully this helps anyone else with the same issue.