Mail 1.3.11, Keychain 3.1.4

When importing certificate (blue) to Keychain, there is no option for X509 Anchor. Trust settings, when changed, are never saved. Lost...

What do you mean? Which version of Mac OS X are you using? You cannot use Mail 1.x on Mac OS X 10.4 (Tiger), nor Mail 2.x on Mac OS X 10.3 (Panther)...

Similar Messages

Moving Mail, Address Book and Keychains from Old Computer to New Computer

My issue: Moving mail, address book and keychains from Panther (old machine) to Leopard (new machine). Old machine (500mh G4 power pc) will not connect directly via firewire to new machine (iMac intel). So, I have to move the files manually via a firewire hard drive.
I am looking for a document that will tell me exactly which files to move. Can someone please help me find this document? Thank you. Dale
P.S. I have no issues with installing Leopard. I only need to move the mail, address book and keychains from old to new machine. No .mac account is available.

for address book: go to your old mac, launch ab, and go to file>export and export your contacts as vcards, select all cards before that, then bring that export file to the new mac, and launch ab there, then go to file>import as vcards and you should be set as far as contacts are, but not as far as groups if you have extensive groups. that would be the safe option. the other option is to go to homefolder/library/application support/address book and move that folder to the new mac. the only question i have is... is the database structure and files the same between panther and leopard, which is why i suggest the first option of import/export of vcards.
for mail, in your old panther go to homefolder/library/mail and move that mail folder to the new mac. make a copy of that folder, then move one copy to the same location in the new mac.
for keychain, in your old panther go to homefolder/library/keychain, you want to bring the file that is in that folder to your new mac. make a copy of that folder, then move one copy to the same location in the new mac.
once that is done, you may have to do some more steps with mail, once you launch mail, such as importing mailboxes. let me know if that is the case.
hope this helps

Mail.app blocked from Keychain access by Sandboxd

