1. 26 Aug, 2013 4 commits
  2. 24 Aug, 2013 1 commit
    • Jim Nelson's avatar
      Force remote folder to open after timeout · 0129af9c
      Jim Nelson authored
      A recent optimization for EmailStore was to only open a connection
      to the remote folder if a command came in requiring it.  If an
      ImapEngine.GenericFolder is opened for monitoring, however, no command
      may come in requiring a remote connection, meaning no folder
      normalization or unsolicited notifications arrive.
      
      This patch "forces" the remote to open after a timeout, which is
      cancelled if it's opened by a command.
      0129af9c
  3. 23 Aug, 2013 1 commit
  4. 22 Aug, 2013 1 commit
  5. 21 Aug, 2013 1 commit
  6. 20 Aug, 2013 6 commits
  7. 19 Aug, 2013 1 commit
    • Charles Lindsay's avatar
      Allow operations on email in any folder; fix #6496 · 5594abd9
      Charles Lindsay authored
      This is squashed commit (sorry -- we'll get better about maintaining a
      clean history in collaborative branches in the future!) of a massive
      amount of work from Jim and myself.
      
      * EmailIdentifiers for normal (i.e. not outbox, etc.) emails are the
        same regardless of which folder they came from
      * New EmailStore interface to manipulate messages that reside in any
        folder, without having to care what folders are open
      * Relevant places that manipulate emails (e.g. the toolbar) have been
        updated to use the new EmailStore interface
      * Conversation and ImplConversation have been smooshed together
      * Many, many more items and bugfixes related to the above points
      5594abd9
  8. 17 Aug, 2013 1 commit
    • Jim Nelson's avatar
      ConversationSet error when searching or archiving: Closes #7275 · 48b72968
      Jim Nelson authored
      We discovered a situation where, depending on the order email is
      processed, it's possible for logically associated emails to form
      two or more conversations.  When an email is processed that belongs
      in more than one conversation, its removal triggers this error (as
      a Message-ID can be associated with one and only one conversation).
      
      Bogus email headers, especially email that does not list a complete
      References: list, aggravate this problem.
      48b72968
  9. 14 Aug, 2013 4 commits
  10. 13 Aug, 2013 5 commits
  11. 12 Aug, 2013 4 commits
  12. 10 Aug, 2013 1 commit
  13. 09 Aug, 2013 6 commits
  14. 08 Aug, 2013 2 commits
  15. 07 Aug, 2013 2 commits