search

fastsupply / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

MailMe cannot find MobileMe account passwords #105

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set up Mail so that your default sending account is MobileMe.
2. Set up MailMe.
3. Set up Growl to use MailMe.

What is the expected output?
Mail.

What do you see instead?
MailMe is unable to find the MobileMe account password in the keychain. It logs 
to the Console:

MailMe: Could not get
password for SMTP account <username>@smtp.me.com:587: -25300/ / The item
cannot be found.

Original issue reported on code.google.com by prhgr...@gmail.com on 31 Jan 2010 at 2:06

GoogleCodeExporter commented 9 years ago 
The bug is that MailMe only looks for SMTP keychain items. MobileMe accounts 
don't use an SMTP keychain item 
like other Mail accounts, but the single MobileMe keychain item, the same one 
that iDisk and Backup and other 
tools use.

The fix is for MailMe to look for a MobileMe keychain item when the SMTP 
hostname is one of MobileMe's 
(smtp.mac.com, smtp.me.com).

Original comment by prhgr...@gmail.com on 31 Jan 2010 at 2:17

GoogleCodeExporter commented 9 years ago 
Is there a workaround for this?

Original comment by simonhaw...@gmail.com on 5 Feb 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
No.

Original comment by prhgr...@gmail.com on 5 Feb 2010 at 11:16

GoogleCodeExporter commented 9 years ago 
Please note that I have attempted several workarounds for this problem 
including changing the default Mail account to one not associated with 
MobileMe.  This did not have any impact on the error messages in the Console or 
inability of MailMe to find a different SMTP keychain.  In fact, when the 
MobileMe account was deleted entirely the same symptom occurred - MailMe 
continued to look for a MobileMe SMTP keychain even though there was no 
MobileMe account in existence in Mail.

Original comment by ScottJGoldman on 15 Jul 2010 at 12:04

GoogleCodeExporter commented 9 years ago 
ScottJGoldman: Make sure you aren't confusing receiving accounts with sending 
accounts. MailMe only uses sending accounts, and it *will not* look for a 
password for a sending account that isn't in Mail. If it's not in Mail, MailMe 
doesn't know it exists.

Also, make sure you stop Growl before adding, changing, or deleting sending 
accounts in Mail, and start Growl again after. Otherwise, MailMe may use 
whatever old settings were current when Growl started.

Original comment by prhgr...@gmail.com on 17 Jul 2010 at 1:54

GoogleCodeExporter commented 9 years ago 
is there any update to this issue?

Original comment by atomicar...@gmail.com on 9 Feb 2011 at 3:41

GoogleCodeExporter commented 9 years ago 
If there were, we would have posted it here.

Original comment by prhgr...@gmail.com on 9 Feb 2011 at 5:15

GoogleCodeExporter commented 9 years ago 
I've attempted to fix this in [8da49fce81c3], but I can't test it, so I will 
need users who have this problem to test with the next beta and report back.

Original comment by prhgr...@gmail.com on 12 Mar 2011 at 4:05

GoogleCodeExporter commented 9 years ago

Original comment by p...@growl.info on 25 May 2011 at 4:44

GoogleCodeExporter commented 9 years ago 
Truly fixed (as far as we're aware) in [a2ee79fb077e].

Original comment by p...@growl.info on 25 May 2011 at 5:24