Working on a clean install of Yosemite. Worked perfect for the first 2 weeks. Then mail all of a sudden cannot send without putting in admin creds for keychain access. I have done all the keychain resets, removed the account and re-added it. Obviously there has to be a way to add an application to trusted status for Security Server/sandbox to allow it access. The question is where and how.
From Log Files:
12/8/14 9:44:33.493 AM com.apple.SecurityServer[57]: Sandbox denied authorizing right 'system.keychain.modify' by client '/Applications/Mail.app' [1240]
12/8/14 9:44:34.175 AM sandboxd[302]: ([1240]) Mail(1240) deny authorization-right-obtain system.keychain.modify
12/8/14 9:58:06.604 AM com.apple.SecurityServer[57]: Sandbox denied authorizing right 'system.keychain.modify' by client '/Applications/Mail.app' [1240]
Full Report Output:
Mail(1240) deny authorization-right-obtain system.keychain.modify
Process: Mail [1240]
Path: /Applications/Mail.app/Contents/MacOS/Mail
Load Address: 0x104b86000
Identifier: com.apple.mail
Version: 1993 (8.1)
Build Info: 1-Mail~1993000000000000
Code Type: x86_64 (Native)
Parent Process: launchd [1]
Date/Time: 2014-12-08 09:44:33.531 -0500
OS Version: Mac OS X 10.10.1 (14B25)
Report Version: 8
Thread 0:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 CoreFoundation 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2 CoreFoundation 0x00007fff839a6fdb __CFRunLoopRun + 1371
3 CoreFoundation 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4 HIToolbox 0x00007fff8f99d43f RunCurrentEventLoopInMode + 235
5 HIToolbox 0x00007fff8f99d1ba ReceiveNextEventCommon + 431
6 HIToolbox 0x00007fff8f99cffb _BlockUntilNextEventMatchingListInModeWithFilter + 71
7 AppKit 0x00007fff80c626d1 _DPSNextEvent + 964
8 AppKit 0x00007fff80c61e80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
9 AppKit 0x00007fff80c55e23 -[NSApplication run] + 594
10 AppKit 0x00007fff80c412d4 NSApplicationMain + 1832
11 libdyld.dylib 0x00007fff851d95c9 start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff82a1322e kevent64 + 10
1 libdispatch.dylib 0x00007fff88ac9a6a _dispatch_mgr_init + 0
Thread 2:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 CoreFoundation 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2 CoreFoundation 0x00007fff839a6fdb __CFRunLoopRun + 1371
3 CoreFoundation 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4 CFNetwork 0x00007fff89e14d20 +[NSURLConnection(Loader) _resourceLoadLoop:] + 434
5 Foundation 0x00007fff8ee8bb7a __NSThread__main__ + 1345
6 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
8 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff82a123f6 __select + 10
1 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
2 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
3 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 CoreFoundation 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2 CoreFoundation 0x00007fff839a6fdb __CFRunLoopRun + 1371
3 CoreFoundation 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4 AppKit 0x00007fff80dc57a7 _NSEventThread + 137
5 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
7 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 QuartzCore 0x00007fff8ec07d63 CA::Render::Server::server_thread(void*) + 198
2 QuartzCore 0x00007fff8ec07c96 thread_fun + 25
3 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
4 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
5 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff82a12132 __psynch_cvwait + 10
1 libc++.1.dylib 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2 JavaScriptCore 0x00007fff8df8d2d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3 JavaScriptCore 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
4 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
5 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
6 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff82a12132 __psynch_cvwait + 10
1 libc++.1.dylib 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2 JavaScriptCore 0x00007fff8df8d86b JSC::GCThread::waitForNextPhase() + 171
3 JavaScriptCore 0x00007fff8df8d6c8 JSC::GCThread::gcThreadMain() + 88
4 JavaScriptCore 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
5 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
7 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff82a12132 __psynch_cvwait + 10
1 libc++.1.dylib 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2 JavaScriptCore 0x00007fff8df8d2d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3 JavaScriptCore 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
4 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
5 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
6 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff82a12132 __psynch_cvwait + 10
1 libc++.1.dylib 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2 JavaScriptCore 0x00007fff8df8d86b JSC::GCThread::waitForNextPhase() + 171
3 JavaScriptCore 0x00007fff8df8d6c8 JSC::GCThread::gcThreadMain() + 88
4 JavaScriptCore 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
5 libsystem_pthread.dylib 0x00007fff8d0cc2fc _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff8d0cc279 _pthread_body + 0
7 libsystem_pthread.dylib 0x00007fff8d0ca4b1 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 12:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff82a12132 __psynch_cvwait + 10
1 Foundation 0x00007fff8ee5d400 -[NSCondition waitUntilDate:] + 343
2 IMAP 0x00007fff8d3df027 -[IMAPGateway isExpensive] + 424
3 IMAP 0x00007fff8d3fca6b -[IMAPMailboxSyncEngine _cacheMessagesWithMonitor:] + 847
4 IMAP 0x00007fff8d3f68b2 -[IMAPMailboxSyncEngine _goWithMessages:] + 2339
5 IMAP 0x00007fff8d3f6c79 -[IMAPMailboxSyncEngine _goWithMessagesIfNeeded:] + 61
6 CoreFoundation 0x00007fff8397033c __invoking___ + 140
7 CoreFoundation 0x00007fff83970192 -[NSInvocation invoke] + 290
8 MailCore 0x00007fff8d2250cc -[MCMonitoredInvocation invoke] + 242
9 MailCore 0x00007fff8d24f1d4 -[MCThrowingInvocationOperation main] + 48
10 MailCore 0x00007fff8d1d771d -[_MCInvocationOperation main] + 426
11 Foundation 0x00007fff8ee2b59c -[__NSOperationInternal _start:] + 653
12 Foundation 0x00007fff8ee2b1a3 __NSOQSchedule_f + 184
13 libdispatch.dylib 0x00007fff88ac6c13 _dispatch_client_callout + 8
14 libdispatch.dylib 0x00007fff88aca365 _dispatch_queue_drain + 1100
15 libdispatch.dylib 0x00007fff88acbecc _dispatch_queue_invoke + 202
16 libdispatch.dylib 0x00007fff88ac96b7 _dispatch_root_queue_drain + 463
17 libdispatch.dylib 0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
18 libsystem_pthread.dylib 0x00007fff8d0cc6cb _pthread_wqthread + 729
19 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 CoreFoundation 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2 CoreFoundation 0x00007fff839a6fdb __CFRunLoopRun + 1371
3 CoreFoundation 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4 Foundation 0x00007fff8ee8dab9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 278
5 AppKit 0x00007fff80ebfa98 -[NSAnimation(NSInternal) _runBlocking] + 390
6 AppKit 0x00007fff80ebf8ea -[NSAnimation(NSInternal) _animationThread] + 66
7 libdispatch.dylib 0x00007fff88acb323 _dispatch_call_block_and_release + 12
8 libdispatch.dylib 0x00007fff88ac6c13 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff88ac988f _dispatch_root_queue_drain + 935
10 libdispatch.dylib 0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
11 libsystem_pthread.dylib 0x00007fff8d0cc6cb _pthread_wqthread + 729
12 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff82a0d52e mach_msg_trap + 10
1 Security 0x00007fff8f32cf80 ucsp_client_generateSignature + 200
2 Security 0x00007fff8f332958 Security::SecurityServer::ClientSession::generateSignature(Security::Context const&, unsigned int, Security::CssmData const&, Security::CssmData&, Security::Allocator&, unsigned int) + 190
3 Security 0x00007fff8f23a6f6 SSSignatureContext::sign(Security::CssmData&) + 370
4 Security 0x00007fff8f23a565 SSSignatureContext::outputSize(bool, unsigned long) + 183
5 Security 0x00007fff8f1bd645 Security::CSPFullPluginSession::CSPContext::final(Security::CssmData&, Security::Allocator&) + 33
6 Security 0x00007fff8f33bfe0 cssm_SignData(long, unsigned long long, cssm_context const*, cssm_data const*, unsigned int, unsigned int, cssm_data*) + 307
7 Security 0x00007fff8f34cb66 CSSM_SignData + 103
8 Security 0x00007fff8f21a7fa SEC_SignData + 256
9 Security 0x00007fff8f219204 SecCmsSignerInfoSign + 434
10 Security 0x00007fff8f2183b4 SecCmsSignedDataEncodeAfterData + 264
11 Security 0x00007fff8f2157d9 nss_cms_encoder_notify + 912
12 Security 0x00007fff8f1bfd7d SEC_ASN1EncoderUpdate + 385
13 Security 0x00007fff8f215b5e SecCmsEncoderFinish + 158
14 Security 0x00007fff8f2618fc CMSEncoderCopyEncodedContent + 136
15 MailCore 0x00007fff8d246696 -[MCMimePart(SMIMEEncoding) newSignedPartWithData:sender:signatureData:] + 4621
16 MailCore 0x00007fff8d1f0a24 -[MCMessageGenerator _newOutgoingMessageFromTopLevelMimePart:topLevelHeaders:withPartData:] + 632
17 MailCore 0x00007fff8d1edd2e -[MCMessageGenerator newMessageWithHtmlString:plainTextAlternative:otherHtmlStringsAndAttachments:he aders:] + 3105
18 Mail 0x0000000104c26f39
19 Mail 0x0000000104c25e18
20 Mail 0x0000000104c243bd
21 CoreFoundation 0x00007fff8397033c __invoking___ + 140
22 CoreFoundation 0x00007fff83970192 -[NSInvocation invoke] + 290
23 MailCore 0x00007fff8d2250cc -[MCMonitoredInvocation invoke] + 242
24 MailCore 0x00007fff8d24f1d4 -[MCThrowingInvocationOperation main] + 48
25 MailCore 0x00007fff8d1d771d -[_MCInvocationOperation main] + 426
26 Foundation 0x00007fff8ee2b59c -[__NSOperationInternal _start:] + 653
27 Foundation 0x00007fff8ee2b1a3 __NSOQSchedule_f + 184
28 libdispatch.dylib 0x00007fff88ac6c13 _dispatch_client_callout + 8
29 libdispatch.dylib 0x00007fff88aca365 _dispatch_queue_drain + 1100
30 libdispatch.dylib 0x00007fff88acbecc _dispatch_queue_invoke + 202
31 libdispatch.dylib 0x00007fff88ac96b7 _dispatch_root_queue_drain + 463
32 libdispatch.dylib 0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
33 libsystem_pthread.dylib 0x00007fff8d0cc6cb _pthread_wqthread + 729
34 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 16:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 17:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 20:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 21:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 23:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 24:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 25:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 26:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 29:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 30:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 31:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Thread 32:
0 libsystem_kernel.dylib 0x00007fff82a12946 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8d0ca4a1 start_wqthread + 13
Binary Images:
 0x104b86000 - 0x104f1bff7 com.apple.mail (8.1 - 1993) <dc7d598c-884d-3bc3-9d97-f2cb5d1ed551> /Applications/Mail.app/Contents/MacOS/Mail
 0x7fff80c3e000 - 0x7fff8177ffff com.apple.AppKit (6.9 - 1343.16) <c98db43f-4245-3e6e-a4ee-37daee33e174> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
 0x7fff81f43000 - 0x7fff81f97fff libc++.1.dylib (120) <1b9530fd-989b-3174-bb1c-bdc159501710> /usr/lib/libc++.1.dylib
 0x7fff829fc000 - 0x7fff82a19fff libsystem_kernel.dylib (2782.1.97) <93e0e0a9-75b6-3904-bb4e-4bc7c05f4b6b> /usr/lib/system/libsystem_kernel.dylib
 0x7fff83935000 - 0x7fff83ccbfff com.apple.CoreFoundation (6.9 - 1151.16) <f2b088af-a5c6-3fae-9eb4-7931af6359e4> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff851d6000 - 0x7fff851d9ff7 libdyld.dylib (353.2.1) <19faf435-c165-3374-9def-d7bba7d61db6> /usr/lib/system/libdyld.dylib
 0x7fff88ac5000 - 0x7fff88aefff7 libdispatch.dylib (442.1.4) <502cf32b-669b-3709-8862-08188225e4f0> /usr/lib/system/libdispatch.dylib
 0x7fff89d74000 - 0x7fff89f77ff3 com.apple.CFNetwork (720.1.1 - 720.1.1) <a82e71b3-2cdb-3840-a476-f2304d896e03> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
 0x7fff8d0c9000 - 0x7fff8d0d2fff libsystem_pthread.dylib (105.1.4) <26b1897f-0cd3-30f3-b55a-37cb45062d73> /usr/lib/system/libsystem_pthread.dylib
 0x7fff8d19f000 - 0x7fff8d27eff7 com.apple.MailCore (8.1 - 1993) <dc6b9e54-74a0-37cd-b693-d54e79df491b> /System/Library/PrivateFrameworks/MailCore.framework/Versions/A/MailCore
 0x7fff8d3ab000 - 0x7fff8d42bff7 com.apple.IMAP (8.1 - 1993) <214b764f-2a95-3939-857b-ddaa92a2330d> /System/Library/PrivateFrameworks/IMAP.framework/Versions/A/IMAP
 0x7fff8df78000 - 0x7fff8e48bff3 com.apple.JavaScriptCore (10600 - 10600.1.17) <ce5255cc-e13f-3694-b6dd-5285356bfcc0> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
 0x7fff8ebe0000 - 0x7fff8ed90ff7 com.apple.QuartzCore (1.10 - 361.11) <7382e4a9-10b0-3877-b9d7-fa84dc71ba55> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
 0x7fff8ee23000 - 0x7fff8f151ff7 com.apple.Foundation (6.9 - 1151.16) <18edd673-a010-3e99-956e-da594ce1fa80> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
 0x7fff8f19b000 - 0x7fff8f403ffb com.apple.security (7.0 - 57031.1.35) <96141d1f-614e-32c4-8ac2-f47481f23f43> /System/Library/Frameworks/Security.framework/Versions/A/Security
 0x7fff8f96f000 - 0x7fff8fc71fff com.apple.HIToolbox (2.1.1) <9dd121b5-b7eb-3c43-8155-61a4417f8e9a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox

I'm having the same issue since yesterday night, after changing the configuration of one specific SMTP connection.
Mail has been asking me for passwords several times in a row on every click in the inbox or on sending a mail.
The log message is the same, along the lines of "Mail(xxx) deny authorization-right-obtain system.keychain.modify".

Mail 6.0 or Keychain problem with passwords

I'm using Mountain Lion and mail 6.0 but it seems that mail or keychain keeps on asking for my password.
Mail bounces on by dock because it needs attention. When I go to it, I see a dialogue that says "cannot coonect to the server"
It is asking me for my password. However, I can see that the password is already entered and all I have to do is click OK and the problem is gone until after about 5 minutes. It starts all over again.

Patrick,
I have experienced the same symptoms.
Opening Audio MIDI Setup, and changing the Built-in Output>Format to another choice (2ch-20bit Integer) and then back to the prvious setting (2ch-24bit Integer) briefly fixes the lack of Mail sounds, but unfortunately the problem eventually returns after computer sleep.
I have tried a Safe Boot, and removed the Audio MIDI plist without success.

Mail Keeps Asking For Keychain Password - Possible Solution

Hi
I am a Mac newbie and all was going well until I played around with the Keychain settings and then, despite putting everything on Keychain back to how it was, I kept getting requests from Mail to enter my password.
Having tried every other solution offered by the various help sites and web forums (this problem seems quite common), I finally went for the deleting the mail account solution that (fingers crossed) has now worked for over a day, so I am posting it here in case it is useful to someone else:
-     First I deleted the two keychain password references to Mail that were in the Keychain Access list (POP and SMTP) and made sure Keychain settings       were all back to how they were originally.
-     Then I archived all my mail and mail folders - was easy to do and then reload again later.
-     Then I deleted my email account; rebooted; went back into mail and went through the process of setting up my account again.
-     Reloaded my mail messages and folders and tidied things up to how they were.
-     Let keychain set up the mail passwords again by sending and receiving a test message to myself.
Hey presto! Everything now appears back to how it was, without those annoying requests for passwords for Mail.
I am pretty sure this problem arose due to me changing the keychain settings, even though I put everything back to how it was (or at least I think I did!) it's almost as though there is a bug that makes Mail think the settings have not been changed back to "normal" again.
Hope this help's someone (took me about half a day to fix this as all sorts of solutions are offered by the help sites and forums, but none fixed the problem until I went through the procedure above).

