Re: [MlMt] error "Mailbox unexpectedly already exists"
On 21 Oct 2019, at 14:49, Sam Hathaway wrote: Try unsubscribing from the mailbox in Edit IMAP Account > Edit Subscriptions maybe? Huh, it wasn't even showing there. So I went into my Gmail labels again and turned on Show in IMAP for it, and now it is subscribed to in Mailmate's Edit Subscriptions, and I haven't seen the error pop up in a couple of hours. If it does appear again -- it always seemed to pop up at random -- I'll try unsubscribing from it in Mailmate while leaving Show in IMAP on in Gmail... Thanks for the suggestion! Shoshanna Green shoshan...@gmail.com ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Help creating a self-signed cert for S/MIME
On 21 Oct 2019, at 14:52, Bill Cole wrote:
You might get more information by looking at what MM logs. Make the
failure occur and then run this in a shell:
log show --debug --info --last 1m --predicate 'processImagePath
endswith "MailMate"'
That will show you the full details of what MM logged in the past
minute. It may have useful clues, or it may not.
Nothing clueful to me, but maybe to others:
$ log show --debug --info --last 1m --predicate 'processImagePath
endswith "MailMate"'
Filtering the log data using "processImagePath ENDSWITH "MailMate""
Timestamp Thread TypeActivity
PIDTTL
2019-10-21 15:03:19.935321-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] GetItemCount('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: -1)
2019-10-21 15:03:19.935323-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0 gen: 1627 count: 1
2019-10-21 15:03:19.935327-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyItemsAndFlavors('Apple CFPasteboard
find ( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9)'
gen: -1)
2019-10-21 15:03:19.935329-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0, gen: -1 item-count: 1 flavor-count: 1 (-1 means nil)
2019-10-21 15:03:19.935334-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyData('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: 1627
item: 789514 flavor: 'public.utf8-plain-text')
2019-10-21 15:03:19.935336-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
(cache) - result: 0 generation: 1627 data (5 bytes) flags: 2000
2019-10-21 15:03:19.935412-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] GetItemCount('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: -1)
2019-10-21 15:03:19.935413-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0 gen: 1627 count: 1
2019-10-21 15:03:19.935416-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyItemsAndFlavors('Apple CFPasteboard
find ( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9)'
gen: -1)
2019-10-21 15:03:19.935417-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0, gen: -1 item-count: 1 flavor-count: 1 (-1 means nil)
2019-10-21 15:03:19.935421-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyData('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: 1627
item: 789514 flavor: 'public.utf8-plain-text')
2019-10-21 15:03:19.935422-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
(cache) - result: 0 generation: 1627 data (5 bytes) flags: 2000
2019-10-21 15:03:19.935463-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] GetItemCount('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: -1)
2019-10-21 15:03:19.935463-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0 gen: 1627 count: 1
2019-10-21 15:03:19.935466-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyItemsAndFlavors('Apple CFPasteboard
find ( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9)'
gen: -1)
2019-10-21 15:03:19.935468-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
result: 0, gen: -1 item-count: 1 flavor-count: 1 (-1 means nil)
2019-10-21 15:03:19.935471-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] CopyData('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: 1627
item: 789514 flavor: 'public.utf8-plain-text')
2019-10-21 15:03:19.935472-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation) [com.apple.CFPasteboard:exit]
(cache) - result: 0 generation: 1627 data (5 bytes) flags: 2000
2019-10-21 15:03:19.935508-0500 0x2725a76 Info0x0
35500 0MailMate: (CoreFoundation)
[com.apple.CFPasteboard:entry] GetItemCount('Apple CFPasteboard find'
( C117FA88-B7A4-4A0F-95F1-289EFCCE55D9) gen: -1)
2019-10-
Re: [MlMt] Help creating a self-signed cert for S/MIME
On 21 Oct 2019, at 14:56, Pete Resnick wrote: > Still looking for help on this one. No luck so far. I'm all out of ideas because I can't reproduce the failure. That implies either a difference between 1.13 and the 2.0BETA equivalent (r6142) or something as yet unspecified and unknown. You might get more information by looking at what MM logs. Make the failure occur and then run this in a shell: log show --debug --info --last 1m --predicate 'processImagePath endswith "MailMate"' That will show you the full details of what MM logged in the past minute. It may have useful clues, or it may not. > On 18 Oct 2019, at 4:47, Pete Resnick wrote: > >> On 18 Oct 2019, at 2:13, Bill Cole wrote: >> >>> On 17 Oct 2019, at 17:45, Pete Resnick wrote: >>> Using MM 1.13 on Mojave. I tried creating a self-signed root S/MIME certificate in the Keychain, but when i try to use it, all I get it: The specified item could not be found in the keychain. (error code -25300) >>> >>> Generic "item not found" error (errSecItemNotFound.) >>> >>> You can get this when a cert (or any keychain item) doesn't have exactly >>> the right name )or other attribute used for matching the item to a >>> request,) lacks a needed attribute (like a "trusted" flag,) or is not in >>> the default keychain. Historically it also could happen with access control >>> issues, but I think Apple fixed that. >>> Obviously I'm missing something. Anyone have a recipe? >>> >>> In Keychain Access, use the Certificate Assistant to create a new cert. In >>> the firsdt screen of gthe creation wizard, give it a reasonable display >>> name, select "Self Signed Root" and "S/MIME (Email)" from the menus. Check >>> the "Let me override defaults" box and hit Continue. In the first screen, >>> enter the exact email address you want the cert to work for, without angle >>> brackets. Click through all the other screens without changes unless >>> there's something you KNOW you want to change, such as key type and size, >>> until you get to the "Subject Alternative Name" extension screen. Make sure >>> your address is there, in the "RFC 822 Name" field. Click through until >>> done, saving the cert in your default keychain, usually named "login". Open >>> the cert in Keychain Access, expand the Trust section, and select "Always >>> Trust" in the menu next to "When using this certificate:" which will apply >>> to all of the specific uses listed beneath. You can *probably* get away >>> with "Use Custom Settings" and only switching S/MIME to "Always Trust" but >>> I have not tried that. >>> >>> The first time you try to use the cert in MM, you will get a keychain >>> access authentication dialog. If you click "Always Allow after entering >>> your password, you won't be prompted that way aghain, it will Just Work in >>> MM. >>> Or some ideas about what I can check for what went wrong? >>> >>> Make sure the cert and its private key are in the default keychain, are >>> trusted, and have the right email address in both the Subject Name section >>> and the Subject Alternative Name extension. >>> >>> This message is signed with a cert I created as described above. I expanded >>> the allowed uses and used a ECC key, but those don't affect how MM works >>> with it. >> >> No joy in Mudville. I followed the recipe to the letter, and I get the same >> message. :-( Any other thoughts? >> >>> Thank you for all the work you've done to make Internet email viable and >>> robust. >> >> I'm not sure I want to take credit for the current state of Internet e-mail! >> :-D >> >>> And also for the bajillion occurrences of "x-stuff-for-pete" in my mail >>> archives. :) >> >> That was Steve's sense of humor. Some of the more "colorful" uses of my name >> appeared in the source code comments. >> >> pr > > > -- > Pete Resnick http://www.episteme.net/ > All connections to the world are tenuous at best > ___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire smime.p7s Description: S/MIME digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Help creating a self-signed cert for S/MIME
Still looking for help on this one. No luck so far. pr On 18 Oct 2019, at 4:47, Pete Resnick wrote: On 18 Oct 2019, at 2:13, Bill Cole wrote: On 17 Oct 2019, at 17:45, Pete Resnick wrote: Using MM 1.13 on Mojave. I tried creating a self-signed root S/MIME certificate in the Keychain, but when i try to use it, all I get it: The specified item could not be found in the keychain. (error code -25300) Generic "item not found" error (errSecItemNotFound.) You can get this when a cert (or any keychain item) doesn't have exactly the right name )or other attribute used for matching the item to a request,) lacks a needed attribute (like a "trusted" flag,) or is not in the default keychain. Historically it also could happen with access control issues, but I think Apple fixed that. Obviously I'm missing something. Anyone have a recipe? In Keychain Access, use the Certificate Assistant to create a new cert. In the firsdt screen of gthe creation wizard, give it a reasonable display name, select "Self Signed Root" and "S/MIME (Email)" from the menus. Check the "Let me override defaults" box and hit Continue. In the first screen, enter the exact email address you want the cert to work for, without angle brackets. Click through all the other screens without changes unless there's something you KNOW you want to change, such as key type and size, until you get to the "Subject Alternative Name" extension screen. Make sure your address is there, in the "RFC 822 Name" field. Click through until done, saving the cert in your default keychain, usually named "login". Open the cert in Keychain Access, expand the Trust section, and select "Always Trust" in the menu next to "When using this certificate:" which will apply to all of the specific uses listed beneath. You can *probably* get away with "Use Custom Settings" and only switching S/MIME to "Always Trust" but I have not tried that. The first time you try to use the cert in MM, you will get a keychain access authentication dialog. If you click "Always Allow after entering your password, you won't be prompted that way aghain, it will Just Work in MM. Or some ideas about what I can check for what went wrong? Make sure the cert and its private key are in the default keychain, are trusted, and have the right email address in both the Subject Name section and the Subject Alternative Name extension. This message is signed with a cert I created as described above. I expanded the allowed uses and used a ECC key, but those don't affect how MM works with it. No joy in Mudville. I followed the recipe to the letter, and I get the same message. :-( Any other thoughts? Thank you for all the work you've done to make Internet email viable and robust. I'm not sure I want to take credit for the current state of Internet e-mail! :-D And also for the bajillion occurrences of "x-stuff-for-pete" in my mail archives. :) That was Steve's sense of humor. Some of the more "colorful" uses of my name appeared in the source code comments. pr -- Pete Resnick http://www.episteme.net/ All connections to the world are tenuous at best ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] error "Mailbox unexpectedly already exists"
Try unsubscribing from the mailbox in Edit IMAP Account > Edit Subscriptions maybe? I’ve sometimes had luck getting mailboxes unstuck by unsubscribing, taking MlMt offline, back online, refreshing the IMAP folder list, etc. Not sure if it’ll work in your case but it’s another knob to fiddle with. On 21 Oct 2019, at 14:45, Shoshanna Green wrote: I'm still hoping someone can offer some suggestions for how to clear this error? I can send and receive mail through MailMate just fine, but the error message still appears every now and then. Thanks, Shoshanna Green On 14 Oct 2019, at 11:31, Shoshanna Green wrote: I tried to clean up some of my Gmail labels in this account, and obviously messed something up, because MailMate keeps popping up the following message: MailMate encountered the following error: “Mailbox unexpectedly already exists. Command: 'I6 CREATE "[Gmail]/Sent Mail"'.”. Mailbox: “[Gmail]/Sent Mail”. with options of "retry", "take account offline," and "try again later." I've been clicking the latter. I tried going back to my Gmail "manage labels" page on the Web at mail.google.com and deleting the "[Gmail]/Sent Mail" label (which never has any messages in it anyway), but that doesn't stop the error message from appearing, and when I check, the label has reappeared in Gmail's Web access. When I look at the [Gmail]/Sent Mail mailbox for this account in MailMate, it's greyed out and marked "(failed)", and MailMate reports about 600 messages in it, even though Gmail looked at through Web access says the label has 0 messages. My other Gmail account also has a "[Gmail]/Sent Mail" mailbox in MailMate, but it's greyed out and marked "(offline)". I tried taking the "[Gmail]/Sent Mail" mailbox that's throwing an error offline as well, and the attempt failed with the same "mailbox unexpectedly already exists" error. The mailing list archive includes a message from Sherman Wilcox this past March who had the same problem, and Benny said "this was solved off list. It was related to the Archive mailbox somehow having become unsubscribed (client side) and MailMate did not handle this well." But MailMate's Archive mailbox for this account seems fine -- I don't use it and there's nothing in it, but it's not greyed out or offline or anything. Can anyone advise? I promise I'll never try to tidy up Gmail again... Shoshanna Green shoshan...@gmail.com ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] error "Mailbox unexpectedly already exists"
I'm still hoping someone can offer some suggestions for how to clear this error? I can send and receive mail through MailMate just fine, but the error message still appears every now and then. Thanks, Shoshanna Green On 14 Oct 2019, at 11:31, Shoshanna Green wrote: I tried to clean up some of my Gmail labels in this account, and obviously messed something up, because MailMate keeps popping up the following message: MailMate encountered the following error: “Mailbox unexpectedly already exists. Command: 'I6 CREATE "[Gmail]/Sent Mail"'.”. Mailbox: “[Gmail]/Sent Mail”. with options of "retry", "take account offline," and "try again later." I've been clicking the latter. I tried going back to my Gmail "manage labels" page on the Web at mail.google.com and deleting the "[Gmail]/Sent Mail" label (which never has any messages in it anyway), but that doesn't stop the error message from appearing, and when I check, the label has reappeared in Gmail's Web access. When I look at the [Gmail]/Sent Mail mailbox for this account in MailMate, it's greyed out and marked "(failed)", and MailMate reports about 600 messages in it, even though Gmail looked at through Web access says the label has 0 messages. My other Gmail account also has a "[Gmail]/Sent Mail" mailbox in MailMate, but it's greyed out and marked "(offline)". I tried taking the "[Gmail]/Sent Mail" mailbox that's throwing an error offline as well, and the attempt failed with the same "mailbox unexpectedly already exists" error. The mailing list archive includes a message from Sherman Wilcox this past March who had the same problem, and Benny said "this was solved off list. It was related to the Archive mailbox somehow having become unsubscribed (client side) and MailMate did not handle this well." But MailMate's Archive mailbox for this account seems fine -- I don't use it and there's nothing in it, but it's not greyed out or offline or anything. Can anyone advise? I promise I'll never try to tidy up Gmail again... Shoshanna Green shoshan...@gmail.com ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
