Freron MailMate

Comments and changes to this ticket

• 

  benny December 21st, 2015 @ 10:29 AM

  Thanks. The output does look very strange. Unfortunately it's not as informative as it could be. The problem is related to the message with UID 3541. You can see UIDs by enabling the UID column in the messages list. You can also enable “Raw Flags” to see which flags MailMate wants the message to have. I'd like to know that as well.

  Please don't delete the message since I would like to figure out what triggers the busy loop. You can take the mailbox offline to stop the busy looping for now.

  I'd like some more details logs like this. Paste the following line in a Terminal window:

  defaults write com.freron.MailMate LoggingEnabled -bool YES
  

  Then relaunch MailMate and let it busy loop a bit before using “Help ▸ Send Server Logs”.

  Thanks in advance!

• You flagged this item as spam.
  

  Henning Fueller December 21st, 2015 @ 01:13 PM

  Hi benny,

  Thanks for the quick response, very appreciated. I changed the defaults via Terminal but did not find the "Raw Flags" preference. It also took a little while for the problem to reappear. Maybe it is related to me training SpamSieve? At least, the problem reappeared after I clicked „Mark not as Junk" on a specific message.

  I sent you the server logs in a separate message.

  Worth to note: the logged occurrence of the problem resolved after some time. This should be in the logs. After two minutes it looped again and then I took the account offline. This second occurrence is not logged.

  Does this whole thing make any sense for you?

  Best,
  Henning

• 

  benny December 23rd, 2015 @ 04:32 PM

  Raw Flags is a custom column for the messages list. See “View ▸ Columns” or right-click the headers of the messages list.

  The logs make no sense to me. It kind of looks like MailMate is to blame, but I'm not 100% sure. And yet, the problem could certainly be triggered by marking something junk/not junk.

  I'm afraid I'll have to add some debug output to learn more and I don't have much the during Christmas. I'll let you know when I have something for. Let me know if you find any other clues.

• 

  benny January 26th, 2016 @ 01:10 PM

  • State changed from “new” to “fixcommitted”

  I believe this problem has been fixed in the latest test releases: Hold down ⌥ when clicking “Check Now” in the Software Update preferences pane.

  Let me know if this is not true.

• 

  benny March 15th, 2016 @ 12:14 PM

  • State changed from “fixcommitted” to “fixreleased”

  [bulk edit]