···11+2017-09-22 11:14 -0700 Kevin McCarthy <kevin@8t8.us> (19c81a140c6e)
22+33+ * imap/imap.c: Add missing IMAP_CMD_POLL flag in imap buffy check.
44+55+ I missed adding the flag to one of the imap_exec() calls inside the
66+ loop, when a different server is encountered in the mailboxes list.
77+88+2017-09-22 11:12 -0700 Kevin McCarthy <kevin@8t8.us> (9e53c623d102)
99+1010+ * imap/command.c: Close the imap socket for the selected mailbox on
1111+ error.
1212+1313+ The new $imap_poll_timeout calls the cmd_handle_fatal() error
1414+ handler on timeout, which is supposed to close and cleanup.
1515+1616+ However, for the currently selected mailbox, the error handler was
1717+ not closing the socket after closing up the mailbox. This left extra
1818+ SSL/GnuTLS data around and was causing errors on an attempt to
1919+ reconnect.
2020+2121+ Thanks to Fabian Groffen for reporting the issue.
2222+2323+2017-09-22 11:07 -0700 Kevin McCarthy <kevin@8t8.us> (7155392ed28b)
2424+2525+ * imap/imap.c: Fix imap sync segfault due to inactive headers during
2626+ an expunge. (closes #3971)
2727+2828+ Mutt has several places where it turns off h->active as a hack. For
2929+ example to avoid FLAG updates, or to exclude from imap_exec_msgset.
3030+3131+ Unfortunately, when a reopen is allowed and the IMAP_EXPUNGE_PENDING
3232+ flag becomes set (e.g. a flag update to a modified header),
3333+ imap_expunge_mailbox() will be called by imap_cmd_finish().
3434+3535+ The mx_update_tables() would free and remove these "inactive"
3636+ headers, despite that an EXPUNGE was not received for them. This
3737+ would result in memory leaks and segfaults due to dangling pointers
3838+ in the msn_index and uid_hash.
3939+4040+ There should probably be a more elegant solution, removing the
4141+ initial hacks. However, this is causing a segfault, and the best
4242+ solution right now is to turn active back on for non-expunged
4343+ messages in imap_expunge_mailbox().
4444+4545+ Extra thanks to chdiza, who bravely runs tip and found this issue
4646+ quickly.
4747+4848+2017-09-14 12:43 -0700 Kevin McCarthy <kevin@8t8.us> (12d3714d8bfa)
4949+5050+ * imap/command.c, imap/message.c: Improve imap fetch handler to accept
5151+ an initial UID. (closes #3969)
5252+5353+ Gmail sends flag updates with a UID before the FLAGS. The handler
5454+ was very simple, and so ignored the flag update in that case.
5555+5656+ Pull the code from msg_parse_fetch(), paring down to just UID and
5757+ FLAGS. This will handle arbitrary order data items.
5858+5959+2017-09-13 15:48 -0700 Kevin McCarthy <kevin@8t8.us> (f90712538cd9)
6060+6161+ * imap/imap.c, imap/imap_private.h, imap/message.c: Change imap
6262+ copy/save and trash to sync flags, excluding deleted. (closes #3966)
6363+ (closes #3860)
6464+6565+ imap_copy_messages() uses a helper to sync the flags before
6666+ performing a server-side copy. However, it had a bug that the
6767+ "deleted" flag on a local message, if set, will be propagated to the
6868+ copy too.
6969+7070+ Change the copy sync helper to ignore the deleted flag. Then, change
7171+ the imap trash function to use the same helper.
7272+7373+ Thanks to Anton Lindqvist for his excellent bug report, suggested
7474+ fixes, and help testing.
7575+7676+2017-09-13 15:48 -0700 Kevin McCarthy <kevin@8t8.us> (19597bb7baa6)
7777+7878+ * imap/imap.c: Remove \Seen flag setting for imap trash. (see #3966)
7979+ (see #3860)
8080+8181+ Commit 323e3d6e5e4c has a side effect where spurious FETCH flag
8282+ updates after setting the \Seen flag can cause a sync to abort.
8383+8484+ Remove manually setting \Seen for all trashed message before
8585+ copying.
8686+8787+ The next commit will change the imap trash function to use the same
8888+ code as the imap copy/save function for syncing the message before
8989+ server-side copying.
9090+9191+2017-09-04 09:40 -0700 Kevin McCarthy <kevin@8t8.us> (3c6f3ca07807)
9292+9393+ * curs_lib.c: Fix rv assignment in mutt_window_mvprintw(). (closes
9494+ #3964)
9595+9696+ Mutt doesn't check the return value, so this wasn't causing a bug,
9797+ but was incorrect.
9898+9999+ Thanks to dcb314 for reporting the issue.
100100+101101+2017-09-04 09:20 -0700 Kevin McCarthy <kevin@8t8.us> (f2298b3e6b93)
102102+103103+ * mutt_ssl_gnutls.c: Fix fp resource leak. (closes #3965)
104104+105105+ Thanks to dcb314 for reporting the issue.
106106+107107+2017-09-02 12:20 -0700 Kevin McCarthy <kevin@8t8.us> (ed024cc919fe)
108108+109109+ * setenv.c: merge default into stable
110110+111111+2017-09-02 12:12 -0700 Kevin McCarthy <kevin@8t8.us> (a586abf3c62d)
112112+113113+ * .hgsigs: mutt-1.9.0 signed
114114+115115+2017-09-02 12:11 -0700 Kevin McCarthy <kevin@8t8.us> (b050efec0ed4)
116116+117117+ * .hgtags: Added tag mutt-1-9-rel for changeset 549821ba69e5
118118+119119+2017-09-02 11:32 -0700 Kevin McCarthy <kevin@8t8.us> (549821ba69e5)
120120+121121+ * ChangeLog, VERSION, po/bg.po, po/ca.po, po/cs.po, po/da.po,
122122+ po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/eu.po,
123123+ po/fr.po, po/ga.po, po/gl.po, po/hu.po, po/id.po, po/it.po,
124124+ po/ja.po, po/ko.po, po/lt.po, po/nl.po, po/pl.po, po/pt_BR.po,
125125+ po/ru.po, po/sk.po, po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po,
126126+ po/zh_TW.po: automatic post-release commit for mutt-1.9.0
127127+11282017-09-02 09:36 -0700 Kevin McCarthy <kevin@8t8.us> (3cd63d517453)
21293130 * po/cs.po, po/eo.po, po/nl.po: Fix the new certificate prompt