The most glaring break in Mac OS X Lion 10.7 has been POP mail compatibility.
Hundreds of users from varying ISPs, companies and institutions have reported that the new Lion Apple Mail 5.0, while working fine for IMAP, can no longer make successful authentication handshakes while in POP mode.
While most of our newer customers are IMAP users, our older clientele tend to be POP.
Though there are many mail server systems out there, we will focus on the Perdition Mail Proxy server for POP.
If your ISP, company or institution uses Perdition POP then there is a chance you will see an issue with Lion depending on its configuration.
Below are the changes that should be made to the perdition configuration file.
Before Perdition 1.8 a proper delimiter was two spaces " " but starting with 1.8 a proper delimiter is now a '.' space.
So in the Perdition configuration file instead of having a
"--pop_capability" string perhaps of:
TOP UIDL USER LOGIN SASL
It should instead be:
TOP.UIDL.USER.LOGIN.SASL
Once this change occurs, apart from successful POP handshakes while in Lion Apple Mail, the results can also be seen when querying the server with a telnet session.
You should see server response change from:
$ telnet [your server] 110Trying [server IP]...Connected to [your server].Escape character is '^]'.+OK POP3 perditon ready on [your server]capa+OK Capability list follows, mateTOP UIDL USER LOGIN SASLSTLS
to
$ telnet [your server] 110Trying [server IP]...Connected to [your server].Escape character is '^]'.+OK POP3 perditon ready on [your server]capa+OK Capability list follows, mateTOPUIDLUSERLOGINSASLSTLS
We hope this will be useful to Perdition admins with newly minted Lion customers who are most likely roaring about Lion's POP problems.
Go Go