This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Email: Failed to shutdown ssl connection / show pop3 stored clean mails

Hello,

i will try to ask this question in english.

The following is given:

  • pop3 proxy --> enabled
  • Scan TLS encrypted POP3 traffic --> enabled
  • TLS certificates --> original certificate from my mailserver (mail.example.de)
  • under POP3 Servers and Prefetch Settings --> my mailserver (mail.example.de). TLS certificate is added to the pop3 server.

The error occurs whether prefetching is enabled or disabled.

Failed to shutdown ssl connection

Now I have two subsequent errors

  • Some mailboxes are blocked --> Maildrop locked for account_id
  • Under Mail Manager, POP3 stored messages, clean total, i have 32 messages. I can't see the recipients.The mails are not delivered.
  • I have enabled and disabled the mailproxy. Now the proxy does not work anymore. --> Can't bind on port 8110: Address already in use

What does the message: Failed to shutdown ssl connection?
How i can unblock a mailbox?
Where i can see the saved clean pop3 messages?
Can I restart the pop3 proxy service separately by ssh access (without having to start the complete UTM)?

Thanks and Regards



This thread was automatically locked due to age.
  • I believe that the POP3 Proxy will attempt to STARTTLS on a connection using port 110.  If your mail.example.de uses SSL/TLS on 993 or 995, I don't think UTM supports that.  I would be happy to learn that I am wrong and that this has changed unbeknownst to me.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Hi,
    yes it works basically on port 995. The mails are retrieved correctly, only the mentioned error is logged. The POP3 client has not used the latest version of OpenSSL. Perhaps that is the reason for the other mistakes. I will update the POP3 client and then test again.

    Thanks