#471 new
Rob Schumann

MailMate crashing after launch

Reported by Rob Schumann | October 30th, 2013 @ 12:11 PM


I'm getting the following entry at a MailMate crash in the MM logfile.

Fatal: Private namespace is already part of the mailbox name.
Destination mailbox: INBOX/Junk Private namespace: INBOX

Everything was fine up until I left the office this morning. Upon return I found it had crashed and now won't get further than just after a full startup... i.e. it seems to startup OK, retrieve any messages that need downloading... sit quietlt for a few seconds (perhaps 10-15) and then poof! It's crashed with this (repeatable) message.

Any thoughts on cause, and especially recovery welcome.



Comments and changes to this ticket

  • benny

    benny October 30th, 2013 @ 12:17 PM

    Thanks for the report. I've been kind of waiting for this since it's been reported before and I was unable to fix it before it resolved itself. The crash you get is a check I've inserted before MailMate starts recursively creating INBOX folders like this:


    That also ends up in a crash, but it also requires some cleanup.

    Could you restart MailMate after pasting this in the Terminal:

    defaults write com.freron.MailMate MmDebugRecursiveName -bool YES

    It should generate some more output before crashing.

    Sorry about the inconvenience. Hopefully I can get this bug fixed with your help.

  • Rob Schumann

    Rob Schumann October 30th, 2013 @ 12:35 PM

    Hi Benny,

    For a moment I thought I may be going to disappoint you as in poking around I'd managed to force a database rebuild after which it started OK, but with all accounts offline. I brought them all progressively online and still no problem. I then started expanding smart mailboxes, not expecting anything ugly, but when opening one with several nested smart mailboxes, bang... crashed again with the same error... restart also reproduced the same error, so here's the logfile dump you wanted (the above is in case it provides any further context):

    Looking for message on disk for id: 87  
     Filepath: /Users/rob/Library/Application Support/MailMate/Messages/IMAP/info%40webspaceworks.com@mail.webspaceworks.com/INBOX.mailbox/Junk.mailbox/Messages/87.eml
     Size: 5539860, Pointer: 0x152ea000
    First private namespace: INBOX  
     Destination mailbox: INBOX/Junk
     UTF7-name: "INBOX.Junk"
     private namespace: 'INBOX'
    Connection log appended to '/Users/rob/Desktop/MailMate_mail.webspaceworks.com_INBOX_Junk.txt'  
    Fatal: Private namespace is already part of the mailbox name.  
     Destination mailbox: INBOX/Junk
     Private namespace: INBOX
  • benny

    benny October 30th, 2013 @ 12:43 PM

    There is a bit of noise that you can disable:

    defaults write com.freron.MailMate MmDebugParserCrash -bool NO

    Also, a log file is mentioned in the output. Could I have that as well?

    Oh, I think I already see the problem. I'll get back to you.

  • Rob Schumann

    Rob Schumann October 30th, 2013 @ 12:45 PM

    Just in case... contents of the txt file on disk.

    Connection log (2013-10-30 12:30:51 +0000):  
    Adding 1 message(s)  
    C: I30 NOOP  
    S: I30 OK NOOP completed.  
    C: I31 LIST INBOX ""  
    S: * LIST (\Noselect) "." "INBOX."  
    S: I31 OK List completed.  
    C: I32 NOOP  
    S: I32 OK NOOP completed.  
    C: I33 APPEND "INBOX.Junk" ($Junk) "30-Oct-2013 11:55:20 +0700" {5611828}  
    S: I33 NO [OVERQUOTA] Quota exceeded (mailbox for user is full)  
    Error: Server response: “I33 NO [OVERQUOTA] Quota exceeded (mailbox for user is full)”. Command attempted: “I33 APPEND "INBOX.Junk" ($Junk) "30-Oct-2013 11:55:20 +0700" {5611828}”.  
    C: I34 NAMESPACE  
    S: * NAMESPACE (("INBOX." ".")) NIL NIL  
    S: I34 OK Namespace completed.
  • benny

    benny October 30th, 2013 @ 12:47 PM

    Oh, two problems.

    1. You have no more space in your account. This makes an upload fail.
    2. When the upload fails MailMate misinterprets the failure to mean that a private namespace is missing.

    I can fix number 2, but you need to fix number 1 yourself.

    Thanks for the great debug output. In theory, this is now a resolved issue.

  • Rob Schumann

    Rob Schumann October 30th, 2013 @ 01:11 PM

    Hi Benny,

    Thanks... fingers crossed, and no problem, happy to assist.

    Found the problem mailbox. Any chance the debugging info could be tweaked to assist in finding the problem a/c in cases such as these?



  • benny

    benny October 30th, 2013 @ 01:14 PM

    • State changed from “new” to “fixcommitted”

    I've just fixed the recursive mailbox creation bug and I'm now looking into catching the OVERQUOTA response code defined in RFC 5530. That should make it at least a bit easier to see what's going on for the user (and certainly much better than crashing :-) ).

    Thanks for your help.

  • Rob Schumann
  • benny

    benny November 11th, 2013 @ 11:56 AM

    • State changed from “fixcommitted” to “fixreleased”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket