EAP3 + newest Apple update. All mail connection to Exchange are dead now.

Hi Paul,

you will have to join the rest of the Apple device users in this forum and disable email scanning util the promised fix is released.

Ian

Just to be sure: You guys use the same kind of Mail relay? I guess not, because exchange most likely uses RPC / MAPI. 

Ian, i guess you are using IMAP? 

Hi Toni,

I am using smtp and iMAPs. I can get IMAPS to work with one ISPs server but not the the others. These all worked in 17.5.8.

SMTP only works with one ISP and reports that the ISP does not use SSL which also worked in v17.5.8.

The daily reports are sent out and the mail is reported on in the daily reports.

Ian

On Iphone, I'm using standard builtin method to connect on Exchange.

On desktop, I use the newer "Microsoft Exchange" type account.  It used to show POP, or IMAP, or else types before (Outlook 2010 or earlier), but now it shows "Exchange" type.  For what it means.  But clearly not old school SMTP.

Paul Jr

And as far as I can tell they are not scanned or passed by the XG.

Ian

We need to split this very carefully. 

Exchange on iPhone and Exchange in outlook is most likely MAPI over http(s). Older versions used RPC over http. So it highly depends on the version, you are using on Client / Exchange. 

There is no SMTP used in Exchange (as far as i know). https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Outlook-Connectivity-with-MAPI-over-HTTP/ba-p/586590

And Exchange has a variety of HTTPs styles. Question one: https://www.ssllabs.com/ssltest/ If you check your Exchange with ssllabs.com (EWS and MAPI), do you have any issues there? 

Is your Exchange version considered safe? 

"Old school SMTP" is still used for MTA communication. Basically how Exchange will send a mail to another mail server. Considered by IANA.

There is another mechanism (try) to split SMTP (port 25) from the Client way to send a mail (SMTPs?).

https://en.wikipedia.org/wiki/SMTPS

Port 578 or Port 465 are most likely the Client to Server ports, while Port 25 is used MTA to MTA. 

As far as i know, they split those ports to have a clear split between the Client and server communication but Port 25 is widely used. 

To sum this up.

Ian has an issue with the IMAP / Legacy SMTP Proxy.

Paul has an issue with DPI Issue hitting on his HTTP(s) traffic. 

We need to split this very carefully. 

Exchange on iPhone and Exchange in outlook is most likely MAPI over http(s). Older versions used RPC over http. So it highly depends on the version, you are using on Client / Exchange. 

There is no SMTP used in Exchange (as far as i know). https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Outlook-Connectivity-with-MAPI-over-HTTP/ba-p/586590

And Exchange has a variety of HTTPs styles. Question one: https://www.ssllabs.com/ssltest/ If you check your Exchange with ssllabs.com (EWS and MAPI), do you have any issues there? 

Is your Exchange version considered safe? 

"Old school SMTP" is still used for MTA communication. Basically how Exchange will send a mail to another mail server. Considered by IANA.

There is another mechanism (try) to split SMTP (port 25) from the Client way to send a mail (SMTPs?).

https://en.wikipedia.org/wiki/SMTPS

Port 578 or Port 465 are most likely the Client to Server ports, while Port 25 is used MTA to MTA. 

As far as i know, they split those ports to have a clear split between the Client and server communication but Port 25 is widely used. 

To sum this up.

Ian has an issue with the IMAP / Legacy SMTP Proxy.

Paul has an issue with DPI Issue hitting on his HTTP(s) traffic. 

Based on your post above, I will rework my IMAPS and SMTP setup on the XG, iPad, iPhone and MBP.

Ian

Remote desktops running Outlook 2010 are using ActiveSync 16.1 on Exchange 2016 to be more accurate.

Behave the same with Outlook 2013.

Paul Jr

Hi Lucar Toni,

I spent a number of hours trying to fix iMAPS on two MBPs, an iPhone and an iPad without success.

SMTPs works to all ISP servers.

iMAPS fails because the certificate on the MBP does not meet pinning requirements and iPad and iPhone it is not trusted even when showing in the profile setting as being trusted.

Works fine when not connected to the XG.

Ian