Re: [courier-users] Build 20170309 of Courier packages

2017-03-15 Thread Gordon Messmer
On 03/15/2017 06:17 PM, Sam Varshavchik wrote: > Ok, this actually turned out to be a small typo. Fixed in the > just-uploaded 20170315, and it builds for me. courier-unicode does build. However, I'm unable to build the new courier package with it installed (also under mock).

[courier-users] Courier build 20170315

2017-03-15 Thread Sam Varshavchik
Download: http://www.courier-mta.org/download.html Changes: - Fix TLS peer hostname verification issue caused by CNAME records. pgpqnefY9mxD_.pgp Description: PGP signature -- Check out the vibrant tech community on

Re: [courier-users] Build 20170309 of Courier packages

2017-03-15 Thread Sam Varshavchik
out to be a small typo. Fixed in the just-uploaded 20170315, and it builds for me. pgpsFJiX7PdJ6.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech si

Re: [courier-users] Build 20170309 of Courier packages

2017-03-15 Thread Gordon Messmer
On 03/11/2017 11:20 AM, Sam Varshavchik wrote: > • A few more tweaks to the courier-unicode configuration script. Building in mock fails on CentOS 7: https://paste.fedoraproject.org/paste/knoYv8gNHfxhfF3flIz6EF5M1UNdIGYhyRLivL9gydE=

Re: [courier-users] Amazon SES "/SECURITY=REQUIRED set, but TLS is not available"

2017-03-15 Thread Sam Varshavchik
SZÉPE Viktor writes: Thank you for your answer. $ grep ^TLS_VERIFYPEER /etc/courier/* /etc/courier/courierd:TLS_VERIFYPEER=NONE /etc/courier/esmtpd:TLS_VERIFYPEER=NONE Look in /proc and verify what TLS_VERIFYPEER is set to. This is a certificate verification error, and TLS_VERIFYPEER=NONE

Re: [courier-users] Amazon SES "/SECURITY=REQUIRED set, but TLS is not available"

2017-03-15 Thread SZÉPE Viktor
Idézem/Quoting Sam Varshavchik : > SZÉPE Viktor writes: > >> 6) telnet email-smtp.us-west-2.amazonaws.com 587 >> 220 email-smtp.amazonaws.com ESMTP SimpleEmailService-1868680227 >> MmKC14V2dPS1oRPRtSjF >> >> Courier says: /SECURITY=REQUIRED set, but TLS is not available >>

Re: [courier-users] Amazon SES "/SECURITY=REQUIRED set, but TLS is not available"

2017-03-15 Thread Sam Varshavchik
SZÉPE Viktor writes: 6) telnet email-smtp.us-west-2.amazonaws.com 587 220 email-smtp.amazonaws.com ESMTP SimpleEmailService-1868680227 MmKC14V2dPS1oRPRtSjF Courier says: /SECURITY=REQUIRED set, but TLS is not available Could it be that Courier compares the SMTP banner

[courier-users] Amazon SES "/SECURITY=REQUIRED set, but TLS is not available"

2017-03-15 Thread SZÉPE Viktor
Hello! I hope Amazon SES is "supported" by courier. 0) courier 0.73.1-1.6 libssl 1.0.1t-1+deb8u6 1) SES requires STARTTLS, so without /SECURITY=REQUIRED SES says: 530 Must issue a STARTTLS command first 2) TLS_VERIFYPEER=NONE in courierd 3) openssl s_client -connect