# Mails not being fetched from Exchange 2016 after update of Ubuntu & Zammad (SSLError: SSL\_write) **URL:** https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308 **Category:** Technical assistance **Created:** [September 17, 2020, 7:54am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308 "2020-09-17T07:54:45Z") **Posts on this page:** 8 **Page:** 1
### Author: ![ZammadBeeblebrox](https://community.zammad.org/letter_avatar_proxy/v4/letter/z/9fc29f/32.png) [@ZammadBeeblebrox](https://community.zammad.org/u/ZammadBeeblebrox) #### Post date: [September 17, 2020, 7:54am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/1 "2020-09-17T07:54:45Z")
### Infos: - Used Zammad version: 3.4.x - Used Zammad installation source: (source, package, …) from source acc. to [Install with Package Manager — Zammad System Documentation documentation](https://docs.zammad.org/en/latest/install/ubuntu.html) - Operating system: Ubuntu 18.04.5 LTS - Browser + version: Firefox 80.0.1 ### Expected behavior: - Mails are fetched from the Exchange server. ### Actual behavior: - Mails are not fetched from the mail server. - Health status says: “Channel: Email::Account in Can’t use Channel::Driver::Imap: #\”. ### Steps to reproduce the behavior: - Update/upgrade the system from Ubuntu 18.04.? LTS and Zammad 3.?.? to Ubuntu 18.04.5 LTS and Zammad 3.4.x via ‘sudo apt-get update && sudo apt-get upgrade’ - Login to Zammad to see that there are no new tickets although the respective Exchange mail account has new mails. Additional information: - Exchange shell says that ImapProxy is active. ([eMail - Exchange 2016 and Zammad: OpenSSL::SSL::SSLError: SSL\_connect SYSCALL · Issue #682 · zammad/zammad · GitHub](https://github.com/zammad/zammad/issues/682)) - No changes to Exchange were made (Exchange server was a little low on disk space, but still had sufficient space; after increasing disk space and doing regular updates it still doesn’t work, so changes to Exchange didn’t have an effect. - The system stopped fetching mails after doing the upgrade of Ubuntu and Zammad and a reboot. Could it be that the Ubuntu upgrade changed TLS settings and is less forgiving than the previous version? The ticket below discusses TLS, but the error message is different from ours. > > > \### Infos: > > \* Docker version: 18.09.7 > \* Operating system (Docker host): Ubunt…u 19.04. > > > \### Expected behavior: > > \* I can update via \_docker-compose pull\_ and everything works fine. > > > \### Actual behavior: > > \* I´ve updated via \_docker-compose pull\_, everything works fine, except the SMTP connection for sending E-Mails. > > > \### Steps to reproduce the behavior: > > \* Update to latest with docker-compose pull > \* Send an E-Mail from a ticket > \* Receive the error message "Zustellung fehlgeschlagen: "Unable to send email to 'XXXX@XXXX.de': Can't use Channel::Driver::Smtp: #\" > > > \### Workaround > After lots of hours of exchange troubleshooting with the latest tag (3.1.0-7), I decided to switch back to image tag 3.1.0-6, but it didn´t work. First the step back to 3.0.0-15 did the trick. Now everything works fine. > > \### Hints > While testing lots of configurations from exchange side, i got different error messages. For example: > > \* "net::ReadTimeout" > \* "SSL\_connect returned=1 errno=0 state=error: wrong". > > It feels like a problem between Ruby and Elasticsearch. Thanks in advance for any ideas! ---
### Author: ![ZammadBeeblebrox](https://community.zammad.org/letter_avatar_proxy/v4/letter/z/9fc29f/32.png) [@ZammadBeeblebrox](https://community.zammad.org/u/ZammadBeeblebrox) #### Post date: [September 21, 2020, 7:58am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/2 "2020-09-21T07:58:13Z")
No ideas? Today I tried updating the system again (not sure it helps but it shouldn’t harm), and it gives an error (first words in German but the message should be clear anyway): “Fehlschlag beim Holen von [https://dl.packager.io/srv/zammad/zammad/downloads/118995?token=eyJ0e[...]](https://dl.packager.io/srv/zammad/zammad/downloads/118995?token=eyJ0e%5B...%5D) 500 Internal Server Error [IP: 178.63.71.248 443]” (I shortened the token). Opening this URL in Firefox gives: “We’re sorry, but something went wrong. If you are the application owner check the logs for more information.” I do not know if this could be responsible for my problem (maybe the Zammad update was incomplete), at least it is worth noting that something at [packager.io](http://packager.io) goes wrong. Greetings 🙂 ---
### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration) #### Post date: [September 21, 2020, 8:06am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/3 "2020-09-21T08:06:37Z")
> [@ZammadBeeblebrox](#): > > “Fehlschlag beim Holen von [https://dl.packager.io/srv/zammad/zammad/downloads/118995?token=eyJ0e[…]](https://dl.packager.io/srv/zammad/zammad/downloads/118995?token=eyJ0e%5B...%5D) 500 Internal Server Error [IP: 178.63.71.248 443]” > (I shortened the token). > [@Internal Server Error 500 - downloading apt package](https://community.zammad.org/t/internal-server-error-500-downloading-apt-package/5329): > > Infos: Used Zammad version: 3.1.0-1569535934.b232e9fb.stretch \> 3.4.0-1599753512.02c0bbc7.buster Used Zammad installation source: apt package Operating system: Debian 9 updated to Debian 10 Browser + version: — Expected behavior: Updating works Actual behavior: Updating fails with Err:1 https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 10/main amd64 zammad amd64 3.4.0-1599753512.02c0bbc7.buster 500 Internal Server Error [IP: \*\*\* 443] E: Failed to fetch https://dl.packager.io/s… ---
### Author: ![ZammadBeeblebrox](https://community.zammad.org/letter_avatar_proxy/v4/letter/z/9fc29f/32.png) [@ZammadBeeblebrox](https://community.zammad.org/u/ZammadBeeblebrox) #### Post date: [September 21, 2020, 8:23am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/4 "2020-09-21T08:23:35Z")
Thanks, I will watch that ticket. ---
### Author: ![ZammadBeeblebrox](https://community.zammad.org/letter_avatar_proxy/v4/letter/z/9fc29f/32.png) [@ZammadBeeblebrox](https://community.zammad.org/u/ZammadBeeblebrox) #### Post date: [September 21, 2020, 9:29am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/5 "2020-09-21T09:29:57Z")
Now the update was installed successfully, but it didn’t help regarding the original problem. ---
### Author: ![ZammadBeeblebrox](https://community.zammad.org/letter_avatar_proxy/v4/letter/z/9fc29f/32.png) [@ZammadBeeblebrox](https://community.zammad.org/u/ZammadBeeblebrox) #### Post date: [September 21, 2020, 10:55am UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/6 "2020-09-21T10:55:14Z")
After reading the docs again (I wanted to switch to POP3 because IMAP didn’t work), I read about port 993 for IMAP. We had 143 configured - which was working fine for 1.5 years, and after setting it to 993 Zammad now works again. Was that announced somewhere in release notes? Probably I missed it. Anyway, it is working again now 🙂 ---
### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration) #### Post date: [September 21, 2020, 12:57pm UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/7 "2020-09-21T12:57:21Z")
> [@ZammadBeeblebrox](#): > > After reading the docs again (I wanted to switch to POP3 because IMAP didn’t work), I read about port 993 for IMAP. We had 143 configured - which was working fine for 1.5 years, and after setting it to 993 Zammad now works again. > > Was that announced somewhere in release notes? Probably I missed it. Glad you could solve your issue. To help solve this mystery: No, there was no change in “ports we require” as this is absolutely depending on your. However, what we did is we dropped no longer supported / suggested encryptions. Especially everything with SSL and I think TLSv1.0 as well. This usually isn’t an issue, but may require you to upgrade the cyphers on your exchange server (or update it). Not entirely sure on the exchange end. The reason why port 993 does work instead of 143 proberbly is the encryption being used or possible. ---
### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system) #### Post date: [January 19, 2021, 12:57pm UTC](https://community.zammad.org/t/mails-not-being-fetched-from-exchange-2016-after-update-of-ubuntu-zammad-sslerror-ssl-write/5308/8 "2021-01-19T12:57:23Z")
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.