Hi Eric,
Hi Quinn,

thanks a lot for your help. I couldn't find the error, but hope on your patch.

I have no other server to help my customers, so they can only have the choice to use roundcube until it is fixed.
Maybe the attached log from testssl.sh can help a bit?
I couldn't find a way to set the cipher-order in qmail. Maybe I haven't searched in the right list- archives?

Andreas




Am 24.10.22 um 17:57 schrieb Eric Broch:
I'm going to have to write a server side patch so we can determine the problem.

On 10/24/2022 9:53 AM, Andreas wrote:
Ok, I just tried with Outlook 2019 on port 465, it doesn't work either.
It times out.



Am 24.10.22 um 17:22 schrieb Eric Broch:
did you try smtps port 465?

On 10/24/2022 9:13 AM, Andreas wrote:
#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
#TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
TCP_CDB="/etc/tcprules.d/tcp.subm.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"

exec /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
    -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


Am 24.10.22 um 17:12 schrieb Eric Broch:
cat /var/qmail/supervise/submission/run

send results

On 10/24/2022 9:03 AM, Andreas wrote:
Hi Eric,

spamdyke is only in the mix with smtp, not with submission.

andreas

Am 24.10.22 um 15:55 schrieb Eric Broch:
is spamdyke in the mix?

On 10/24/2022 7:53 AM, Andreas wrote:
It is setup to use submission, someones use starttls some automatic.



Andreas

Am 24.10.22 um 15:51 schrieb Eric Broch:
How is your SMTP set up in Outlook?

On 10/24/2022 7:50 AM, Andreas wrote:
Hi Eric,

that's right.

IMAP is OK

Andreas

Am 24.10.22 um 15:49 schrieb Eric Broch:
Sending emails would be a qmail issue wouldn't it? Not a imap issue, right?

On 10/24/2022 7:45 AM, Andreas wrote:
Hi Eric,

Yes, it is only a issue when trying to send mails.
Retrieving mails is OK

Andreas

Am 24.10.22 um 15:30 schrieb Eric Broch:
Is this only a imap issue?

On 10/24/2022 6:46 AM, Andreas wrote:
Hi Eric,

with LEGACY it still doesn't work.

I tried FUTURE and get the following in dovecot-logs:
Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small: user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, session=<HBCFFMfrgdROXk9Z>


Andreas
Am 24.10.22 um 14:24 schrieb Eric Broch:
What does this command yield?

update-crypto-policies --show

update-crypto-policies --set DEFAULT

update-crypto-policies --set LEGACY

update-crypto-policies --set FUTURE


On 10/24/2022 5:12 AM, Andreas wrote:

Hi list,

I have read the discussion and fix.
I have installed dovecot--2.3.19.1-2.x86_64 and
dovecot-mysql-2.3.19.1-2.x86_64
on RockyLinux 8

Since last update on Microsoft and Outlook they cannot send emails.

In the log I dont see any error, on the client:
Task "myuser@... - Sending: reported error (Ox800CCC1A) :
'Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or internet service provider (ISP) for additional assistance.'


Do you have any advice how I could change the server settings?

Andreas


--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com









###########################################################
    testssl.sh       3.0.6 from https://testssl.sh/

      This program is free software. Distribution and
             modification under GPLv2 permitted.
      USAGE w/o ANY WARRANTY. USE IT AT YOUR OWN RISK!

       Please file bugs @ https://testssl.sh/bugs/

###########################################################

 Using "OpenSSL 1.0.2-chacha (1.0.2k-dev)" [~179 ciphers]
 on TP-AG:./bin/openssl.Linux.x86_64
 (built: "Jan 18 17:12:17 2019", platform: "linux-x86_64")


 Start 2022-10-24 23:13:15        -->> xx.xx.x.xx:587 (send.mail,server) 
<<--

 rDNS (xx.xx.x.xx):    send.mail,server.
 Service set:            STARTTLS via SMTP

 Testing protocols via sockets 

 SSLv2      not offered (OK)
 SSLv3      likely not offered (OK), received 4xx/5xx 
after STARTTLS handshake, rerun with DEBUG>=2 or --ssl-native
 TLS 1      offered (deprecated)
 TLS 1.1    offered (deprecated)
 TLS 1.2    offered (OK)
 TLS 1.3    offered (OK): final

 Testing cipher categories 

 NULL ciphers (no encryption)                  not offered (OK)
 Anonymous NULL Ciphers (no authentication)    not offered (OK)
 Export ciphers (w/o ADH+NULL)                 not offered (OK)
 LOW: 64 Bit + DES, RC[2,4] (w/o export)       not offered (OK)
 Triple DES Ciphers / IDEA                     not offered
 Obsolete CBC ciphers (AES, ARIA etc.)         offered
 Strong encryption (AEAD ciphers)              offered (OK)


 Testing robust (perfect) forward secrecy, (P)FS -- omitting 
Null Authentication/Encryption, 3DES, RC4 

 PFS is offered (OK)          TLS_AES_256_GCM_SHA384 
