Freron MailMate

Comments and changes to this ticket

• 

  benny August 29th, 2012 @ 06:18 AM

  What is the revision of MailMate you are using? (See the About window.)

  The beta versions of MailMate now use an Apple developer id for code signing (in order to work with Gatekeeper on Mountain Lion) and this means that you'll be asked to allow MailMate to read passwords in the keychain (because the code signature has changed). This should only happen once for each password and therefore your problem is much more serious, but it may be triggered by the change of code signature.

  Here are two ideas you could try out:

  • Open Keychain Access and then run the keychain verification in main menu (⌥⌘A).
  • Locate one of your account passwords in your keychain and remove it in order to let MailMate re-add it to the keychain (write the password down first).

• You flagged this item as spam.
  

  Mike K August 30th, 2012 @ 12:45 AM

  Thanks so much for your response. I'm using Version 1.4.2 (2818).

  I ran the Keychain Repair and got the following messages:

  Checked contents of ~/Library/Keychains/login.keychain
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “smtp.greentmail.com” is a duplicate; this item's port attribute is not set
  Item “mail.mac.com” has unspecified value for port attribute
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Item “imap.gmail.com” is a duplicate; this item's port attribute is not set
  Checked contents of ~/Library/Application Support/Adobe/AIR/ELS/TweetDeckFast.FFF259DC0CE2657847BBB4AFF0E62062EFC56543.1/PrivateEncryptedDatak
  Checked contents of ~/Library/Keychains/Microsoft_Intermediate_Certificates
  Problems were found; you should choose the Repair option to fix them
  Verification failed

  I quit MailMate, ran the keychain repair, and it gave similar errors then reported all as fixed. I then started MailMate again, and still had the same problem. So I quit MailMate, deleted all my email passwords from the keychain, opened MailMate again, Synchronized all, re-entered all my passwords as asked. Then 10 minutes later, I tried to synchronize again, and it repeatedly started asking for all my passwords again. I re-ran keychain repair and it reported no problems found.

  Right now Outlook, Postbox, and Apple Mail, which I had previously set up from before I started using Mailmate, are sending and receiving mail just fine using the passwords stored on the keychain.

  I'll try updating to a more recent beta. Right now MailMate reports that the update server is down.

• 

  benny August 30th, 2012 @ 06:11 AM

  Thanks for the thorough experiments. I don't think Postbox uses the keychain, but it certainly indicates that the problem is somehow related to MailMate.

  The screenshot indicates that the password does not exist in the keychain, so maybe the problem is that MailMate cannot successfully write to the keychain. Check Console.app for any related output.

  Also, open Keychain Access and see if you can find any of the passwords after re-entering them. Also check that MailMate is on the list of applications allowed to access the passwords.

  (And you are also welcome to try the latest beta, but I don't think anything related to this problem has been fixed.)

• You flagged this item as spam.
  

  Mike K August 31st, 2012 @ 02:35 AM

  All console.app says is this, over and over again:

  8/30/12 7:02:06 PM [0x0-0x3ce3ce].com.freron.MailMate[6729] SecKeychainFindInternetPassword failed with error: -67061

  I checked all the keychain entries, they are all set so MailMate can access them.

  I used MailMate for about a week without any issue, this started very suddenly, and I can't use the program at all like this.

  Fortunately I'm still on my evaluation period of Mailmate, I regret that I won't be buying it, because until this dealkiller it seemed like the only usable email client for Mac... since the demise of Eudora I've literally tried every Mac email client on the market, and until now MailMate had been the only one that didn't have a showstopper bug or crucial features missing. So I regret that it has turned totally unusable.

  Thanks for your efforts, and good luck with the app. In terms of features, you're definitely on the right path. I'll keep an eye on this thread, and if this issue is ever fixed I'll try MailMate again.

  If there's any other troubleshooting info I can give you, please let me know, I'd love to see MailMate become usable.

• You flagged this item as spam.
  

  Mike K August 31st, 2012 @ 02:36 AM

  Oh, also, the update server is still down.

• 

  benny August 31st, 2012 @ 06:25 AM

  Thanks for the details. I hope you are willing to try a few more things. The problem really should be solvable since no one else has reported it.

  The error reported in console.app is:

  errSecCSSignatureFailed =           -67061, /* invalid signature (code or signature have been modified) */
  

  Since I'm very sure the code signature is fine then I suggest you re-download MailMate from the homepage. I think your local copy may somehow have been modified/corrupted.

  With respect to the update server then it is not down and it is not know to have been down recently. Are there any special network conditions at your location? (The update server is the same server as the homepage.)

• You flagged this item as spam.
  

  Mike K September 4th, 2012 @ 10:36 PM

  Redownloading the app seems to have solved the password problem. It still tells me the update server is down when I hit the "Check Now" button, but the Updates pane indicates it last checked a half hour ago, so I don't know what to make of that. Overall, it seems to be working again for me, though.

• 

  benny September 5th, 2012 @ 08:13 AM

  • State changed from “new” to “resolved”

  I'm glad redownloading worked. I should have suggested it earlier on. You should also note that this may be an early sign of hard disk failure.

  I cannot reproduce any problems with the “Check Now” button. Let me know if you see some kind of pattern with regard to this behavior.

• You flagged this item as spam.
  

  Mike K October 31st, 2012 @ 09:48 PM

  Happening again. I'll try redownloading again.

  I'm also having numerous other problems with it... crashing, etc. I'll open up separate tickets for them.

• You flagged this item as spam.
  

  Mike K October 31st, 2012 @ 09:55 PM

  Yep, re-downloading solved it again.

• 

  benny November 1st, 2012 @ 08:59 AM

  You should allow MailMate to send the crash reports to me (see the General preferences pane). It still sounds like you might have a flaky disk, but if you only have problems with MailMate then that theory might be wrong.

  If it happens again then you could zip MailMate.app and send it to me. Then I can compare it with a clean copy of MailMate to find out what could trigger this problem.