Can not receive email, password not accepted by server

I have the very same problem here:

READ Jul 21 09:16:58.393 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:********************************** -- port:993 -- socket:0x7fdfac1faf90 -- thread:0x7fdfad205b40

1.14 BAD Missing or invalid argument to AUTHENTICATE

I can confirm the same problem

iPad -> working fine

iTouch -> working fine

iMac -> before -> working fine

iMac -> upgraded to Lion -> the same error as above, and I am also on Scarlet. So exaclty the same issue.

The issue is that I am not able to receive Email, but I am able to SEND email, which is very very weird. I have tried with SSL, without SSL, and all the possible combinations, it is not possible to get this to work.

So I took the step :> installled Thunderbird, and reconfigured that with POPs, and guess what, running on Lion, that works absolutely fine! The issue is I think the way the authentication is working now.

So this confirms there is an issue with the mail application. Hope this will get fixed soon. I thought I was going crazy and was the only Scarlet (service provider in Belgium) to experience this 😁

READ Jul 21 09:46:55.833 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f92ef352db0 -- thread:0x7f92ed009cf0

CAPA

TOP

UIDL

RESP-CODES

PIPELINING

USER SASL PLAIN LOGIN

.

WROTE Jul 21 09:46:55.834 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f92ee993da0 -- thread:0x7f92ee9a2470

QUIT

WROTE Jul 21 09:46:55.856 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f92ef352db0 -- thread:0x7f92ed009cf0

QUIT

READ Jul 21 09:46:55.858 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f92ee993da0 -- thread:0x7f92ee9a2470

+OK QUIT

READ Jul 21 09:46:55.878 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f92ef352db0 -- thread:0x7f92ed009cf0

+OK QUIT

READ Jul 21 09:46:56.391 [kCFStreamSocketSecurityLevelNone] -- host:smtp.scarlet.be -- port:25 -- socket:0x7f92ed433990 -- thread:0x7f92eb51b8d0

220 eir ESMTP - Scarlet

WROTE Jul 21 09:46:56.406 [kCFStreamSocketSecurityLevelNone] -- host:smtp.scarlet.be -- port:25 -- socket:0x7f92ed433990 -- thread:0x7f92eb51b8d0

EHLO [192.168.0.112]

READ Jul 21 09:46:56.428 [kCFStreamSocketSecurityLevelNone] -- host:smtp.scarlet.be -- port:25 -- socket:0x7f92ed433990 -- thread:0x7f92eb51b8d0

250-eir.is.scarlet.be Hello ip-62-235-206-161.dsl.scarlet.be [62.235.206.161], pleased to meet you

250-ENHANCEDSTATUSCODES

250-8BITMIME

250-SIZE 78643200

250-DSN

250-AUTH PLAIN LOGIN

250-STARTTLS

250 HELP

WROTE Jul 21 09:46:56.433 [kCFStreamSocketSecurityLevelNone] -- host:smtp.scarlet.be -- port:25 -- socket:0x7f92ed433990 -- thread:0x7f92eb51b8d0

QUIT

I have the same issue in Lion Mail when connecting to my IMAP-UW server using SSL with PLAIN authentication.

WROTE Jul 21 08:08:50.647 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:xxx -- port:993 -- socket:0x7fb27b26f5b0 -- thread:0x7fb27bcd00a01.544 AUTHENTICATE PLAIN ******************** READ Jul 21 08:08:50.905 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:xxx -- port:993 -- socket:0x7fb27b26f5b0 -- thread:0x7fb27bcd00a01.544 BAD Missing or invalid argument to AUTHENTICATE

Same connection works fine with Leopard, Snow Leopard, iPhone and iPad (or any other SSL capable IMAP client), only Lion Mail is failing and showing this issue.

This is was the server logs for every login attempt. I'll try to get some more verbose output...

Jul 21 09:57:46 amd imapd[43438]: Unexpected client disconnect, while reading line user=??? host=xxx [1.2.3.4]

Same problem here....

I have also a scarlet account and my pop mail doesn't work anymore after the Lion update 😕

Help ..... !!!!

mysticTV, relax... You could create a gmail account and email as much you want. Or think of it as a holiday. Yeah, you're on holiday. No e-mail... heavenly. Think that.

It is not like Apple is not going to fix this. "POP email does not work in Lion." I think they know.

The build/revision number of Lion we got yesterday was the same as the one that was released to developers on July 1st, and was probably ready for release to QA somewhere end of June. That means what we got is almost a month old. In the mean time there's been 3 full work-weeks during which Apple has been further fixing Lion, we'll get the update soon.

So relax, it's only email. And it's only POP email. That sort of tells me your email was already not very important to begin with, or you'd be using an IMAP solution, but I could be wrong.

I have the same problem. All was fine yesterday upgraded to Lion and I can send mail but not receive. Iphone working fine on same accounts.

I am CEO of a company and I have not received mail for five hours, this is a disaster for me.

Apple please fix this ASAP.

Apple, move on. Mail doesn't work!

Has anyone tried to use IMAP instead of POP protocol?

I am authenticating against five OS X mail servers here, with no issues under IMAP not POP. Might be worth checking to at least temporarily switch to IMAP.

Hope this helps.

Yaroon,

Let's put things in the right perspective:

• Yes, you're right, screaming and shouting against Apple will not make this fix appear any sooner
• No, IMAP doesn't work either (actually, in my case POP works without problems, while IMAP is broken)
• No, this is not "just e-mails"; my inbox is my main work instrument. WIthout it I'm completely unable to do anything.

Waiting for a fix I just momentarily switched to Thunderbird, that works without problems. But, let me say that this is a pity as the new Mail is (IMHO) one of the most compelling innovations in Lion.

I also downloaded Thunderbird and everything works. This is a mac bug.

Ok, this is messy but I just went into prefernces accounts and disenabled the account. I then sent up a new account using my pop settings. I finished and all my mail downloaded. Now I just have to work out how to transfer my mail to this account. It wont allow me to enable the original account for me to drop the mail over.

I did compare the IMAP authentication process on Snow Leopard and Lion, and there has indeed been a change in the way Mail communicates with the server.

When in the Mail preferences the authentication is set to "Password" (I think this is the most common case), and the server is signalizing it supports SASL PLAIN authentication by sending "AUTH=PLAIN" in its capabilities, Snow Leopard uses the "LOGIN" command to authenticate, while Lion is using the "AUTHENTICATE PLAIN" command.

While this should be ok, according to http://www.ietf.org/rfc/rfc4616.txt, there seems to be a bug in the implementation, which causes the server not to understand the authentication parameters correctly.