SOGo | BTS

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004272SOGoApple iPhone OSpublic2017-09-05 22:442018-03-13 16:48
ReporterKb1ibt 
Assigned Toludovic 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionsuspended 
PlatformAppleOSiOSOS Version11.0
Product Version3.2.10 
Target VersionFixed in Version 
Summary0004272: Unable to send email via iOS 11
DescriptionI am trying to send email using my iPad and my iPhone using the Exchange setup. Both have iOS 11 beta (latest) installed. When I try to send email it errors out in the mail client with "Cannot Send Mail - The message was rejected by the server."
When I log into the server and check the logs there is no line with POST ... cmd=SendMail
Additional InformationThis SOGo install is part of MailCow:dockerized
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0012257)
Kb1ibt (reporter)
2017-09-05 22:50

This only occurs on one of my two accounts on this server. The other account can send email just fine.
(0012258)
Kb1ibt (reporter)
2017-09-05 23:07

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.
(0012259)
tfu (reporter)
2017-09-06 01:17

Set SOGoEASDebugEnabled=YES and test again.
(0012300)
chrroessner (reporter)
2017-09-18 06:42

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
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:36:22.414507 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [S], seq 984687253, win 65535, options [mss 1400,nop,
wscale 6,nop,nop,TS val 549509296 ecr 0,sackOK,eol], length 0
12:36:22.414599 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [S.], seq 3834293778, ack 984687254, win 28960, optio
ns [mss 1460,sackOK,TS val 3329581360 ecr 549509296,nop,wscale 7], length 0
12:36:22.428310 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [P.], seq 1:240, ack 1, win 2060, options [nop,nop,TS
 val 549509306 ecr 3329581360], length 239
12:36:22.428375 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [.], ack 240, win 235, options [nop,nop,TS val 332958
1374 ecr 549509306], length 0
12:36:22.433238 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [.], seq 1:2777, ack 240, win 235, options [nop,nop,T
S val 3329581379 ecr 549509306], length 2776
12:36:22.433265 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [P.], seq 2777:4465, ack 240, win 235, options [nop,n
op,TS val 3329581379 ecr 549509306], length 1688
...
...
12:36:22.548418 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [F.], seq 4935, ack 5123, win 319, options [nop,nop,TS val 3329581494 ecr 549509424], length 0
12:36:22.549601 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [F.], seq 5123, ack 4935, win 2048, options [nop,nop,TS val 549509425 ecr 3329581477], length 0
12:36:22.549639 IP 134.255.226.246.https > 193.239.106.201.43394: Flags [.], ack 5124, win 319, options [nop,nop,TS val 3329581495 ecr 549509425], length 0
12:36:22.554851 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [.], ack 4623, win 2047, options [nop,nop,TS val 549509415 ecr 3329581474], length 0
12:36:22.554885 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [.], ack 4665, win 2047, options [nop,nop,TS val 549509419 ecr 3329581475], length 0
12:36:22.555154 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [.], ack 4935, win 2043, options [nop,nop,TS val 549509420 ecr 3329581477], length 0
12:36:22.561050 IP 193.239.106.201.43394 > 134.255.226.246.https: Flags [F.], seq 5123, ack 4936, win 2048, options [nop,nop,TS val 549509435 ecr 3329581494], length 0
--------------------------------------------------------------------------

So something happens that the iPad can not deliver its email.

I also can confirm that I can send regular email. I tried replying to an email, which does not work. Also forwarding does not work.
(0012301)
chrroessner (reporter)
2017-09-18 06:52

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
(0012317)
Kb1ibt (reporter)
2017-09-19 18:04

Looks like it isn't just a SOGo issue, but Exchange 2016 on Windows 2016 and Outlook.com as well
https://support.apple.com/en-us/HT208136 [^]
(0012320)
Kb1ibt (reporter)
2017-09-20 20:30

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:
If you use the Mail app to sync data from Exchange Server 2016 that is running on Windows Server 2016, you can ask the system administrator to disable HTTP/2 in Windows Server 2016 as a workaround
(0012327)
Kb1ibt (reporter)
2017-09-27 10:35

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.
User avatar (0012689)
ludovic (administrator)
2018-03-13 16:48

Reopen if necessary.

- Issue History
Date Modified Username Field Change
2017-09-05 22:44 Kb1ibt New Issue
2017-09-05 22:50 Kb1ibt Note Added: 0012257
2017-09-05 23:07 Kb1ibt Note Added: 0012258
2017-09-06 01:17 tfu Note Added: 0012259
2017-09-06 10:27 ludovic Severity major => minor
2017-09-18 06:42 chrroessner Note Added: 0012300
2017-09-18 06:52 chrroessner Note Added: 0012301
2017-09-19 18:04 Kb1ibt Note Added: 0012317
2017-09-20 20:30 Kb1ibt Note Added: 0012320
2017-09-27 10:35 Kb1ibt Note Added: 0012327
2018-03-13 16:48 ludovic Note Added: 0012689
2018-03-13 16:48 ludovic Status new => resolved
2018-03-13 16:48 ludovic Resolution open => suspended
2018-03-13 16:48 ludovic Assigned To => ludovic


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker