Mail in OSX Lion : pop not OK

I had the same problem. Since upgrading to Lion, no single mail showed up despite "connection doctor" and "activity" showed no problems at all. Then it hit me: I checked the Spam folder - and there were sitting all my e-mails. I used Spam Sieve previously and hadn't reinstalled it yet, so all my mail got directed into the Spam folder. I reinstalled the current version of Spam Sieve and keep my fingers crossed.

Now I think the capability is mandatory in new MAIL in LION

I think the new Mail in Lion is respecting the capability command when starts to talk with the server pop.

When mail connects a SMTP 25 server it asks for extended helo (ehlo)

So the server can says its rules, limits so Mail can respect this rules.

When Mail connects an IMAP server is the same.

But now it seems that the new MAIL in Lion when connects a POP server its asks CAPA before send user and password.

If your server is not prepared to answer correct its ask, the connection will not complete.

It's not usual to ask capability in POP connections

First Check out after the connection if your server is answering correct the command CAPA when connected your port 110 POP

# telnet X.X.X.X 110

Trying X.X.X.X...

Connected to X.X.X.X.

Escape character is '^]'.

+OK POP3 Ready X.X.X.X 0001bc8e

CAPA

+OK Capability list follows, mate

Now I think the capability is mandatory in new MAIL in LION

hi i have found a fix that worked for me. in account information remove your incoming mail password, only have your incoming mail server and username.in the outgoing mail server click edit, and use default ports and check the use SSL, change authentication to password, and enter your username and password, click ok. In advanced uncheck use ssl and the port should change to 110 by itself and make authentication : password from the drop down menu.

if you can understand my jibberish this should work it did for me.

hmmm,

I've tried all the suggestion in this threat,

except for the one by Manuelfhp (that chinese to me)

and nothing seems to work.

Even going back to 10.6 is impossible.

Every single installation dvd I've tried is rejected of ignored.

I'm getting hopeless....

I had trouble setting up a pop email account as each time it came back as an imap. I have pop accounts and not imap. In order to get it to work where I can select pop or imap, I had to put an incorrect password in the field and then it let me continue and at the top of the block is a drop down found no where else that lets me change to pop and then I put the correct password in and change the incoming server to pop and remove the imap locations.

Hope this helps a little.

Lion Mail is giving me headaches too. My POP server with Jazztel (Spain) stopped working. It worked flawlessly in Snow Leopard, but now in Lion it's a mess. Apple must fix this problem as soon as possible, e-mail is an essential service.

I switched to IMAP to get email running again. In the future I will be more careful about updating. I never thought that basic services like email can be that buggy in a new release. I'm disappointed about that...

Maybe the only way to fixit is wait and download 10.7.1

Same problem here. Appears to be abug. I rebuilt the mailbox. Opened and closed. Re booted. Nothing works so far.

OK, I followed the thread and read further. Checked spam folder, and all my emails are there. While I try to figure out how to transfer them over, I'll keep reading further for a fix.

I read up on the Spam Sieve instructins in the SS app, under SS Help. How to setup SS. I am using the latst update. It advises to uncheck 'filter junk mail' in Mail 5 prefs. I did that. Appears to be working correctly. I'l keeping testing for a few days and in the meantime, I have my POP settings set to 'do not delete from server', just in case.

Okay, I have it resolved. I switched to imap to get by, but after deactivating and killing the password to the pop account (not deleting it), and taking it back online with having to re-enter the password, it worked again - similar to a previous post. Thanks to all and I hope this helps someone.

Okay, so it looks like a guy posted the solution that an admin would have to do to make on their POP server work for Lion 10.7 POP in relation to the CAPA sequence.

I'm assuming that this is what some of the reported ISPs have done to make Lion work (since Lion was initially broken and then suddenly got fixed for some of them). This fix though seems to specifically pertain to companies that use the Perdition Proxy Mail server (not sure how somebody finds outs what their company uses on the backend though without personally asking).

I think the gist of the article was that in the perdition mail server config file the "--pop_capability" had to be changed from having two space delimiters like:

TOP UIDL USER LOGIN SASL

To having '.' space delimiters as below:

TOP.UIDL.USER.LOGIN.SASL

Once that happen then doing a telnet query provides the correct response of:

TOP

UIDL

USER

LOGIN

SASL

STLS

Anyhow, there's more information in the article itself.

http://gogotechnology.blogspot.com/2011/07/getting-pop-mail-to-work-with-107-lio n.html

I'm going to try to see if I can get my company admin to make the change. I'm not sure how Mac friendly he is but I'll find out. Though I happen to remember that perhaps they are running something called NginX for their IMAP but maybe they do Perdition for the POP. I'll find out in anycase and report back!

Thank you so much to pboehi. I was tearing my hair out. I have Lion downloaded on home 28" iMac and on work 24" iMac and mail worked perfectly on home but I wasn't getting any new mail on work until today. I never thought to look at the spam folder .... it's all there. Apparently when my spam filter required a new subscription I let it lapse and at some point I uninstalled it from my home computer and forgot to do this on my work computer. So simple Thanks again.

Problems accessing IMAP on 5 accounts. Clicked off "Use IDLE command" under Accounts/Advanced. Worked. MacBook Air mid-2009. On MacBook Pro upgrade to Lion. No problems. Same accounts.

This trick has did not work on my exchange account.