Skip to main content

Issues with mail auth fails & mail delivery

Comments

9 comments

  • keat63
    OSX by any chance ?
    0
  • cPanelLauren
    This looks like the server is no longer accepting SSLv2 connections (this is typically done in favor of TLSv1.2) - the thread here might be helpful for you:
    0
  • Obble
    OSX by any chance ?

    I believe this client in particular is on OSX, yes.
    This looks like the server is no longer accepting SSLv2 connections (this is typically done in favor of TLSv1.2) - the thread here might be helpful for you:
    0
  • Henry Carter
    Hi Obble, check /var/log/exim_mainlog logs, if you see any errors like "SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol". The reason for the errors in regards to SSL and TLS is that security was increased on Exim SSL/TLS and ciphers. The issue that occurs from the source email client sending side is that the operating system version and/or email client version used only supports older SSL/TLS versions and ciphers. The absolute best approach is to have the users upgrade their workstations to up to date operating system versions along with up to date email client versions. There is a workaround on the server side but I would like to mention that workaround is not recommended and undoes the security update made to Exim itself.
    0
  • Obble
    Hi Obble, check /var/log/exim_mainlog logs, if you see any errors like "SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol". The reason for the errors in regards to SSL and TLS is that security was increased on Exim SSL/TLS and ciphers. The issue that occurs from the source email client sending side is that the operating system version and/or email client version used only supports older SSL/TLS versions and ciphers. The absolute best approach is to have the users upgrade their workstations to up to date operating system versions along with up to date email client versions. There is a workaround on the server side but I would like to mention that workaround is not recommended and undoes the security update made to Exim itself.

    Hi Henry. Thanks for your reply. I haven"t checked just now but when looking into those logs earlier I did see those messages. What is the workaround here? I know it"s best for users to upgrade their systems but not always practical.
    0
  • Henry Carter
    Hi Obble, Log into WHM and go to "Exim Configuration Manager" Change "Options for OpenSSL" to +no_sslv2 +no_sslv3 Change "SSL/TLS Cipher Suite List" to ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS then scroll down and click save. Then for dovecot log into WHM and go to "Service Configuration "Mailserver Configuration" Under "SSL Cipher List" clear the text box and paste instead ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS Next scroll to the bottom of the page and click Save change.
    0
  • Obble
    Thanks for your help on this Henry. Do you think this would also stop those IP blocks from failed IMAP or SMTP logins? As this allows clients on older systems to connect? I've made the changes and will keep an eye out for the errors you mentioned to see if they reappear.
    0
  • Obble
    Still getting errors like this: dovecot_plain authenticator failed for ([IPv6:::ffff:xxxxx]) [xxxxx]:56815: 535 Incorrect authentication data (set_id=xxxxx@xxxxx.com)
    And Aug 5 11:05:37 server dovecot: imap-login: Login: user=, method=PLAIN, rip=xxxxx, lip=xxxxx, mpid=xxxxx, TLS, session= Aug 5 11:05:40 server dovecot: imap-login: Disconnected (no auth attempts in 75 secs): user=<>, rip=xxxxx, lip=xxxxx, TLS handshaking: read(size=1017) failed: Connection reset by peer, session= Aug 5 11:05:42 server dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=xxxxx, lip=xxxxx, TLS: Connection closed, session= Aug 5 11:05:48 server dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=xxxxx, lip=xxxxx, TLS: Connection closed, session=
    Then the user gets blocked by CSF and sometimes CPHULK and then can't view the site, or do anything.
    0
  • cPanelLauren
    Feel free to open a ticket using the link in my signature. Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0

Please sign in to leave a comment.