I've been helping my father in-law set up his email. According to Cox Communications tech support, they do not support IMAP. This is weird thing number one. So, I set up Purify to forward all Cox Communications email to an account that I set up on my server that does support IMAP. Purify starts doing it's thing, but has a hard time digesting the POP email coming in from Cox. Turns out that they are sending the "." that terminates a message as a separate packet. Ok, I can fix this, I add some code to Purify that insists on getting this packet. This works, but, I can't connect to the forward server on port 25. Apparently, Cox has this closed in Northern Virginia. So I set the forward up on port 26 (purify.cc can accept mail on this port).
So, I'm probably going to add this feature in the next release of Purify (one is already in the new version 2.2.1 soon to be released).
-- POP protocol support to look for the "lone packet" to terminate a POP message.
It'll be a few weeks before all of this happens, with my iPhone app work, and Thanksgiving, blah blah ...