Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Bad Parse Error, now crashing

#3144

For the last few days I've been getting a period message that:

"MailMate encountered the following error: “Server response: “I8 BAD Parse Error (took 0 ms)”.”. Mailbox: “Sent Messages”."

I tried downgrading to the release version, and also trying to see if there was a suspect message in that folder with no luck. Mailmate has also started crashing.

I have upgraded to Ventura, but I believe I got this message before doing that.

I'll try rebuilding the database in case it helps.

Reported by Kevin Miller · October 27th, 2022 @ 06:14 PM

State: closed
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny

    I don't think it's related to Ventura (or the MailMate database). Looks like an Exchange issue (weird non-informative error message). Probably related to uploading a sent message. Go to the Sent Messages mailbox, enable the UID column in the message list, and look for any messages which has no UID (waiting to be uploaded). One of these is likely to be the problem. You might need to delete it permanently by holding down ⌥ when using “Message ▸ Delete Immediately”. Don't do it if you need the message of course :)

    November 1st, 2022 @ 03:41 PM

  2. benny
    benny

    The crashes is likely a different (Ventura?) issue. You are welcome to send me crash reports via “Help > Send Feedback”.

    November 1st, 2022 @ 03:42 PM

  3. Kevin Miller
    Kevin Miller

    I was able to rebuild the database by moving the files outside of the library. It seems to have worked - no crashes, and no repeats of the error. I will follow up if it recurs.

    Thanks for a wonderful piece of software.

    November 1st, 2022 @ 08:56 PM

  4. benny
    benny
    • State changed from new to closed

    Rebuilding the database would also have the effect of deleting any non-uploaded drafts, but note that there might have been others waiting to be uploaded than the one causing the problem...

    (But Office365 stores its own copy of sent messages -- an entirely different unresolved problem.)

    November 2nd, 2022 @ 01:08 PM

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.