1. 21 Feb, 2019 6 commits
  2. 20 Feb, 2019 11 commits
  3. 19 Feb, 2019 10 commits
  4. 17 Feb, 2019 4 commits
  5. 16 Feb, 2019 4 commits
    • Michael Gratton's avatar
      Merge branch 'wip/all-mail-sticky-conversations' into 'master' · 6a42d110
      Michael Gratton authored
      Fix sticky conversations in GMail
      See merge request !108
    • Michael Gratton's avatar
    • Michael Gratton's avatar
      Ensure conversations that have no email in the base folder are dropped · 9619d18e
      Michael Gratton authored
      If a least one email in a conversation that is in the base folder but
      also in another is removed from the base folder, the conversation may
      not be removed from the monitor despite possibly not having any email
      in the base folder, since the email may not have been completely removed
      from the conversation.
      This was particulary being seen with GMail accounts where even single
      message conversations were not disappering when trashed because the
      converation's email was still in All Mail.
      This fix does a few things: Avoids hitting the database when checking
      a conversation still has email in the base folder, when it does check
      only ensures that email are in the base folder, not *any* folder, and
      updates ConversationSet::remove_all_emails_by_identifier to do this
      check iternally, clean up its API and implementation and avoids having
      to use out args calling it.
    • Michael Gratton's avatar
      Add base_folder property back to ConversationSet · 67bf1183
      Michael Gratton authored
      Athough it was removed a while back, add it back since it is not only
      needed when adding conversations, but also when removing email from
      conversations to be able to detect when a conversation should be
  6. 15 Feb, 2019 4 commits
  7. 14 Feb, 2019 1 commit
    • Michael Gratton's avatar
      Add Email.Field.FIELDS to ImapDb.Folder.REQUIRED_FIELDS · 272d95e3
      Michael Gratton authored
      This is especially needed since when moving a message from one folder to
      another, the copy's flags are will un-flag it as deleted, so it actually
      shows up again in conversations after the MoveEmailCommit op deletes the
      original in the source folder.
      This also has the extra benefit however of makig sure the engine knows
      up-front what the uread state of all new mail is, and hence might
      actaully get unread counts correct.