which ports does an iPhone use

ConanMan

I am following these instructions but they are insufficient

https://docs.mailcow.email/client/client-apple/ states

Download and open the file from https://${MAILCOW_HOSTNAME}/mobileconfig.php.
Enter the unlock code (iPhone) or computer password (Mac).
Enter your email password three times when prompted.

however this is not everything that needs to be done. All other mail clients will resolve perfectly happily on ports 143/587 STARTTLS on my mailcow instance. But not iPhone. I have followed the instructions as provided, but they lack the substantive information on what protocols and ports mailcow is expecting.

Could someone please tell me what implicit ports and protocols iPhone will use for this process. Clearly they are not STARTTLS 143/587

https://${MAILCOW_HOSTNAME}/mobileconfig.php.

I also recall, that when I was setting up mailcow the first time, I am 99% sure somewhere in the admin panel were alternate instructions relating to iPhone but I cannot find them? could someone help me locate them?

ConanMan

It now works: in case it helps, I read this post, and I made sure ports 143,587,993,465,25 were checked to be open and it seems to now work

(993 was the only one not already added)

esackbauer

You could have found that in the docs also:
https://docs.mailcow.email/prerequisite/prerequisite-system/
See section “Firewall & Ports”
It seems reading the manuals is a forgotten art 😉

ConanMan

esackbauer but you simply do not need all those ports open for the mailcow to function, and the default ports section doesn’t mention anywhere that iPhone clients will need to probe them. It just mentions the server application and protocols. Perhaps case specific information seems to be a lost art too?

esackbauer

ConanMan
Well, if you followed the advanced DNS configuration, any phone WILL probe the port 993 for IMAPS.
If you don’t follow the documentation, you run into troubles, sooner or later, as your problem has shown 😉

D4niel

Well, Mailcow can’t provide every information for every client out there that doesn’t follow simple standards. That’s something that I would expect in the docs of the client, not the server.