TLS_CHACHA20_POLY1305_SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-SHA
                              DHE-RSA-AES256-GCM-SHA384 
ECDHE-RSA-CHACHA20-POLY1305 DHE-RSA-CHACHA20-POLY1305 DHE-RSA-AES256-CCM
                              DHE-RSA-AES256-SHA TLS_AES_128_GCM_SHA256 
TLS_AES_128_CCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256
                              ECDHE-RSA-AES128-SHA DHE-RSA-AES128-GCM-SHA256 
DHE-RSA-AES128-CCM DHE-RSA-AES128-SHA 
 Elliptic curves offered:     prime256v1 secp384r1 
secp521r1 X25519 X448 
 DH group offered:            Unknown DH group (2048 
bits)

 Testing server preferences 

 Has server cipher order?     no (NOT ok)
 Negotiated protocol          TLSv1.3
 Negotiated cipher            TLS_AES_256_GCM_SHA384, 
253 bit ECDH (X25519) (limited sense as client will pick)
 Negotiated cipher per proto  (limited sense as client will pick)
     ECDHE-RSA-AES256-SHA:          TLSv1, TLSv1.1
     ECDHE-RSA-AES256-GCM-SHA384:   TLSv1.2
     TLS_AES_128_GCM_SHA256:        TLSv1.3
 No further cipher order check has been done as order is determined by the 
client


 Testing server defaults (Server Hello) 

 TLS extensions (standard)    "renegotiation info/#65281" "EC point 
formats/#11" "session ticket/#35" "supported versions/#43"
                              "key share/#51" "supported_groups/#10" "max 
fragment length/#1" "encrypt-then-mac/#22"
                              "extended master secret/#23"
 Session Ticket RFC 5077 hint 7200 seconds, session tickets keys seems 
to be rotated < daily
 SSL Session ID support       yes
 Session Resumption           Tickets no, ID: no
 TLS clock skew               Random values, no fingerprinting possible 
 Signature Algorithm          SHA256 with RSA
 Server key size              RSA 2048 bits
 Server key usage             Digital Signature, Key Encipherment
 Server extended key usage    TLS Web Server Authentication, TLS Web 
Client Authentication
 Serial / Fingerprints        0461F2D848E49073DCBC14927D28811F5C93 / 
SHA1 BCF3B9D0C5D7635C9DD825C1A717CB0F5AE29A52
                              SHA256 
22DE807DABCBEF115E8752CDB815708197085923EB69A782ACB6E2169A58A306
 Common Name (CN)             send.mail,server 
 subjectAltName (SAN)         send.mail,server 
 Issuer                       R3 (Let's Encrypt from 
US)
 Trust (hostname)             Ok via SAN (same w/o SNI)
 Chain of trust               Ok   
 EV cert (experimental)       no 
 ETS/"eTLS", visibility info  not present
 Certificate Validity (UTC)   89 >= 30 days (2022-10-24 08:31 
--> 2023-01-22 08:31)
 # of certificates provided   3
 Certificate Revocation List  --
 OCSP URI                     http://r3.o.lencr.org
 OCSP stapling                not offered
 OCSP must staple extension   --
 DNS CAA RR (experimental)    not offered
 Certificate Transparency     yes (certificate extension)


 Testing vulnerabilities 

 Heartbleed (CVE-2014-0160)                not vulnerable 
(OK), no heartbeat extension
 CCS (CVE-2014-0224)                       not vulnerable (OK)
 ROBOT                                     not vulnerable (OK)
 Secure Renegotiation (RFC 5746)           supported (OK)
 Secure Client-Initiated Renegotiation     VULNERABLE (NOT 
ok), potential DoS threat
 CRIME, TLS (CVE-2012-4929)                not vulnerable (OK) 
(not using HTTP anyway)
 POODLE, SSL (CVE-2014-3566)               not vulnerable 
(OK), no SSLv3 support
 TLS_FALLBACK_SCSV (RFC 7507)              Downgrade attack 
prevention supported (OK)
 SWEET32 (CVE-2016-2183, CVE-2016-6329)    not vulnerable (OK)
 FREAK (CVE-2015-0204)                     not vulnerable (OK)
 DROWN (CVE-2016-0800, CVE-2016-0703)      not vulnerable on this 
host and port (OK)
                                           make sure you don't use this 
certificate elsewhere with SSLv2 enabled services
                                           
https://censys.io/ipv4?q=22DE807DABCBEF115E8752CDB815708197085923EB69A782ACB6E2169A58A306
 could help you to find out
 LOGJAM (CVE-2015-4000), experimental      not vulnerable 
(OK): no DH EXPORT ciphers, no common prime detected
 BEAST (CVE-2011-3389)                     TLS1: 
ECDHE-RSA-AES256-SHA DHE-RSA-AES256-SHA AES256-SHA ECDHE-RSA-AES128-SHA
                                                 DHE-RSA-AES128-SHA AES128-SHA 

                                           VULNERABLE -- but also 
supports higher protocols  TLSv1.1 TLSv1.2 (likely mitigated)
 LUCKY13 (CVE-2013-0169), experimental     potentially 
