 |
This only occurs on one of my two accounts on this server. The other account can send email just fine. |
|
|
After even more testing it is something specific because I can send email from the account to other people but so far I can't respond to this one thread. I can even send mail individually to people in the thread but I can't reply in this email thread, I've tried replying to 3 different messages so far. |
|
|
Set SOGoEASDebugEnabled=YES and test again. |
|
|
I can fully confirm this issue with iOS 11 GM and SOGo nightly builds from just right now. Unfortunately, the debug option does not generate any output, if tapping on the send link in the mail on my iPad, even though debugging works, as I see lots of XML and other stuff for that same iPad. I waited for the logs to become somewhat more quiet. Then I tapped on send and nothing gets logged. But at the same time I listen with a sniffer on port 443 on my SOGo server and I see that the iPad tries to do a communication. It looks normal in the sense of not seeing any reset flags. Normal TCP/IP communication: Example:tcpdump -pni eth0 port 443 [25/25]tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
|
|
|
Okay, found the problem, which may also be the problem for the OP: Turning off HTTP/2.0 solved the problem for me. I am an nginx user. So at least the issue has to do with HTTP/2.0 |
|
|
Looks like it isn't just a SOGo issue, but Exchange 2016 on Windows 2016 and Outlook.com as well |
|
|
Based on Microsoft's official support document on the issue https://support.microsoft.com/en-us/help/4043473/you-can-t-send-or-reply-from-outlook-com-office-365-or-exchange-2016-i it indeed looks to be an HTTP/2.0 issue based on the following text in the work around section: |
|
|
I haven't tested it today yet, but yesterday's release of iOS11.0.1 was supposed to fix the Outlook.com/Exchange2016 issue. So one could assume that it also fixes this issue. |
 |
Reopen if necessary. |
- Anonymous