Still, that was quite funny....!
Erm, I'm still having this problem along with several others that have gone unanswered on here about why Mac Mail decides to keep all my trash, junk, sent, but clears out the INBOX every 5 or 7 days. No server problems, No settings changed... For a computer I bought to make my life easier, its sure making me work exceedingly hard for it. I'm this close to going back to Windows. DON'T LET ME DO IT!!!!!!!!! Helllllp!!!!

Mail keeps asking me keychain until I visit mail provider on safari

Hi, for some reason, when I open mail up it asks me for my "keychain" password, in this case my password I use to login to my hotmail. But, for some reason it will not accept the password untill I open up Safari and actually log into my hotmail.
How can I solve this issue? Thanks.

Woohoo! I got it fixed
Apparently the keychain is often corrupted for many people after upgrading to 10.4 to Leopard.
The fix is (in my case) to run the "keychain first aid". There are step-by-step instructions on the following link (they suggest booting up in Safe Mode first... I did not (thats your call)).
http://1passwd.com/help/607/keychain/usingkeychainaccess
Good Luck,
Jeff.C

FIXED! How I fixed Mail not remembering passwords, keychains, certificates

As noted in this lengthy thread, hundreds of users who upgraded to Leopard were experiencing their email accounts not remembering their passwords in Mail. Since the upgrade to Leo, I was seeing this, too. Every hour or so, I'd need to reenter all the passwords to all 8 emails that I had. I also was seeing odd keychain behavior with Safari. I'd need to re-enter passwords and certificates over and over again.
From reading the above thread, a couple posters had come up with a fix. I modified it slightly, and for the past 3 days, everything has worked perfectly. Note that I'm no geek, don't really get why it worked, and basically attacked this like a man with a shotgun shooting a mouse. So what I did may break your system or cause you to die from cancer. But here's the steps I did that eliminated the problem
1. I quit Mail & Safari.
2. I opened up Keychain Access (in Utilities) and deleted everything I possibly could. I initially tried to just delete Mail and Safari-related stuff, but that didn't work, so I deleted everything the system allowed me to delete.
3. I ran Keychain First Aid (Menu: Keychain Access). I re-ran it about 4 times until it couldn't repair anything further (there was a dozen things it said it couldn't change, but there you go).
4. I then hooked up a second Mac, via Firewire, that had recently had a clean install of Leopard on it. I dragged the Mail app file over into the applications folder had it replace the existing Mail app.
5. I did the same with Safari, replacing the existing Safari app file.
(NOTE: I hear you can do essentially the same thing for steps 4 and 5, using your original Leopard install discs and a program called Pacifist, but that was more techie than I felt comfortable with. But I hear it does the same thing as copying over clean virgin copies of Mail and Safari, as I did in steps 4 and 5)
6. I then repaired permissions (via the Disk Utility in Utilities). I think this step is a little like smudging with sage, or chanting, but in fact both the new Safari and the Mail app needed thousands of repairs, so perhaps this wasn't as voodoo as suspected.
7. I then restarted the Mac. Upon opening up Mail, I did, of course, need to re-enter all of the passwords again. But that was it. That was 3 days ago, and I've been groovy ever since. I've restarted the apps, and restarted the Mac numerous times. So far, all passwords and keychains and certificates have remained solid.
So there you go. How I Fixed a Hair-Pulling Glitch in my Otherwise Nice Leopard System.
Scott
http://www.braintoniq.com

