Gnus development mailing list
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <kon@iki.fi>
To: ding@gnus.org
Subject: workaround for IMAP server-side timeout during mail splitting
Date: Tue, 01 May 2018 18:50:25 +0300	[thread overview]
Message-ID: <87a7tj4bpa.fsf@Niukka.kon.iki.fi> (raw)

I had a problem where my email provider's IMAP server closed the
connection while Gnus was splitting received mail to nnml
folders, and Gnus was then unable to expunge those messages from
the server.  I worked around it by customizing the mail-sources
variable and adding various date limits to the predicate.
I hope this information will help someone else.

Background:

I use Gnus to download my email over IMAP and then read it on my
computer.  I don't normally keep any email on my email provider's
server.  Recently though, I neglected my computer for several
weeks, and the email accumulated on the server.  When I resumed
using the computer, Gnus first downloaded the email, then split
it to folders, and finally tried to expunge it from the server;
but the server had apparently timed out and closed the connection
because the splitting took so long.  I retried fetching the mail
but got the same error again.  I monitored the IMAP responses
using strace and saw that retrying the operation made Gnus fetch
the UID numbers from the IMAP server again.

Workaround:

I customized the mail-sources variable and added a date limit to
the predicate, like this:

UNSEEN UNDELETED BEFORE 22-Mar-2018

That let Gnus download a smaller number of messages at a time,
and finish splitting them before the server timed out.  I then
kept incrementing the date in the predicate until I got all the
messages and could remove the date limit.



             reply	other threads:[~2018-05-01 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 15:50 Kalle Olavi Niemitalo [this message]
2018-05-02 10:31 ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7tj4bpa.fsf@Niukka.kon.iki.fi \
    --to=kon@iki.fi \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).