VULNERABLE, uses cipher block chaining (CBC) ciphers with TLS. Check 
patches
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers 
detected (OK)


 Testing 370 ciphers via OpenSSL plus sockets against the server, 
ordered by encryption strength 

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.   Encryption  Bits     
Cipher Suite Name (IANA/RFC)
-----------------------------------------------------------------------------------------------------------------------------
 x1302   TLS_AES_256_GCM_SHA384            ECDH 253   AESGCM      256 
     TLS_AES_256_GCM_SHA384                             
 x1303   TLS_CHACHA20_POLY1305_SHA256      ECDH 253   ChaCha20    256 
     TLS_CHACHA20_POLY1305_SHA256                       
 xc030   ECDHE-RSA-AES256-GCM-SHA384       ECDH 521   AESGCM      256 
     TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384              
 xc014   ECDHE-RSA-AES256-SHA              ECDH 521   AES         256 
     TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA                 
 x9f     DHE-RSA-AES256-GCM-SHA384         DH 2048    AESGCM      256 
     TLS_DHE_RSA_WITH_AES_256_GCM_SHA384                
 xcca8   ECDHE-RSA-CHACHA20-POLY1305       ECDH 521   ChaCha20    256 
     TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256        
 xccaa   DHE-RSA-CHACHA20-POLY1305         DH 2048    ChaCha20    256 
     TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256          
 xc09f   DHE-RSA-AES256-CCM                DH 2048    AESCCM      256 
     TLS_DHE_RSA_WITH_AES_256_CCM                       
 x39     DHE-RSA-AES256-SHA                DH 2048    AES         256 
     TLS_DHE_RSA_WITH_AES_256_CBC_SHA                   
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      
TLS_RSA_WITH_AES_256_GCM_SHA384                    
 xc09d   AES256-CCM                        RSA        AESCCM      256      
TLS_RSA_WITH_AES_256_CCM                           
 x35     AES256-SHA                        RSA        AES         256      
TLS_RSA_WITH_AES_256_CBC_SHA                       
 x1301   TLS_AES_128_GCM_SHA256            ECDH 253   AESGCM      128 
     TLS_AES_128_GCM_SHA256                             
 x1304   TLS_AES_128_CCM_SHA256            ECDH 253   AESCCM      128 
     TLS_AES_128_CCM_SHA256                             
 xc02f   ECDHE-RSA-AES128-GCM-SHA256       ECDH 521   AESGCM      128 
     TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256              
 xc013   ECDHE-RSA-AES128-SHA              ECDH 521   AES         128 
     TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA                 
 x9e     DHE-RSA-AES128-GCM-SHA256         DH 2048    AESGCM      128 
     TLS_DHE_RSA_WITH_AES_128_GCM_SHA256                
 xc09e   DHE-RSA-AES128-CCM                DH 2048    AESCCM      128 
     TLS_DHE_RSA_WITH_AES_128_CCM                       
 xc09c   AES128-CCM                        RSA        AESCCM      128      
TLS_RSA_WITH_AES_128_CCM                           
 x33     DHE-RSA-AES128-SHA                DH 2048    AES         128 
     TLS_DHE_RSA_WITH_AES_128_CBC_SHA                   
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      
TLS_RSA_WITH_AES_128_GCM_SHA256                    
 x2f     AES128-SHA                        RSA        AES         128      
TLS_RSA_WITH_AES_128_CBC_SHA                       


 Running client simulations via sockets 

 Android 8.1 (native)         TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256, 253 
bit ECDH (X25519)
 Android 9.0 (native)         TLSv1.3 TLS_AES_128_GCM_SHA256, 253 bit 
ECDH (X25519)
 Android 10.0 (native)        TLSv1.3 TLS_AES_128_GCM_SHA256, 253 bit 
ECDH (X25519)
 Java 6u45                    TLSv1.0 AES128-SHA, No FS
 Java 7u25                    TLSv1.0 ECDHE-RSA-AES128-SHA, 256 bit ECDH 
(P-256)
 Java 8u161                   TLSv1.2 ECDHE-RSA-AES256-SHA, 256 bit ECDH 
(P-256)
 Java 11.0.2 (OpenJDK)        TLSv1.3 TLS_AES_128_GCM_SHA256, 256 bit 
ECDH (P-256)
 Java 12.0.1 (OpenJDK)        TLSv1.3 TLS_AES_128_GCM_SHA256, 256 bit 
ECDH (P-256)
 OpenSSL 1.0.2e               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 
bit ECDH (P-256)
 OpenSSL 1.1.0l (Debian)      TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 253 
bit ECDH (X25519)
 OpenSSL 1.1.1d (Debian)      TLSv1.3 TLS_AES_256_GCM_SHA384, 253 bit 
ECDH (X25519)
 Thunderbird (68.3)           TLSv1.3 TLS_AES_128_GCM_SHA256, 253 bit 
ECDH (X25519)

 Done 2022-10-24 23:14:28 [  75s] -->> xx.xx.x.xx:587 (send.mail,server) 
<<--


---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Reply via email to