Did you copy both key3.db and signons.sqlite to the profile folder?
You can use this button to go to the Firefox profile folder:
*Help > Troubleshooting Information > Profile Directory: Open Containing Folder
It is possible that there is a problem with the files key3.db and signons.sqlite that store the encrypted names and passwords in Firefox. 
Rename the files key3.db and signons.sqlite in the Firefox profile folder. 
You can add .old to the file names (key3.db.old and signons.sqlite.old) or move them to another folder to make it possible to undo the action. 
You need to set a new Master Password after renaming or deleting key3.db and all currently saved passwords are lost. 
If that has worked then you can remove the renamed files that are no longer needed. 
* "Troubleshooting" in http://kb.mozillazine.org/Password_Manager

Mail, POP Account, and Keychain password

DIdn't see a "Mail" forum so posted here.
New behavior on the computer, not related to any software update or other changes.
Recently I get a dialog box stating that the ISP server rejected my password, please enter password. The box also offers to keep a copy in my keychain. Thought it might be too many of the same pw in the keychain, so went to keychain access and ensured there's one incoming and one outgoing pw for the ISP in the list. Also did the keychain repair thing and no problems found.
It's an inconsistent behavior, and I'm not sure if there's not a problem at the ISP end. I get mail, but the dialog box every time the computer checks for mail is distracting. Any ideas?

