-
All replies
-
Helpful answers
-
by Michael Sidoric,Jul 20, 2011 5:55 PM in response to mysticTV
Michael Sidoric
Jul 20, 2011 5:55 PM
in response to mysticTV
Level 2 (369 points)
Servers EnterpriseThe settings in Lion Mail should be the same as your previous Snow Leopard install. Are your other email accounts functioning properly? Is just one account affected?
Might I suggest launching Lion Mail and go up to the top menu bar under WINDOW and pull down to Connection Doctor and have it poll your server connections. The diagnostic will display at right.
Please report back here and let's work through this to get you online quickly.
Regards, Michael
-
Jul 20, 2011 6:28 PM in response to Michael Sidoricby mysticTV,Nothing!
Just got off the phone with the server tech support and there is nothing wrong with their side. I can see my incoming mail via the server's mail site and can log in there using the same password and user name with no problem.
It's just trying to connect thru my iMac using the new mail that I can't log in.
Keep getting the server will not accept the password even though it's correct......
-
by Michael Sidoric,Jul 20, 2011 6:52 PM in response to mysticTV
Michael Sidoric
Jul 20, 2011 6:52 PM
in response to mysticTV
Level 2 (369 points)
Servers EnterpriseI'd suggest going to Keychain Access and remove all references to the troubled account. Only do this if you are SURE of the correct password.
Then copy all settings for incoming and outgoing servers and then delete and re-add the account. When responding to password request from server choose NOT to save until you know it works.
Sorry for the extra work. But I mail admin three Mac servers, this is usually the fastest way to resolve issues like this.
-
Jul 20, 2011 7:15 PM in response to Michael Sidoricby mysticTV,Tried this!
I deleted all keychain ref's to POP and smtp accounts.
Deleted mail account and started from scratch.
Still same problem!
Getting this message too:
Mail cannot send your password securely to the server.
-
by Michael Sidoric,Jul 20, 2011 7:46 PM in response to mysticTV
Michael Sidoric
Jul 20, 2011 7:46 PM
in response to mysticTV
Level 2 (369 points)
Servers EnterpriseGood feedback. What type of server is this? Enterprise? Your internet provider?
From the error message, the password may be correct – the issue seems to be that it is being submitted to the server insecurely. That could be because of the type of password (plain text, clear) which can be intercepted and is therefore rejected by most secure servers – or your computer may no longer have the proper Certificate listed in the Keychain.
Do you have any documentation from when you first set up this email account that indicates the proper settings for access? Ports for SSL, types of accounts used POP/IMAP for incoming, and SMTP settings?
The best diagnostic is the Connection Doctor within Mail. It will attempt to authenticate and report back with the cause for the rejection.
Since there are so many settings – each server is different – I suspect that something burped during the migration. It is not a fatal error and can be fixed once we understand the settings the server is looking for.
If you have any leads on settings required for that particular server, I'm glad to help you get your Mail account back.
Did find an online resource that had settings for teleguam.net – since they are for a Windows app, you will need to look around for the matching places in Mail to enter your data – but it would be helpful: http://www.gta.net/residential/spyder-internet/pdfs/EmailWindowsNetscapeCommunic ator6.pdf
-
Jul 20, 2011 7:59 PM in response to mysticTVby SingingFriar,Disable the firewall. That fixed it for me.
-
by Michael Sidoric,Jul 20, 2011 8:04 PM in response to SingingFriar
Michael Sidoric
Jul 20, 2011 8:04 PM
in response to SingingFriar
Level 2 (369 points)
Servers EnterpriseHmmm Rather than disable the protection of the Firewall in Security – would be better to allow access to/from Mail specifically while maintaining protection for othjer services and operations.
Not sure that's the proper fix here. If the Firewall was blocking access – there would be no response from the server, rather than an 'insecure submission' reply.
Good point on Firewall when troubleshooting iChat and FaceTime. Thanks for the info.
-
Jul 20, 2011 8:18 PM in response to Michael Sidoricby SingingFriar,I just disabled it for a moment, then renabled it. It's not like your machine is going to get hacked that moment.
Just relating my experience and fix.
-
Jul 20, 2011 9:05 PM in response to SingingFriarby mysticTV,Disabling the firewall does nothing.
Just connected my iPod to the same mail settings and works fine.
Problem is.......... APPLE!!!!!!!!
Lion has a screwed up mail program.
There should have been no mod's needed in the upgrade
to get mail running.
-
by Michael Sidoric,Jul 20, 2011 9:14 PM in response to mysticTV
Michael Sidoric
Jul 20, 2011 9:14 PM
in response to mysticTV
Level 2 (369 points)
Servers EnterpriseSorry but frustration will not fix your Mail.
I have seven accounts with a variety of servers that migrated perfectly.
Are there any mail accounts functioning correctly under Lion?
What does the Connection Doctor report when it attempts to connect and authorize (log in)?
Blanket blaming Apple is not helpful. Neither is switch flipping. If you wish my help I will do my best with the information you provide.
Take care.
-
Jul 20, 2011 10:54 PM in response to Michael Sidoricby leonino_c,Hi Michael,
i think your contribution is actually very appreciated. But I can also understand the frustration from mysticTV as this doesn't seem to be an isolated problem (you can spot several similar help requests on this forum).
I have the same issue with my work's IMAP server (proteced by SSL with plain auth): it worked perfectly with SnowLeo and now it refuses the connection asking for the password.
I followed your suggestion to check with the connectino doctor and this is the outcome (i stripped out other lines concerting SMTP over SSL for the same server (that works perfectly) and ther server as well (e.g. Google IMAP overs SSL):
CONNECTED Jul 21 07:44:58.943 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap.dis.uniroma1.it -- port:993 -- socket:0x7ff8c22b56d0 -- thread:0x1018a7530
READ Jul 21 07:44:59.247 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap.dis.uniroma1.it -- port:993 -- socket:0x7ff8c22b56d0 -- thread:0x1018a7530
* OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] mail.dis.uniroma1.it IMAP4rev1 2007e.404 at Thu, 21 Jul 2011 07:44:59 +0200 (CEST)
WROTE Jul 21 07:44:59.257 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap.dis.uniroma1.it -- port:993 -- socket:0x7ff8c22b56d0 -- thread:0x7ff8c380c3e0
1.10 AUTHENTICATE PLAIN ************************
READ Jul 21 07:44:59.322 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap.dis.uniroma1.it -- port:993 -- socket:0x7ff8c22b56d0 -- thread:0x7ff8c380c3e0
1.10 BAD Missing or invalid argument to AUTHENTICATE
Seems like there is an error in the way the new version of Mail tries to authenticate with the server...
-
Jul 20, 2011 11:37 PM in response to leonino_cby giuseppefrommerelbeke,Michael,
I am experiencing the same problem of mysticTV with a POP account. I have another MacBook running on Leppard and using the previous Mail version. Just installed the POP account there and it works perfectly.
Also my service provider confirmed everything is working well from his side...
Hope to get solution soon.
-
Jul 21, 2011 12:08 AM in response to mysticTVby tlammens,Same problem here, worked fine before upgrading to Mac OS X Lion, now it doesn't work anymore:
I tried to telnet to my pop3 server and had no problems authenticating in this way. So there is definitely something wrong with the current Mail implementation.
Problem occurs with pop3 server: pop.scarlet.be
Here is the response doing plain telnet:
+OK POP3 Ready tisch 0001e4dd
CAPA
+OK Capability list follows, mate
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
USER SASL PLAIN LOGIN
.
here using the Connection Doctor in Mail:
READ Jul 21 08:55:45.722 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7f9776cb4e70 -- thread:0x7f97753e5bc0
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
USER SASL PLAIN LOGIN
.
To be complete, everything in the Connection Doctor regarding pop.scarlet.be:
CONNECTED Jul 21 09:04:00.693 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
READ Jul 21 09:04:00.706 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
+OK POP3 Ready niles 0001e4dd
WROTE Jul 21 09:04:00.708 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
CAPA
READ Jul 21 09:04:00.726 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
+OK Capability list follows, mate
READ Jul 21 09:04:00.823 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
USER SASL PLAIN LOGIN
.
WROTE Jul 21 09:04:00.830 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
QUIT
READ Jul 21 09:04:00.845 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fbfb36bc5f0 -- thread:0x7fbfb3848830
+OK QUIT
-
Jul 21, 2011 12:11 AM in response to tlammensby ojnv,I've got the same problem with scarlet (everything was fine before the upgrade to OS Lion) :
CONNECTED Jul 21 09:01:38.322 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
READ Jul 21 09:01:38.385 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
+OK POP3 Ready niles 0001e4dd
WROTE Jul 21 09:01:38.419 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
CAPA
READ Jul 21 09:01:38.434 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
+OK Capability list follows, mate
READ Jul 21 09:01:38.533 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
USER SASL PLAIN LOGIN
.
WROTE Jul 21 09:01:38.544 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
QUIT
READ Jul 21 09:01:38.557 [kCFStreamSocketSecurityLevelNone] -- host:pop.scarlet.be -- port:110 -- socket:0x7fdf823ad9e0 -- thread:0x7fdf825095c0
+OK QUIT