mutt stable branch with some hacks
automatic post-release commit for mutt-1.9.1
+132
-1
+127
ChangeLog
+127
ChangeLog
···
1
+
2017-09-22 11:14 -0700 Kevin McCarthy <kevin@8t8.us> (19c81a140c6e)
2
+
3
+
* imap/imap.c: Add missing IMAP_CMD_POLL flag in imap buffy check.
4
+
5
+
I missed adding the flag to one of the imap_exec() calls inside the
6
+
loop, when a different server is encountered in the mailboxes list.
7
+
8
+
2017-09-22 11:12 -0700 Kevin McCarthy <kevin@8t8.us> (9e53c623d102)
9
+
10
+
* imap/command.c: Close the imap socket for the selected mailbox on
11
+
error.
12
+
13
+
The new $imap_poll_timeout calls the cmd_handle_fatal() error
14
+
handler on timeout, which is supposed to close and cleanup.
15
+
16
+
However, for the currently selected mailbox, the error handler was
17
+
not closing the socket after closing up the mailbox. This left extra
18
+
SSL/GnuTLS data around and was causing errors on an attempt to
19
+
reconnect.
20
+
21
+
Thanks to Fabian Groffen for reporting the issue.
22
+
23
+
2017-09-22 11:07 -0700 Kevin McCarthy <kevin@8t8.us> (7155392ed28b)
24
+
25
+
* imap/imap.c: Fix imap sync segfault due to inactive headers during
26
+
an expunge. (closes #3971)
27
+
28
+
Mutt has several places where it turns off h->active as a hack. For
29
+
example to avoid FLAG updates, or to exclude from imap_exec_msgset.
30
+
31
+
Unfortunately, when a reopen is allowed and the IMAP_EXPUNGE_PENDING
32
+
flag becomes set (e.g. a flag update to a modified header),
33
+
imap_expunge_mailbox() will be called by imap_cmd_finish().
34
+
35
+
The mx_update_tables() would free and remove these "inactive"
36
+
headers, despite that an EXPUNGE was not received for them. This
37
+
would result in memory leaks and segfaults due to dangling pointers
38
+
in the msn_index and uid_hash.
39
+
40
+
There should probably be a more elegant solution, removing the
41
+
initial hacks. However, this is causing a segfault, and the best
42
+
solution right now is to turn active back on for non-expunged
43
+
messages in imap_expunge_mailbox().
44
+
45
+
Extra thanks to chdiza, who bravely runs tip and found this issue
46
+
quickly.
47
+
48
+
2017-09-14 12:43 -0700 Kevin McCarthy <kevin@8t8.us> (12d3714d8bfa)
49
+
50
+
* imap/command.c, imap/message.c: Improve imap fetch handler to accept
51
+
an initial UID. (closes #3969)
52
+
53
+
Gmail sends flag updates with a UID before the FLAGS. The handler
54
+
was very simple, and so ignored the flag update in that case.
55
+
56
+
Pull the code from msg_parse_fetch(), paring down to just UID and
57
+
FLAGS. This will handle arbitrary order data items.
58
+
59
+
2017-09-13 15:48 -0700 Kevin McCarthy <kevin@8t8.us> (f90712538cd9)
60
+
61
+
* imap/imap.c, imap/imap_private.h, imap/message.c: Change imap
62
+
copy/save and trash to sync flags, excluding deleted. (closes #3966)
63
+
(closes #3860)
64
+
65
+
imap_copy_messages() uses a helper to sync the flags before
66
+
performing a server-side copy. However, it had a bug that the
67
+
"deleted" flag on a local message, if set, will be propagated to the
68
+
copy too.
69
+
70
+
Change the copy sync helper to ignore the deleted flag. Then, change
71
+
the imap trash function to use the same helper.
72
+
73
+
Thanks to Anton Lindqvist for his excellent bug report, suggested
74
+
fixes, and help testing.
75
+
76
+
2017-09-13 15:48 -0700 Kevin McCarthy <kevin@8t8.us> (19597bb7baa6)
77
+
78
+
* imap/imap.c: Remove \Seen flag setting for imap trash. (see #3966)
79
+
(see #3860)
80
+
81
+
Commit 323e3d6e5e4c has a side effect where spurious FETCH flag
82
+
updates after setting the \Seen flag can cause a sync to abort.
83
+
84
+
Remove manually setting \Seen for all trashed message before
85
+
copying.
86
+
87
+
The next commit will change the imap trash function to use the same
88
+
code as the imap copy/save function for syncing the message before
89
+
server-side copying.
90
+
91
+
2017-09-04 09:40 -0700 Kevin McCarthy <kevin@8t8.us> (3c6f3ca07807)
92
+
93
+
* curs_lib.c: Fix rv assignment in mutt_window_mvprintw(). (closes
94
+
#3964)
95
+
96
+
Mutt doesn't check the return value, so this wasn't causing a bug,
97
+
but was incorrect.
98
+
99
+
Thanks to dcb314 for reporting the issue.
100
+
101
+
2017-09-04 09:20 -0700 Kevin McCarthy <kevin@8t8.us> (f2298b3e6b93)
102
+
103
+
* mutt_ssl_gnutls.c: Fix fp resource leak. (closes #3965)
104
+
105
+
Thanks to dcb314 for reporting the issue.
106
+
107
+
2017-09-02 12:20 -0700 Kevin McCarthy <kevin@8t8.us> (ed024cc919fe)
108
+
109
+
* setenv.c: merge default into stable
110
+
111
+
2017-09-02 12:12 -0700 Kevin McCarthy <kevin@8t8.us> (a586abf3c62d)
112
+
113
+
* .hgsigs: mutt-1.9.0 signed
114
+
115
+
2017-09-02 12:11 -0700 Kevin McCarthy <kevin@8t8.us> (b050efec0ed4)
116
+
117
+
* .hgtags: Added tag mutt-1-9-rel for changeset 549821ba69e5
118
+
119
+
2017-09-02 11:32 -0700 Kevin McCarthy <kevin@8t8.us> (549821ba69e5)
120
+
121
+
* ChangeLog, VERSION, po/bg.po, po/ca.po, po/cs.po, po/da.po,
122
+
po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/eu.po,
123
+
po/fr.po, po/ga.po, po/gl.po, po/hu.po, po/id.po, po/it.po,
124
+
po/ja.po, po/ko.po, po/lt.po, po/nl.po, po/pl.po, po/pt_BR.po,
125
+
po/ru.po, po/sk.po, po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po,
126
+
po/zh_TW.po: automatic post-release commit for mutt-1.9.0
127
+
1
128
2017-09-02 09:36 -0700 Kevin McCarthy <kevin@8t8.us> (3cd63d517453)
2
129
3
130
* po/cs.po, po/eo.po, po/nl.po: Fix the new certificate prompt
+4
UPDATING
+4
UPDATING