Are all your mailboxes online or greyed out?
Occasionally mine have gone offline when the request for a password has been made.
If any are offline put them back using these instructions from Ernie:-
Click on Mailbox and then on Online Status -- select this account and say to take it back Online. Then Quit Mail, and relaunch. Your provider probably had a problem, and this double step approach should get things back to normal, if the provider has recovered on their end.

Mail & Safari ignoring default keychain setting on 10.9 Mavericks

Regardless of which keychain is set as default Apple Mail and Safari seem to always store saved passwords in the "local items" keychain instead of the one selected as default. Even worse, Mail is not even able to use account passwords stored in another keychain.
What's the point in having a default keychain setting if it is ignored by two major applications using keychains? Does anyone know why there are some applications respecting the default setting and some that are not?

SSD drives have no moving parts so are generally much more reliable than ordinary hard disks so the need for RAID1 is less. However Mail is nowadays regarded as a business critical service so you still want to minimise downtime.
Unfortunately Apple don't make it practical to implement a server cluster using their software which would be the best approach. Other than using a different product like Microsoft Exchange which can be used in a cluster but would cost enormously more, I would use an external hardware RAID solution, perhaps the Promise Pegasus R4.
See http://www.promise.com/storage/raid_series.aspx?m=192&region=en-global&rsn1=40&r sn3=47
I did also find recently the following which is a FireWire external RAID enclosure for 2.5" drives but also includes hardware RAID1 support. You could use two 1TB 2.5" drives in it. It can be powered via FireWire so does not even have a power supply to possibly fail.
See http://eshop.macsales.com/shop/firewire/EliteALmini/RAID/eSATA_FW800_FW400_USB
As Simon mentioned you could also use a hosted mail solution, there is even the option of Office365 with the add-on of MS Exchange.

Mail requires password for keychain

Just recently, every time I open Mail, it requires that I put in my password so that my keychain can be accessed. If anyone knows how to prevent this, I would really appreciate the info.
Thanks -
Dudley Warner

Still, that was quite funny....!
Erm, I'm still having this problem along with several others that have gone unanswered on here about why Mac Mail decides to keep all my trash, junk, sent, but clears out the INBOX every 5 or 7 days. No server problems, No settings changed... For a computer I bought to make my life easier, its sure making me work exceedingly hard for it. I'm this close to going back to Windows. DON'T LET ME DO IT!!!!!!!!! Helllllp!!!!

Why is mac mail and ical always asking for my login keychain?

