Ensure that non-QRESYNC nnimap can proceed after a QRESYNC fail
commit4616ddc1316f9e25429ab932bf87149dc578381d
authorLars Ingebrigtsen <larsi@gnus.org>
Thu, 12 Apr 2018 16:12:03 +0000 (12 18:12 +0200)
committerLars Ingebrigtsen <larsi@gnus.org>
Thu, 12 Apr 2018 16:12:03 +0000 (12 18:12 +0200)
tree448ab4e6bb8bedf2faae324509b58b1979112d10
parentd9d90def6e76e445be965760705b75f9c01b83a5
Ensure that non-QRESYNC nnimap can proceed after a QRESYNC fail

* lisp/gnus/nnimap.el (nnimap-update-info): If we don't have a
start-article in the non-QRESYNC case, then the start has to be 1
(bug#23241).
lisp/gnus/nnimap.el