[quote user="ecosse"][quote user="Rolf Lindby"]
IMAP will only need port 143 to be open to work, but it could be that some antimalware program is monitoring that port and causes lockups. If a sub-folder, for instance the one for sent messages, contains extremely many messages that could perhaps lead to problems, but I don't see any connection to the _inbox_.pnm file unless it would crash the IMAP module altogether. You could try to increase the TCP/IP timeout for IMAP considerably and see if that makes any difference, though. Make sure that you run the current version of Mercury (1.74) as well.
/Rolf
[/quote]
Not correct Rolf. Have a look here :-
http://support.apple.com/kb/ts1629
Appear to have problem solved.
I have opened 3 more ports on external net traffic to my domain, will post more specifics soon but port 587 is my favourite. :-
Message Submission for Mail (Authenticated SMTP) :- Mail (for sending mail), iCloud Mail (SMTP authentication)
The issue only arises when the remote client is trying to update the sent messages folder. (Causes serious issues in the configured 'scratch' folder)
Dougie.
[/quote]
Found the definitive apple document :-
http://support.apple.com/kb/HT1421
iOS: Setting up a corporate email server
Summary
This article explains the key steps for setting up a corporate mail server which can be accessed by an iOS device. These key steps will need to be completed by the IT support team or network administrator to enable email access.
Products Affected
iPad, iPhone, iPod touch, Verisign
For non-Exchange mail server configurations, or for Exchange server access via IMAP, use the following settings to enable secure iOS access:
Step 1
Open port 993 to allow email to be received through the firewall.
The proxy server must be set to IMAP over SSL only. SSL ensures that mail is securely encrypted during wireless transmission.
Step 2
As a best practice and for additional security protection, install a digital certificate on the server from a trusted certificate authority such as Verisign.
Installing a certificate from a certificate authority (CA) is an important step in ensuring that your proxy server is a trusted entity within your corporate infrastructure.
Step 3
Either port 587, 465, or 25 must be opened to allow email to be sent from iOS.
Additional Information
When sending a message, iOS automatically checks first for port 587, then 465, and then 25. Apple recommends opening 587 as the most reliable, secure port because it requires user authentication. Port 25 is considered to be the least secure because it's been around the longest and is subject to more attacks by hackers. It's also the port that some ISPs block by default to prevent unsolicited spam.
_____________________________________________________________________________
Problem must be a bug in IOS as it never touches our port 25 when updating sent messages.
p.s. What corporate does not have port 25 open if hosting their own smtp ?
[quote user="ecosse"][quote user="Rolf Lindby"]<p>IMAP will only need port 143 to be open to work, but it could be that some antimalware program is monitoring that port and causes lockups. If a sub-folder, for instance the one for sent messages,&nbsp;contains&nbsp;extremely many messages that could perhaps lead to problems, but I don't see any connection to the&nbsp;<span style="font-family: Tahoma, Arial, Helvetica; font-size: 12px;">_inbox_.pnm file unless it would crash the IMAP module altogether. You could try to increase the TCP/IP timeout for IMAP considerably and see if that makes any difference, though. Make sure that you run the current version of Mercury (1.74) as well.</span></p><p>/Rolf&nbsp;</p><p>[/quote]</p><p>
</p><p>
</p><p>Not correct Rolf. Have a look here :-</p><p>
</p><p>[url]http://support.apple.com/kb/ts1629[/url]</p><p>&nbsp;</p><p>
</p><p>Appear to have problem solved.</p>
<p>&nbsp;</p><p>I have opened 3 more ports on external net traffic to my domain, will post more specifics soon but port 587 is my favourite. :-
Message Submission for Mail (Authenticated SMTP) :- Mail (for sending mail), iCloud Mail (SMTP authentication)
</p><p>The issue only arises when the remote client is trying to update the sent messages folder. (Causes serious issues in the configured 'scratch' folder)
Dougie.
</p><p>
</p><p>[/quote]</p><p>
</p><p>Found the definitive apple document :- &nbsp;</p><p>[url]http://support.apple.com/kb/HT1421[/url]</p><p>
</p><p>iOS: Setting up a corporate email server
</p><p>Summary
This article explains the key steps for setting up a corporate mail server which can be accessed by an iOS device. These key steps will need to be completed by the IT support team or network administrator to enable email access.
Products Affected
iPad, iPhone, iPod touch, Verisign
For non-Exchange mail server configurations, or for Exchange server access via IMAP, use the following settings to enable secure iOS access:&nbsp;
Step 1
Open port 993 to allow email to be received through the firewall.
The proxy server must be set to IMAP over SSL only. SSL ensures that mail is securely encrypted during wireless transmission.
Step 2
As a best practice and for additional security protection, install a digital certificate on the server from a trusted certificate authority such as Verisign.
Installing a certificate from a certificate authority (CA) is an important step in ensuring that your proxy server is a trusted entity within your corporate infrastructure.
Step 3
Either port 587, 465, or 25 must be opened to allow email to be sent from iOS.
Additional Information
When sending a message, iOS automatically checks first for port 587, then 465, and then 25. Apple recommends opening 587 as the most reliable, secure port because it requires user authentication. Port 25 is considered to be the least secure because it's been around the longest and is subject to more attacks by hackers. It's also the port that some ISPs block by default to prevent unsolicited spam.</p><p>
</p><p>_____________________________________________________________________________
</p><p>Problem must be a bug in IOS as it never touches our port 25 when updating sent messages.&nbsp;
</p><p>p.s. What corporate does not have port 25 open if hosting their own smtp ?</p><p>
</p>