This problem is driving me crazy! Every time I close my Mac and then reopen it, I get windows saying that Mail needs my login keychain, and the same for iCal and sys admin. I've done the KeyChain first aid and nothing works. Help!

Applications/Utilities/Keychain Access. Try deleting your Mail and Calendar passwords.
Password not Saved
Password – Mail keeps asking for Password

Cannot deny Keychain access in Mail application anymore

in Lion when i first steup my Mail account and it asked to enter my mail password, the dialog asking for the Keychain password had a button "deny", so that the Mail application wont use the Keychain.
Now in Mountain Lion i dont have the deny Button anymore, and the dialog keeps poping up all the time cause Mail wants to store my mail password to the Keychain. But i dont want that!!! I could'nt find any way to prevent Mail from using the Keychain. Can anyone help me here?
Thanks

I am having issues with Keychains since the upgrade. Drives me crazy, as it randomly asks if it can have access to my calendars.
Keep selecting Deny every 10 minutes twice in a row. Interesting thing is I haven't even launched calendars, and haven't even sinced any device to this computer.
Really makes me cranky.
Also, this assistantd also drives me crazy. Mountain Lion so far brought me only nuisance.

OS X mail won't open after upgrade to 10.2.8...requires keychain password

Help please! I have upgraded one of the school secretaries eMac to OS 10.2.8 and now mail will not open. Instead, I get the message "Mail wants acess to keychain password or phrase".
Mail worked fine in 10.2.4 before the upgrade.
I have read several posts and keychain help but have found no solutions. Administrator password and mail password are not the same, if that makes any difference.
Any help here is appreciated.
Tom L

For future reference, when you're having keychain issues, you can always reset your password without having the old one by booting to install disk 1. 10.3.9 or earlier click the installer menu and choose reset password. 10.4 or higher, click the Utilites menu and choose reset password. Enter password, verify it. Quit reset password, quit installer, restart system. When you get back to the OS, go to System Preferences, go to accounts and choose to change your password. Even if you use the same password, it's okay because it will reset your keychain password to match your admin password.

I downloaded OS X maverick but now can't get into mail or enter keychain password. Nothing is working

I downloaded OS X to my Mac book pro. Now I can't get into yahoo mail or enter my keychain password. What should I do?

Do you have OS X and OS 9 installed on your Mac? If so, startup with the Option key depressed. This will open the Startup Manager window. Select the OS you want to start from & click the right arrow.
 Cheers, Tom

Mail wants to use the "login" keychain

I have recently upgraded my macbook pro to the next gen mac book pro. When starting up my new computer i tranfered all of the info from my old mac to my new mac via the welcome screen that appears when starting up a new mac for the first time. After this, a problem is occuring in mail. Everytime I open mail after i restart my computer, a window appears and asks the question 'Mail wants to us the "pattygeorge" keychain". I cannot stop this no mater what i try. What I found is that the new computer has shortname that differs from my old computer shortname i.e. patgeorge (new) vs. pattygeorge(old). Please help me remedy this

Strgzr wrote:
Mark I too am getting request each time I restart iMac that "Mail wants to access keychain". I don't know what you mean from this pic which thing to move to where? Please explain:(I blocked out pers.info in pic)
I didn't make a specific suggestion to the previous poster, and I don't have a specific suggestion for you.
Mail will want access to some keychain if you told it to save passwords; that's where it saves them. The keychain named "login" (the top one at the left of your picture) is usually unlocked when you log in. If your mail password is stored in a keychain not currently unlocked, the system will ask if it is OK for Mail to access that keychain.
You have five keychains. Three (login, System, and System Roots) are standard. I can guess that the Symantec keychain is used by some Symantec software you have installed. I have no idea what the one that starts "Priva" and ends "tedDatak" is.
The message you get should indicate the name of the keychain that Mail is trying to access. (In the original question, 'Mail wants to us the "pattygeorge" keychain", "pattygeorge" was the keychain name.) If you want to have the mail passwords available to Mail without prompting, you can move their entries from a locked keychain to one that is already unlocked when Mail wants to access them.
The mail passwords should be of type "Internet password" and should have names corresponding to the names of your mail servers. For example, imap.gmail.com and smtp.gmail.com for Gmail reading and sending respectively.

Mail 1.3.11, Keychain 3.1.4

Similar Messages

Maybe you are looking for