2002-06-19 07:22:21 +02:00
|
|
|
# IMAP folder support
|
2016-06-29 03:42:57 +02:00
|
|
|
# Copyright (C) 2002-2016 John Goerzen & contributors.
|
2002-06-19 07:22:21 +02:00
|
|
|
#
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
|
|
# it under the terms of the GNU General Public License as published by
|
2003-04-16 21:23:45 +02:00
|
|
|
# the Free Software Foundation; either version 2 of the License, or
|
|
|
|
# (at your option) any later version.
|
2002-06-19 07:22:21 +02:00
|
|
|
#
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
# GNU General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program; if not, write to the Free Software
|
2006-08-12 06:15:55 +02:00
|
|
|
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
2002-06-19 07:22:21 +02:00
|
|
|
|
2010-12-22 12:35:41 +01:00
|
|
|
import random
|
|
|
|
import binascii
|
|
|
|
import re
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
import os
|
2011-01-05 19:31:08 +01:00
|
|
|
import time
|
2016-06-04 00:49:57 +02:00
|
|
|
import six
|
2011-09-06 13:19:26 +02:00
|
|
|
from sys import exc_info
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2012-02-05 12:52:12 +01:00
|
|
|
from .Base import BaseFolder
|
2013-01-17 14:21:21 +01:00
|
|
|
from offlineimap import imaputil, imaplibutil, emailutil, OfflineImapError
|
2013-01-28 20:08:20 +01:00
|
|
|
from offlineimap import globals
|
2016-06-04 00:49:57 +02:00
|
|
|
from offlineimap.virtual_imaplib2 import MonthNames
|
2016-05-17 19:56:52 +02:00
|
|
|
|
2002-07-18 02:51:03 +02:00
|
|
|
|
2012-10-16 20:53:54 +02:00
|
|
|
# Globals
|
|
|
|
CRLF = '\r\n'
|
2016-05-18 02:42:09 +02:00
|
|
|
MSGCOPY_NAMESPACE = 'MSGCOPY_'
|
2012-10-16 20:53:54 +02:00
|
|
|
|
|
|
|
|
2012-10-17 21:45:19 +02:00
|
|
|
# NB: message returned from getmessage() will have '\n' all over the place,
|
|
|
|
# NB: there will be no CRLFs. Just before the sending stage of savemessage()
|
|
|
|
# NB: '\n' will be transformed back to CRLF. So, for the most parts of the
|
|
|
|
# NB: code the stored content will be clean of CRLF and one can rely that
|
|
|
|
# NB: line endings will be pure '\n'.
|
|
|
|
|
|
|
|
|
2002-06-19 07:22:21 +02:00
|
|
|
class IMAPFolder(BaseFolder):
|
2011-09-16 10:54:26 +02:00
|
|
|
def __init__(self, imapserver, name, repository):
|
2015-01-11 13:54:53 +01:00
|
|
|
# FIXME: decide if unquoted name is from the responsability of the
|
|
|
|
# caller or not, but not both.
|
2011-09-16 10:54:22 +02:00
|
|
|
name = imaputil.dequote(name)
|
2011-09-30 17:20:11 +02:00
|
|
|
self.sep = imapserver.delim
|
2011-09-16 10:54:22 +02:00
|
|
|
super(IMAPFolder, self).__init__(name, repository)
|
2003-04-18 04:18:34 +02:00
|
|
|
self.expunge = repository.getexpunge()
|
2002-07-20 09:03:21 +02:00
|
|
|
self.root = None # imapserver.root
|
2002-06-19 07:22:21 +02:00
|
|
|
self.imapserver = imapserver
|
2003-04-18 04:18:34 +02:00
|
|
|
self.randomgenerator = random.Random()
|
2016-06-28 18:46:57 +02:00
|
|
|
# self.ui is set in BaseFolder.
|
2012-10-17 21:45:19 +02:00
|
|
|
self.imap_query = ['BODY.PEEK[]']
|
2002-06-21 08:51:21 +02:00
|
|
|
|
2012-10-16 20:53:54 +02:00
|
|
|
fh_conf = self.repository.account.getconf('filterheaders', '')
|
|
|
|
self.filterheaders = [h for h in re.split(r'\s*,\s*', fh_conf) if h]
|
|
|
|
|
2016-06-28 23:58:03 +02:00
|
|
|
# self.copy_ignoreUIDs is used by BaseFolder.
|
|
|
|
self.copy_ignoreUIDs = repository.get_copy_ignore_UIDs(
|
|
|
|
self.getvisiblename())
|
|
|
|
|
2012-10-16 20:53:54 +02:00
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
def __selectro(self, imapobj, force=False):
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
"""Select this folder when we do not need write access.
|
2011-05-07 18:39:13 +02:00
|
|
|
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
Prefer SELECT to EXAMINE if we can, since some servers
|
|
|
|
(Courier) do not stabilize UID validity until the folder is
|
2013-07-21 21:00:23 +02:00
|
|
|
selected.
|
2011-05-07 18:39:13 +02:00
|
|
|
.. todo: Still valid? Needs verification
|
2012-01-08 11:29:54 +01:00
|
|
|
:param: Enforce new SELECT even if we are on that folder already.
|
2011-05-07 18:39:13 +02:00
|
|
|
:returns: raises :exc:`OfflineImapError` severity FOLDER on error"""
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
try:
|
2012-01-08 11:29:54 +01:00
|
|
|
imapobj.select(self.getfullname(), force = force)
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
except imapobj.readonly:
|
2012-01-08 11:29:54 +01:00
|
|
|
imapobj.select(self.getfullname(), readonly = True, force = force)
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-07-04 03:35:05 +02:00
|
|
|
def suggeststhreads(self):
|
2013-01-28 20:08:20 +01:00
|
|
|
return not globals.options.singlethreading
|
2002-07-04 03:35:05 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-07-04 03:35:05 +02:00
|
|
|
def waitforthread(self):
|
|
|
|
self.imapserver.connectionwait()
|
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
def getmaxage(self):
|
|
|
|
if self.config.getdefault("Account %s"%
|
|
|
|
self.accountname, "maxage", None):
|
2016-06-29 03:42:57 +02:00
|
|
|
six.reraise(OfflineImapError,
|
|
|
|
OfflineImapError(
|
|
|
|
"maxage is not supported on IMAP-IMAP sync",
|
|
|
|
OfflineImapError.ERROR.REPO),
|
|
|
|
exc_info()[2])
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2016-05-18 02:42:09 +02:00
|
|
|
def getinstancelimitnamespace(self):
|
|
|
|
return MSGCOPY_NAMESPACE + self.repository.getname()
|
2002-07-04 05:59:19 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2012-01-19 11:24:16 +01:00
|
|
|
def get_uidvalidity(self):
|
|
|
|
"""Retrieve the current connections UIDVALIDITY value
|
|
|
|
|
|
|
|
UIDVALIDITY value will be cached on the first call.
|
|
|
|
:returns: The UIDVALIDITY as (long) number."""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2012-01-19 11:24:16 +01:00
|
|
|
if hasattr(self, '_uidvalidity'):
|
2016-06-28 18:46:57 +02:00
|
|
|
# Use cached value if existing.
|
2012-01-19 11:24:16 +01:00
|
|
|
return self._uidvalidity
|
2002-07-04 03:35:05 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
|
|
|
try:
|
2016-06-28 18:46:57 +02:00
|
|
|
# SELECT (if not already done) and get current UIDVALIDITY.
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__selectro(imapobj)
|
2012-01-19 11:24:16 +01:00
|
|
|
typ, uidval = imapobj.response('UIDVALIDITY')
|
|
|
|
assert uidval != [None] and uidval != None, \
|
|
|
|
"response('UIDVALIDITY') returned [None]!"
|
2016-05-08 16:42:52 +02:00
|
|
|
self._uidvalidity = int(uidval[-1])
|
2012-01-19 11:24:16 +01:00
|
|
|
return self._uidvalidity
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2011-04-11 18:33:11 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
def quickchanged(self, statusfolder):
|
|
|
|
# An IMAP folder has definitely changed if the number of
|
|
|
|
# messages or the UID of the last message have changed. Otherwise
|
|
|
|
# only flag changes could have occurred.
|
2011-09-12 10:26:42 +02:00
|
|
|
retry = True # Should we attempt another round or exit?
|
|
|
|
while retry:
|
|
|
|
retry = False
|
|
|
|
imapobj = self.imapserver.acquireconnection()
|
|
|
|
try:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Select folder and get number of messages.
|
2011-09-12 10:26:42 +02:00
|
|
|
restype, imapdata = imapobj.select(self.getfullname(), True,
|
|
|
|
True)
|
2012-04-21 13:26:09 +02:00
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2012-02-05 10:14:23 +01:00
|
|
|
except OfflineImapError as e:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Retry on dropped connections, raise otherwise.
|
2011-09-12 10:26:43 +02:00
|
|
|
self.imapserver.releaseconnection(imapobj, True)
|
2011-09-12 10:26:42 +02:00
|
|
|
if e.severity == OfflineImapError.ERROR.FOLDER_RETRY:
|
|
|
|
retry = True
|
2016-07-28 06:51:47 +02:00
|
|
|
else:
|
|
|
|
raise
|
2012-04-21 13:26:09 +02:00
|
|
|
except:
|
2016-07-28 06:51:47 +02:00
|
|
|
# Cleanup and raise on all other errors.
|
2012-04-21 13:26:09 +02:00
|
|
|
self.imapserver.releaseconnection(imapobj, True)
|
|
|
|
raise
|
2011-09-12 10:26:42 +02:00
|
|
|
# 1. Some mail servers do not return an EXISTS response
|
|
|
|
# if the folder is empty. 2. ZIMBRA servers can return
|
|
|
|
# multiple EXISTS replies in the form 500, 1000, 1500,
|
|
|
|
# 1623 so check for potentially multiple replies.
|
|
|
|
if imapdata == [None]:
|
|
|
|
return True
|
|
|
|
maxmsgid = 0
|
|
|
|
for msgid in imapdata:
|
2016-05-08 16:42:52 +02:00
|
|
|
maxmsgid = max(int(msgid), maxmsgid)
|
2011-09-12 10:26:42 +02:00
|
|
|
# Different number of messages than last time?
|
|
|
|
if maxmsgid != statusfolder.getmessagecount():
|
2013-07-21 21:00:23 +02:00
|
|
|
return True
|
2011-09-12 10:26:43 +02:00
|
|
|
return False
|
Daniel Jacobowitz patches
fixes deb#433732
Date: Sun, 30 Sep 2007 13:54:56 -0400
From: Daniel Jacobowitz <drow@false.org>
To: offlineimap@complete.org
Subject: Assorted patches
Here's the result of a lazy Sunday hacking on offlineimap. Sorry for
not breaking this into multiple patches. They're mostly logically
independent so just ask if that would make a difference.
First, a new -q (quick) option. The quick option means to only update
folders that seem to have had significant changes. For Maildir, any
change to any message UID or flags is significant, because checking
the flags doesn't add a significant cost. For IMAP, only a change to
the total number of messages or a change in the UID of the most recent
message is significant. This should catch everything except for
flags changes.
The difference in bandwidth is astonishing: a quick sync takes 80K
instead of 5.3MB, and 28 seconds instead of 90.
There's a configuration variable that lets you say every tenth sync
should update flags, but let all the intervening ones be lighter.
Second, a fix to the UID validity problems many people have been
reporting with Courier. As discussed in Debian bug #433732, I changed
the UID validity check to use SELECT unless the server complains that
the folder is read-only. This avoids the Courier bug (see the Debian
log for more details). This won't fix existing validity errors, you
need to remove the local status and validity files by hand and resync.
Third, some speedups in Maildir checking. It's still pretty slow
due to a combination of poor performance in os.listdir (never reads
more than 4K of directory entries at a time) and some semaphore that
leads to lots of futex wake operations, but at least this saves
20% or so of the CPU time running offlineimap on a single folder:
Time with quick refresh and md5 in loop: 4.75s user 0.46s system 12%
cpu 41.751 total
Time with quick refresh and md5 out of loop: 4.38s user 0.50s system
14% cpu 34.799 total
Time using string compare to check folder: 4.11s user 0.47s system 13%
cpu 34.788 total
And fourth, some display fixes for Curses.Blinkenlights. I made
warnings more visible, made the new quick sync message cyan, and
made all not explicitly colored messages grey. That last one was
really bugging me. Any time OfflineIMAP printed a warning in
this UI, it had even odds of coming out black on black!
Anyway, I hope these are useful. I'm happy to revise them if you see
a problem.
--
Daniel Jacobowitz
CodeSourcery
2007-10-01 23:20:37 +02:00
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
def _msgs_to_fetch(self, imapobj, min_date=None, min_uid=None):
|
2015-01-08 17:13:33 +01:00
|
|
|
"""Determines sequence numbers of messages to be fetched.
|
2012-10-16 20:20:35 +02:00
|
|
|
|
|
|
|
Message sequence numbers (MSNs) are more easily compacted
|
|
|
|
into ranges which makes transactions slightly faster.
|
2012-10-17 21:45:19 +02:00
|
|
|
|
|
|
|
Arguments:
|
|
|
|
- imapobj: instance of IMAPlib
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
- min_date (optional): a time_struct; only fetch messages newer than this
|
|
|
|
- min_uid (optional): only fetch messages with UID >= min_uid
|
|
|
|
|
|
|
|
This function should be called with at MOST one of min_date OR
|
|
|
|
min_uid set but not BOTH.
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2012-10-16 20:20:35 +02:00
|
|
|
Returns: range(s) for messages or None if no messages
|
2015-01-08 17:13:33 +01:00
|
|
|
are to be fetched."""
|
2012-10-17 21:45:19 +02:00
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
def search(search_conditions):
|
|
|
|
"""Actually request the server with the specified conditions.
|
2012-10-17 21:45:19 +02:00
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
Returns: range(s) for messages or None if no messages
|
|
|
|
are to be fetched."""
|
|
|
|
res_type, res_data = imapobj.search(None, search_conditions)
|
2012-10-17 21:45:19 +02:00
|
|
|
if res_type != 'OK':
|
|
|
|
raise OfflineImapError("SEARCH in folder [%s]%s failed. "
|
2015-01-08 17:13:33 +01:00
|
|
|
"Search string was '%s'. Server responded '[%s] %s'"% (
|
2012-10-17 21:45:19 +02:00
|
|
|
self.getrepository(), self, search_cond, res_type, res_data),
|
|
|
|
OfflineImapError.ERROR.FOLDER)
|
Handle maxage for davmail correctly
"imapobj.search" returns a list with one string element of numbers
separated by one whitespace character for regular box (GMail, AOL...).
['1 2 3 4 5 6 7 8 9 10 11 12']
But if we would like to sync from Davmail it would return a list of
numbers.
['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'].
The code "return res_data[0].split()" in the first case will return what
we already have when using Davmail, hence only one email will be
fetched. But if only the first sync would be with maxage the emails
will be removed, because offlineimap will think that they were removed
by us.
The patch distinguishes between syncing with Davmail and regular box and
applies split on the first element only when it finds whitespace
character. It also handles the case when the first element is empty on
first sync.
Closes #327
Signed-off-by: Łukasz Żarnowiecki <dolohow@outlook.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2016-05-07 12:32:10 +02:00
|
|
|
# Davmail returns list instead of list of one element string.
|
|
|
|
# On first run the first element is empty.
|
|
|
|
if ' ' in res_data[0] or res_data[0] == '':
|
|
|
|
res_data = res_data[0].split()
|
2016-05-25 03:29:03 +02:00
|
|
|
# Some servers are broken.
|
|
|
|
if 0 in res_data:
|
|
|
|
self.ui.warn("server returned UID with 0; ignoring.")
|
|
|
|
res_data.remove(0)
|
Handle maxage for davmail correctly
"imapobj.search" returns a list with one string element of numbers
separated by one whitespace character for regular box (GMail, AOL...).
['1 2 3 4 5 6 7 8 9 10 11 12']
But if we would like to sync from Davmail it would return a list of
numbers.
['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'].
The code "return res_data[0].split()" in the first case will return what
we already have when using Davmail, hence only one email will be
fetched. But if only the first sync would be with maxage the emails
will be removed, because offlineimap will think that they were removed
by us.
The patch distinguishes between syncing with Davmail and regular box and
applies split on the first element only when it finds whitespace
character. It also handles the case when the first element is empty on
first sync.
Closes #327
Signed-off-by: Łukasz Żarnowiecki <dolohow@outlook.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2016-05-07 12:32:10 +02:00
|
|
|
return res_data
|
2012-10-17 21:45:19 +02:00
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
res_type, imapdata = imapobj.select(self.getfullname(), True, True)
|
|
|
|
if imapdata == [None] or imapdata[0] == '0':
|
|
|
|
# Empty folder, no need to populate message list.
|
|
|
|
return None
|
2012-10-17 21:45:19 +02:00
|
|
|
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
conditions = []
|
|
|
|
# 1. min_uid condition.
|
|
|
|
if min_uid != None:
|
|
|
|
conditions.append("UID %d:*"% min_uid)
|
|
|
|
# 2. date condition.
|
|
|
|
elif min_date != None:
|
|
|
|
# Find out what the oldest message is that we should look at.
|
|
|
|
conditions.append("SINCE %02d-%s-%d"% (
|
|
|
|
min_date[2], MonthNames[min_date[1]], min_date[0]))
|
|
|
|
# 3. maxsize condition.
|
|
|
|
maxsize = self.getmaxsize()
|
|
|
|
if maxsize != None:
|
|
|
|
conditions.append("SMALLER %d"% maxsize)
|
|
|
|
|
|
|
|
if len(conditions) >= 1:
|
|
|
|
# Build SEARCH command.
|
|
|
|
search_cond = "(%s)"% ' '.join(conditions)
|
|
|
|
search_result = search(search_cond)
|
|
|
|
return imaputil.uid_sequence(search_result)
|
|
|
|
|
|
|
|
# By default consider all messages in this folder.
|
|
|
|
return '1:*'
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2014-08-03 14:47:26 +02:00
|
|
|
# Interface from BaseFolder
|
|
|
|
def msglist_item_initializer(self, uid):
|
|
|
|
return {'uid': uid, 'flags': set(), 'time': 0}
|
|
|
|
|
2012-10-17 21:45:19 +02:00
|
|
|
|
|
|
|
# Interface from BaseFolder
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
def cachemessagelist(self, min_date=None, min_uid=None):
|
|
|
|
self.ui.loadmessagelist(self.repository, self)
|
2016-04-09 18:12:18 +02:00
|
|
|
self.dropmessagelistcache()
|
2002-07-11 05:31:39 +02:00
|
|
|
|
2011-08-18 09:08:54 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
2002-07-04 03:35:05 +02:00
|
|
|
try:
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
msgsToFetch = self._msgs_to_fetch(
|
|
|
|
imapobj, min_date=min_date, min_uid=min_uid)
|
2012-10-17 21:45:19 +02:00
|
|
|
if not msgsToFetch:
|
2016-05-25 03:29:03 +02:00
|
|
|
return # No messages to sync.
|
2011-08-18 09:08:54 +02:00
|
|
|
|
2011-08-18 09:08:55 +02:00
|
|
|
# Get the flags and UIDs for these. single-quotes prevent
|
|
|
|
# imaplib2 from quoting the sequence.
|
2015-01-08 17:13:33 +01:00
|
|
|
res_type, response = imapobj.fetch("'%s'"%
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
msgsToFetch, '(FLAGS UID INTERNALDATE)')
|
2011-08-18 09:08:56 +02:00
|
|
|
if res_type != 'OK':
|
|
|
|
raise OfflineImapError("FETCHING UIDs in folder [%s]%s failed. "
|
2015-01-14 22:58:25 +01:00
|
|
|
"Server responded '[%s] %s'"% (self.getrepository(), self,
|
|
|
|
res_type, response), OfflineImapError.ERROR.FOLDER)
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2011-08-18 09:08:55 +02:00
|
|
|
|
2002-06-20 08:26:28 +02:00
|
|
|
for messagestr in response:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Looks like: '1 (FLAGS (\\Seen Old) UID 4807)' or None if no msg.
|
2011-08-16 12:16:46 +02:00
|
|
|
# Discard initial message number.
|
2011-09-05 14:03:09 +02:00
|
|
|
if messagestr == None:
|
|
|
|
continue
|
2011-01-31 15:50:18 +01:00
|
|
|
messagestr = messagestr.split(' ', 1)[1]
|
2002-06-20 08:26:28 +02:00
|
|
|
options = imaputil.flags2hash(messagestr)
|
2012-02-05 13:40:06 +01:00
|
|
|
if not 'UID' in options:
|
2016-06-28 18:46:57 +02:00
|
|
|
self.ui.warn('No UID in message with options %s'%
|
|
|
|
str(options), minor=1)
|
2002-10-30 05:26:49 +01:00
|
|
|
else:
|
2016-05-08 16:42:52 +02:00
|
|
|
uid = int(options['UID'])
|
2014-08-03 14:47:26 +02:00
|
|
|
self.messagelist[uid] = self.msglist_item_initializer(uid)
|
2002-10-30 05:26:49 +01:00
|
|
|
flags = imaputil.flagsimap2maildir(options['FLAGS'])
|
2015-11-20 20:09:10 +01:00
|
|
|
keywords = imaputil.flagsimap2keywords(options['FLAGS'])
|
2007-07-04 19:51:57 +02:00
|
|
|
rtime = imaplibutil.Internaldate2epoch(messagestr)
|
2015-11-20 20:09:10 +01:00
|
|
|
self.messagelist[uid] = {'uid': uid, 'flags': flags, 'time': rtime,
|
|
|
|
'keywords': keywords}
|
maxage: fix timezone issues, remove IMAP-IMAP support, add startdate option
1. When using maxage, local and remote messagelists are supposed to only
contain messages from at most maxage days ago. But local and remote used
different timezones to calculate what "maxage days ago" means, resulting
in removals on one side. Now, we ask the local folder for maxage days'
worth of mail, find the lowest UID, and then ask the remote folder for
all UID's starting with that lowest one.
2. maxage was fundamentally wrong in the IMAP-IMAP case: it assumed that
remote messages have UIDs in the same order as their local counterparts,
which could be false, e.g. when messages are copied in quick succession.
So, remove support for maxage in the IMAP-IMAP case.
3. Add startdate option for IMAP-IMAP syncs: use messages from the given
repository starting at startdate, and all messages from the other
repository. In the first sync, the other repository must be empty.
4. Allow maxage to be specified either as number of days to sync (as
previously) or as a fixed date.
Signed-off-by: Janna Martl <janna.martl109@gmail.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2015-04-07 10:14:11 +02:00
|
|
|
self.ui.messagelistloaded(self.repository, self, self.getmessagecount())
|
2002-06-20 09:40:29 +02:00
|
|
|
|
2015-08-29 14:53:20 +02:00
|
|
|
# Interface from BaseFolder
|
|
|
|
def getvisiblename(self):
|
|
|
|
vname = super(IMAPFolder, self).getvisiblename()
|
|
|
|
if self.repository.getdecodefoldernames():
|
|
|
|
return imaputil.decode_mailbox_name(vname)
|
|
|
|
return vname
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-06-20 13:39:27 +02:00
|
|
|
def getmessage(self, uid):
|
2015-01-14 22:58:25 +01:00
|
|
|
"""Retrieve message with UID from the IMAP server (incl body).
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2015-03-27 12:38:16 +01:00
|
|
|
After this function all CRLFs will be transformed to '\n'.
|
2011-04-26 15:18:54 +02:00
|
|
|
|
2011-06-15 10:59:00 +02:00
|
|
|
:returns: the message body or throws and OfflineImapError
|
|
|
|
(probably severity MESSAGE) if e.g. no message with
|
|
|
|
this UID could be found.
|
2011-04-26 15:18:54 +02:00
|
|
|
"""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2015-11-25 07:39:56 +01:00
|
|
|
data = self._fetch_from_imap(str(uid), 2)
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Data looks now e.g.
|
|
|
|
# [('320 (UID 17061 BODY[] {2565}','msgbody....')]
|
|
|
|
# We only asked for one message, and that msg is in data[0]. msbody is
|
|
|
|
# in [0][1].
|
2012-10-17 21:45:19 +02:00
|
|
|
data = data[0][1].replace(CRLF, "\n")
|
|
|
|
|
2016-06-28 19:15:07 +02:00
|
|
|
if len(data) > 200:
|
2015-01-14 22:58:25 +01:00
|
|
|
dbg_output = "%s...%s"% (str(data)[:150], str(data)[-50:])
|
2012-10-17 21:45:19 +02:00
|
|
|
else:
|
|
|
|
dbg_output = data
|
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
self.ui.debug('imap', "Returned object from fetching %d: '%s'"%
|
2012-10-17 21:45:19 +02:00
|
|
|
(uid, dbg_output))
|
|
|
|
|
2011-05-08 22:46:08 +02:00
|
|
|
return data
|
2006-08-22 03:09:36 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2006-08-22 03:09:36 +02:00
|
|
|
def getmessagetime(self, uid):
|
|
|
|
return self.messagelist[uid]['time']
|
2011-04-11 18:33:11 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-06-20 13:39:27 +02:00
|
|
|
def getmessageflags(self, uid):
|
2002-07-04 03:35:05 +02:00
|
|
|
return self.messagelist[uid]['flags']
|
2003-04-18 04:18:34 +02:00
|
|
|
|
2015-11-20 20:09:10 +01:00
|
|
|
# Interface from BaseFolder
|
|
|
|
def getmessagekeywords(self, uid):
|
|
|
|
return self.messagelist[uid]['keywords']
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __generate_randomheader(self, content):
|
2011-03-04 17:34:20 +01:00
|
|
|
"""Returns a unique X-OfflineIMAP header
|
|
|
|
|
|
|
|
Generate an 'X-OfflineIMAP' mail header which contains a random
|
|
|
|
unique value (which is based on the mail content, and a random
|
|
|
|
number). This header allows us to fetch a mail after APPENDing
|
|
|
|
it to an IMAP server and thus find out the UID that the server
|
|
|
|
assigned it.
|
|
|
|
|
|
|
|
:returns: (headername, headervalue) tuple, consisting of strings
|
|
|
|
headername == 'X-OfflineIMAP' and headervalue will be a
|
|
|
|
random string
|
|
|
|
"""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2010-10-07 12:33:27 +02:00
|
|
|
headername = 'X-OfflineIMAP'
|
2011-03-04 17:34:20 +01:00
|
|
|
# We need a random component too. If we ever upload the same
|
|
|
|
# mail twice (e.g. in different folders), we would still need to
|
|
|
|
# get the UID for the correct one. As we won't have too many
|
|
|
|
# mails with identical content, the randomness requirements are
|
|
|
|
# not extremly critial though.
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Compute unsigned crc32 of 'content' as unique hash.
|
|
|
|
# NB: crc32 returns unsigned only starting with python 3.0.
|
2011-03-04 17:34:20 +01:00
|
|
|
headervalue = str( binascii.crc32(content) & 0xffffffff ) + '-'
|
|
|
|
headervalue += str(self.randomgenerator.randint(0,9999999999))
|
2003-04-18 04:18:34 +02:00
|
|
|
return (headername, headervalue)
|
|
|
|
|
2011-03-04 17:34:22 +01:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __savemessage_searchforheader(self, imapobj, headername, headervalue):
|
2016-07-28 06:51:47 +02:00
|
|
|
self.ui.debug('imap', '__savemessage_searchforheader called for %s: %s'%
|
2015-01-08 17:13:33 +01:00
|
|
|
(headername, headervalue))
|
2003-04-18 04:18:34 +02:00
|
|
|
# Now find the UID it got.
|
|
|
|
headervalue = imapobj._quote(headervalue)
|
|
|
|
try:
|
2015-01-14 22:58:25 +01:00
|
|
|
matchinguids = imapobj.uid('search', 'HEADER',
|
|
|
|
headername, headervalue)[1][0]
|
2012-02-05 10:14:23 +01:00
|
|
|
except imapobj.error as err:
|
2003-04-18 04:18:34 +02:00
|
|
|
# IMAP server doesn't implement search or had a problem.
|
2016-07-28 06:51:47 +02:00
|
|
|
self.ui.debug('imap', "__savemessage_searchforheader: got IMAP "
|
|
|
|
"error '%s' while attempting to UID SEARCH for message with "
|
|
|
|
"header %s"% (err, headername))
|
2006-05-16 04:34:46 +02:00
|
|
|
return 0
|
2016-07-28 06:51:47 +02:00
|
|
|
self.ui.debug('imap', "__savemessage_searchforheader got initial "
|
|
|
|
"matchinguids: " + repr(matchinguids))
|
2006-05-15 04:51:12 +02:00
|
|
|
|
|
|
|
if matchinguids == '':
|
2016-07-28 06:51:47 +02:00
|
|
|
self.ui.debug('imap', "__savemessage_searchforheader: UID SEARCH "
|
|
|
|
"for message with header %s yielded no results"% headername)
|
2006-05-16 04:34:46 +02:00
|
|
|
return 0
|
2006-05-15 04:51:12 +02:00
|
|
|
|
2003-04-18 04:18:34 +02:00
|
|
|
matchinguids = matchinguids.split(' ')
|
2016-07-28 06:51:47 +02:00
|
|
|
self.ui.debug('imap', '__savemessage_searchforheader: matchinguids now '
|
|
|
|
+ repr(matchinguids))
|
|
|
|
if len(matchinguids) != 1 or matchinguids[0] is None:
|
2012-02-05 11:51:02 +01:00
|
|
|
raise ValueError("While attempting to find UID for message with "
|
2016-07-28 06:51:47 +02:00
|
|
|
"header %s, got wrong-sized matchinguids of %s"%
|
2012-02-05 11:51:02 +01:00
|
|
|
(headername, str(matchinguids)))
|
2016-05-08 16:42:52 +02:00
|
|
|
return int(matchinguids[0])
|
2003-04-18 04:18:34 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __savemessage_fetchheaders(self, imapobj, headername, headervalue):
|
2011-08-16 10:55:14 +02:00
|
|
|
""" We fetch all new mail headers and search for the right
|
|
|
|
X-OfflineImap line by hand. The response from the server has form:
|
|
|
|
(
|
|
|
|
'OK',
|
|
|
|
[
|
|
|
|
(
|
|
|
|
'185 (RFC822.HEADER {1789}',
|
|
|
|
'... mail headers ...'
|
|
|
|
),
|
|
|
|
' UID 2444)',
|
|
|
|
(
|
|
|
|
'186 (RFC822.HEADER {1789}',
|
|
|
|
'... 2nd mail headers ...'
|
|
|
|
),
|
|
|
|
' UID 2445)'
|
|
|
|
]
|
|
|
|
)
|
|
|
|
We need to locate the UID just after mail headers containing our
|
|
|
|
X-OfflineIMAP line.
|
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
Returns UID when found, 0 when not found."""
|
|
|
|
|
|
|
|
self.ui.debug('imap', '__savemessage_fetchheaders called for %s: %s'% \
|
2011-08-16 10:55:14 +02:00
|
|
|
(headername, headervalue))
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Run "fetch X:* rfc822.header".
|
|
|
|
# Since we stored the mail we are looking for just recently, it would
|
2011-08-16 10:55:14 +02:00
|
|
|
# not be optimal to fetch all messages. So we'll find highest message
|
|
|
|
# UID in our local messagelist and search from there (exactly from
|
|
|
|
# UID+1). That works because UIDs are guaranteed to be unique and
|
|
|
|
# ascending.
|
|
|
|
|
|
|
|
if self.getmessagelist():
|
2015-01-08 17:13:33 +01:00
|
|
|
start = 1 + max(self.getmessagelist().keys())
|
2011-08-16 10:55:14 +02:00
|
|
|
else:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Folder was empty - start from 1.
|
2011-08-16 10:55:14 +02:00
|
|
|
start = 1
|
|
|
|
|
|
|
|
# Imaplib quotes all parameters of a string type. That must not happen
|
|
|
|
# with the range X:*. So we use bytearray to stop imaplib from getting
|
2016-06-28 18:46:57 +02:00
|
|
|
# in our way.
|
2011-08-16 10:55:14 +02:00
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
result = imapobj.uid('FETCH', bytearray('%d:*'% start), 'rfc822.header')
|
2011-08-16 10:55:14 +02:00
|
|
|
if result[0] != 'OK':
|
2015-01-14 22:58:25 +01:00
|
|
|
raise OfflineImapError('Error fetching mail headers: %s'%
|
|
|
|
'. '.join(result[1]), OfflineImapError.ERROR.MESSAGE)
|
2011-08-16 10:55:14 +02:00
|
|
|
|
|
|
|
result = result[1]
|
|
|
|
|
|
|
|
found = 0
|
|
|
|
for item in result:
|
|
|
|
if found == 0 and type(item) == type( () ):
|
2016-06-28 18:46:57 +02:00
|
|
|
# Walk just tuples.
|
2015-01-08 17:13:33 +01:00
|
|
|
if re.search("(?:^|\\r|\\n)%s:\s*%s(?:\\r|\\n)"% (headername, headervalue),
|
2011-08-16 10:55:14 +02:00
|
|
|
item[1], flags=re.IGNORECASE):
|
|
|
|
found = 1
|
|
|
|
elif found == 1:
|
|
|
|
if type(item) == type (""):
|
|
|
|
uid = re.search("UID\s+(\d+)", item, flags=re.IGNORECASE)
|
|
|
|
if uid:
|
|
|
|
return int(uid.group(1))
|
|
|
|
else:
|
|
|
|
self.ui.warn("Can't parse FETCH response, can't find UID: %s", result.__repr__())
|
|
|
|
else:
|
|
|
|
self.ui.warn("Can't parse FETCH response, we awaited string: %s", result.__repr__())
|
|
|
|
|
|
|
|
return 0
|
2011-03-04 17:34:21 +01:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __getmessageinternaldate(self, content, rtime=None):
|
2011-03-04 17:34:21 +01:00
|
|
|
"""Parses mail and returns an INTERNALDATE string
|
|
|
|
|
2015-01-14 22:58:25 +01:00
|
|
|
It will use information in the following order, falling back as an
|
|
|
|
attempt fails:
|
2011-03-04 17:34:21 +01:00
|
|
|
- rtime parameter
|
|
|
|
- Date header of email
|
|
|
|
|
|
|
|
We return None, if we couldn't find a valid date. In this case
|
|
|
|
the IMAP server will use the server local time when appening
|
|
|
|
(per RFC).
|
|
|
|
|
|
|
|
Note, that imaplib's Time2Internaldate is inherently broken as
|
|
|
|
it returns localized date strings which are invalid for IMAP
|
|
|
|
servers. However, that function is called for *every* append()
|
|
|
|
internally. So we need to either pass in `None` or the correct
|
|
|
|
string (in which case Time2Internaldate() will do nothing) to
|
|
|
|
append(). The output of this function is designed to work as
|
|
|
|
input to the imapobj.append() function.
|
|
|
|
|
|
|
|
TODO: We should probably be returning a bytearray rather than a
|
|
|
|
string here, because the IMAP server will expect plain
|
|
|
|
ASCII. However, imaplib.Time2INternaldate currently returns a
|
|
|
|
string so we go with the same for now.
|
|
|
|
|
|
|
|
:param rtime: epoch timestamp to be used rather than analyzing
|
|
|
|
the email.
|
|
|
|
:returns: string in the form of "DD-Mmm-YYYY HH:MM:SS +HHMM"
|
|
|
|
(including double quotes) or `None` in case of failure
|
|
|
|
(which is fine as value for append)."""
|
2013-01-17 14:21:21 +01:00
|
|
|
|
2011-03-04 17:34:21 +01:00
|
|
|
if rtime is None:
|
2013-01-17 14:21:21 +01:00
|
|
|
rtime = emailutil.get_message_date(content)
|
|
|
|
if rtime == None:
|
2011-03-04 17:34:21 +01:00
|
|
|
return None
|
2013-01-17 14:21:21 +01:00
|
|
|
datetuple = time.localtime(rtime)
|
2011-03-04 17:34:21 +01:00
|
|
|
|
|
|
|
try:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Check for invalid dates.
|
2011-03-04 17:34:21 +01:00
|
|
|
if datetuple[0] < 1981:
|
|
|
|
raise ValueError
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Check for invalid dates.
|
2011-03-04 17:34:21 +01:00
|
|
|
datetuple_check = time.localtime(time.mktime(datetuple))
|
|
|
|
if datetuple[:2] != datetuple_check[:2]:
|
|
|
|
raise ValueError
|
|
|
|
|
|
|
|
except (ValueError, OverflowError):
|
|
|
|
# Argh, sometimes it's a valid format but year is 0102
|
|
|
|
# or something. Argh. It seems that Time2Internaldate
|
|
|
|
# will rause a ValueError if the year is 0102 but not 1902,
|
|
|
|
# but some IMAP servers nonetheless choke on 1902.
|
2015-01-08 17:13:33 +01:00
|
|
|
self.ui.debug('imap', "Message with invalid date %s. "
|
|
|
|
"Server will use local time."% datetuple)
|
2011-03-04 17:34:21 +01:00
|
|
|
return None
|
|
|
|
|
2015-01-14 22:58:25 +01:00
|
|
|
# Produce a string representation of datetuple that works as
|
|
|
|
# INTERNALDATE.
|
2011-03-04 17:34:21 +01:00
|
|
|
num2mon = {1:'Jan', 2:'Feb', 3:'Mar', 4:'Apr', 5:'May', 6:'Jun',
|
|
|
|
7:'Jul', 8:'Aug', 9:'Sep', 10:'Oct', 11:'Nov', 12:'Dec'}
|
|
|
|
|
2015-01-14 22:58:25 +01:00
|
|
|
# tm_isdst coming from email.parsedate is not usable, we still use it
|
|
|
|
# here, mhh.
|
2015-04-08 20:51:46 +02:00
|
|
|
if datetuple.tm_isdst == 1:
|
2011-03-04 17:34:21 +01:00
|
|
|
zone = -time.altzone
|
|
|
|
else:
|
|
|
|
zone = -time.timezone
|
|
|
|
offset_h, offset_m = divmod(zone//60, 60)
|
|
|
|
|
2015-01-14 22:58:25 +01:00
|
|
|
internaldate = '"%02d-%s-%04d %02d:%02d:%02d %+03d%02d"'% \
|
|
|
|
(datetuple.tm_mday, num2mon[datetuple.tm_mon], datetuple.tm_year, \
|
|
|
|
datetuple.tm_hour, datetuple.tm_min, datetuple.tm_sec, offset_h, offset_m)
|
2011-03-04 17:34:21 +01:00
|
|
|
|
|
|
|
return internaldate
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2006-08-22 03:09:36 +02:00
|
|
|
def savemessage(self, uid, content, flags, rtime):
|
2011-03-04 17:34:21 +01:00
|
|
|
"""Save the message on the Server
|
|
|
|
|
|
|
|
This backend always assigns a new uid, so the uid arg is ignored.
|
|
|
|
|
|
|
|
This function will update the self.messagelist dict to contain
|
|
|
|
the new message after sucessfully saving it.
|
|
|
|
|
2011-09-16 11:44:50 +02:00
|
|
|
See folder/Base for details. Note that savemessage() does not
|
|
|
|
check against dryrun settings, so you need to ensure that
|
|
|
|
savemessage is never called in a dryrun mode.
|
|
|
|
|
2011-03-04 17:34:23 +01:00
|
|
|
:param rtime: A timestamp to be used as the mail date
|
2011-07-26 10:59:54 +02:00
|
|
|
:returns: the UID of the new message as assigned by the server. If the
|
|
|
|
message is saved, but it's UID can not be found, it will
|
|
|
|
return 0. If the message can't be written (folder is
|
|
|
|
read-only for example) it will return -1."""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2011-09-16 11:44:50 +02:00
|
|
|
self.ui.savemessage('imap', uid, flags, self)
|
2011-03-04 17:34:21 +01:00
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Already have it, just save modified flags.
|
2011-03-28 16:19:20 +02:00
|
|
|
if uid > 0 and self.uidexists(uid):
|
2011-03-16 16:03:35 +01:00
|
|
|
self.savemessageflags(uid, flags)
|
|
|
|
return uid
|
|
|
|
|
2012-10-17 21:45:19 +02:00
|
|
|
content = self.deletemessageheaders(content, self.filterheaders)
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Use proper CRLF all over the message.
|
2012-10-16 20:53:54 +02:00
|
|
|
content = re.sub("(?<!\r)\n", CRLF, content)
|
2014-05-02 13:14:22 +02:00
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Get the date of the message, so we can pass it to the server.
|
2014-05-02 13:14:22 +02:00
|
|
|
date = self.__getmessageinternaldate(content, rtime)
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Message-ID is handy for debugging messages.
|
2014-07-01 05:44:18 +02:00
|
|
|
msg_id = self.getmessageheader(content, "message-id")
|
|
|
|
if not msg_id:
|
|
|
|
msg_id = '[unknown message-id]'
|
|
|
|
|
2011-09-13 16:27:54 +02:00
|
|
|
retry_left = 2 # succeeded in APPENDING?
|
2011-09-06 13:19:26 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
2014-02-26 14:51:48 +01:00
|
|
|
# NB: in the finally clause for this try we will release
|
|
|
|
# NB: the acquired imapobj, so don't do that twice unless
|
|
|
|
# NB: you will put another connection to imapobj. If you
|
|
|
|
# NB: really do need to release connection manually, set
|
|
|
|
# NB: imapobj to None.
|
2002-07-04 03:35:05 +02:00
|
|
|
try:
|
2011-09-13 16:27:54 +02:00
|
|
|
while retry_left:
|
2014-06-01 20:09:44 +02:00
|
|
|
# XXX: we can mangle message only once, out of the loop
|
2011-09-06 13:19:26 +02:00
|
|
|
# UIDPLUS extension provides us with an APPENDUID response.
|
|
|
|
use_uidplus = 'UIDPLUS' in imapobj.capabilities
|
|
|
|
|
|
|
|
if not use_uidplus:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Insert a random unique header that we can fetch later.
|
2014-03-16 13:27:35 +01:00
|
|
|
(headername, headervalue) = self.__generate_randomheader(
|
2015-01-08 17:13:33 +01:00
|
|
|
content)
|
|
|
|
self.ui.debug('imap', 'savemessage: header is: %s: %s'%
|
|
|
|
(headername, headervalue))
|
2014-06-01 20:09:44 +02:00
|
|
|
content = self.addmessageheader(content, CRLF, headername, headervalue)
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2016-07-28 06:51:47 +02:00
|
|
|
if len(content) > 200:
|
2015-01-14 22:58:25 +01:00
|
|
|
dbg_output = "%s...%s"% (content[:150], content[-50:])
|
2011-09-06 13:19:26 +02:00
|
|
|
else:
|
|
|
|
dbg_output = content
|
2015-01-08 17:13:33 +01:00
|
|
|
self.ui.debug('imap', "savemessage: date: %s, content: '%s'"%
|
|
|
|
(date, dbg_output))
|
2011-03-04 17:34:23 +01:00
|
|
|
|
2011-09-06 13:19:26 +02:00
|
|
|
try:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Select folder for append and make the box READ-WRITE.
|
2011-09-06 13:19:26 +02:00
|
|
|
imapobj.select(self.getfullname())
|
|
|
|
except imapobj.readonly:
|
|
|
|
# readonly exception. Return original uid to notify that
|
|
|
|
# we did not save the message. (see savemessage in Base.py)
|
|
|
|
self.ui.msgtoreadonly(self, uid, content, flags)
|
|
|
|
return uid
|
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Do the APPEND.
|
2011-09-06 13:19:26 +02:00
|
|
|
try:
|
2015-01-12 17:15:06 +01:00
|
|
|
(typ, dat) = imapobj.append(self.getfullname(),
|
2015-01-08 17:13:33 +01:00
|
|
|
imaputil.flagsmaildir2imap(flags), date, content)
|
2013-03-27 13:43:39 +01:00
|
|
|
# This should only catch 'NO' responses since append()
|
|
|
|
# will raise an exception for 'BAD' responses:
|
|
|
|
if typ != 'OK':
|
|
|
|
# For example, Groupwise IMAP server can return something like:
|
|
|
|
#
|
|
|
|
# NO APPEND The 1500 MB storage limit has been exceeded.
|
|
|
|
#
|
|
|
|
# In this case, we should immediately abort the repository sync
|
|
|
|
# and continue with the next account.
|
|
|
|
msg = \
|
2014-07-01 05:44:18 +02:00
|
|
|
"Saving msg (%s) in folder '%s', repository '%s' failed (abort). " \
|
2015-01-08 17:13:33 +01:00
|
|
|
"Server responded: %s %s\n"% \
|
2014-07-01 05:44:18 +02:00
|
|
|
(msg_id, self, self.getrepository(), typ, dat)
|
2013-03-27 13:43:39 +01:00
|
|
|
raise OfflineImapError(msg, OfflineImapError.ERROR.REPO)
|
2016-06-28 18:46:57 +02:00
|
|
|
retry_left = 0 # Mark as success.
|
2012-02-05 10:14:23 +01:00
|
|
|
except imapobj.abort as e:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Connection has been reset, release connection and retry.
|
Fix "command CHECK illegal in state AUTH"
Dave identified a case where our new dropped connection handling did
not work out correctly: we use the retry_left variable to signify
success (0=success if no exception occured).
However, we were decrementing the variable AFTER all the exception
checks, so if there was one due to a dropped connection, it
could well be that we 1) did not raise an exception (because we want to
retry), and 2) then DECREMENTED retry_left, which indicated "all is
well, no need to retry".
The code then continued to check() the append, which failed with the
above message (because we obtained a new connection which had not even
selected the current folder and we were still in mode AUTH). The fix is
of course, to fix our logic: Decrement retry_left first, THEN decide
whether to raise() (retry_left==0) or retry (retry_left>0) which would
then correctly attempt another loop. I am sorry for this newbie type of
logic error. The retry count loop was too hastily slipped in, it seems.
Reported-by: Dave Abrahams <dave@boostpro.com>
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
2011-09-26 16:04:00 +02:00
|
|
|
retry_left -= 1
|
2011-09-06 13:19:26 +02:00
|
|
|
self.imapserver.releaseconnection(imapobj, True)
|
|
|
|
imapobj = self.imapserver.acquireconnection()
|
2011-09-13 16:27:54 +02:00
|
|
|
if not retry_left:
|
2016-06-29 03:42:57 +02:00
|
|
|
six.reraise(OfflineImapError,
|
|
|
|
OfflineImapError("Saving msg (%s) in folder '%s', "
|
|
|
|
"repository '%s' failed (abort). Server responded: %s\n"
|
|
|
|
"Message content was: %s"%
|
|
|
|
(msg_id, self, self.getrepository(), str(e), dbg_output),
|
|
|
|
OfflineImapError.ERROR.MESSAGE),
|
|
|
|
exc_info()[2])
|
2015-01-11 21:44:24 +01:00
|
|
|
# XXX: is this still needed?
|
Fix "command CHECK illegal in state AUTH"
Dave identified a case where our new dropped connection handling did
not work out correctly: we use the retry_left variable to signify
success (0=success if no exception occured).
However, we were decrementing the variable AFTER all the exception
checks, so if there was one due to a dropped connection, it
could well be that we 1) did not raise an exception (because we want to
retry), and 2) then DECREMENTED retry_left, which indicated "all is
well, no need to retry".
The code then continued to check() the append, which failed with the
above message (because we obtained a new connection which had not even
selected the current folder and we were still in mode AUTH). The fix is
of course, to fix our logic: Decrement retry_left first, THEN decide
whether to raise() (retry_left==0) or retry (retry_left>0) which would
then correctly attempt another loop. I am sorry for this newbie type of
logic error. The retry count loop was too hastily slipped in, it seems.
Reported-by: Dave Abrahams <dave@boostpro.com>
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
2011-09-26 16:04:00 +02:00
|
|
|
self.ui.error(e, exc_info()[2])
|
2012-02-05 10:14:23 +01:00
|
|
|
except imapobj.error as e: # APPEND failed
|
2011-09-26 15:57:35 +02:00
|
|
|
# If the server responds with 'BAD', append()
|
|
|
|
# raise()s directly. So we catch that too.
|
2011-11-02 10:27:08 +01:00
|
|
|
# drop conn, it might be bad.
|
|
|
|
self.imapserver.releaseconnection(imapobj, True)
|
|
|
|
imapobj = None
|
2016-06-29 03:42:57 +02:00
|
|
|
six.reraise(OfflineImapError,
|
|
|
|
OfflineImapError("Saving msg (%s) folder '%s', repo '%s'"
|
|
|
|
"failed (error). Server responded: %s\nMessage content was: "
|
|
|
|
"%s"% (msg_id, self, self.getrepository(), str(e), dbg_output),
|
|
|
|
OfflineImapError.ERROR.MESSAGE),
|
|
|
|
exc_info()[2])
|
2012-02-24 08:31:31 +01:00
|
|
|
# Checkpoint. Let it write out stuff, etc. Eg searches for
|
|
|
|
# just uploaded messages won't work if we don't do this.
|
2012-02-24 08:35:59 +01:00
|
|
|
(typ,dat) = imapobj.check()
|
2012-02-24 08:31:31 +01:00
|
|
|
assert(typ == 'OK')
|
2003-04-18 04:18:34 +02:00
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
# Get the new UID, do we use UIDPLUS?
|
Remove the APPENDUID hack, previously introduced
As Gmail was only announcing the presence of the UIDPLUS extension
after we logged in, and we were then only getting server
capabilities before, a hack was introduced that checked the
existence of an APPENDUID reply, even if the server did not claim
to support it.
However, John Wiegley reports problems, where the APPENDUID would
be None, and we attempt to go this path (it seems that imaplib2
returns [None] if there is no such reply, so our test here for "!="
might fail. Given that this is an undocumented imaplib2 function
anyway, and we do fetch gmail capabilities after authentication,
this hack should no longer be necessary.
We had problems there earlier, where imapobj.response() would
return [None] although we had received a APPENDUID response from
the server, this might need more debugging and testing.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
2012-06-06 10:02:42 +02:00
|
|
|
if use_uidplus:
|
2016-06-28 18:46:57 +02:00
|
|
|
# Get new UID from the APPENDUID response, it could look
|
2012-01-07 01:28:20 +01:00
|
|
|
# like OK [APPENDUID 38505 3955] APPEND completed with
|
2012-02-24 08:35:59 +01:00
|
|
|
# 38505 bein folder UIDvalidity and 3955 the new UID.
|
|
|
|
# note: we would want to use .response() here but that
|
|
|
|
# often seems to return [None], even though we have
|
|
|
|
# data. TODO
|
|
|
|
resp = imapobj._get_untagged_response('APPENDUID')
|
Remove the APPENDUID hack, previously introduced
As Gmail was only announcing the presence of the UIDPLUS extension
after we logged in, and we were then only getting server
capabilities before, a hack was introduced that checked the
existence of an APPENDUID reply, even if the server did not claim
to support it.
However, John Wiegley reports problems, where the APPENDUID would
be None, and we attempt to go this path (it seems that imaplib2
returns [None] if there is no such reply, so our test here for "!="
might fail. Given that this is an undocumented imaplib2 function
anyway, and we do fetch gmail capabilities after authentication,
this hack should no longer be necessary.
We had problems there earlier, where imapobj.response() would
return [None] although we had received a APPENDUID response from
the server, this might need more debugging and testing.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
2012-06-06 10:02:42 +02:00
|
|
|
if resp == [None] or resp is None:
|
Update to match semantics of new imaplib2
The biggest change here is that imapobj.untagged_responses is no
longer a dictionary, but a list. To access it, I use the semi-private
_get_untagged_response method.
* offlineimap/folder/IMAP.py (IMAPFolder.quickchanged,
IMAPFolder.cachemessagelist): imaplib2 now explicitly removes its
EXISTS response on select(), so instead we use the return values from
select() to get the number of messages.
* offlineimap/imapserver.py (UsefulIMAPMixIn.select): imaplib2 now
stores untagged_responses for different mailboxes, which confuses us
because it seems like our mailboxes are "still" in read-only mode when
we just re-opened them. Additionally, we have to return the value
from imaplib2's select() so that the above thing works.
* offlineimap/imapserver.py (UsefulIMAPMixIn._mesg): imaplib2 now
calls _mesg with the name of a thread, so we display this
information in debug output. This requires a corresponding change to
imaplibutil.new_mesg.
* offlineimap/imaplibutil.py: We override IMAP4_SSL.open, whose
default arguments have changed, so update the default arguments. We
also subclass imaplib.IMAP4 in a few different places, which now
relies on having a read_fd file descriptor to poll on.
Signed-off-by: Ethan Glasser-Camp <ethan@betacantrips.com>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2011-03-10 21:36:20 +01:00
|
|
|
self.ui.warn("Server supports UIDPLUS but got no APPENDUID "
|
2015-01-08 17:13:33 +01:00
|
|
|
"appending a message.")
|
2012-02-24 08:35:59 +01:00
|
|
|
return 0
|
2016-05-08 16:42:52 +02:00
|
|
|
uid = int(resp[-1].split(' ')[1])
|
2012-02-24 08:35:59 +01:00
|
|
|
if uid == 0:
|
|
|
|
self.ui.warn("savemessage: Server supports UIDPLUS, but"
|
2015-01-08 17:13:33 +01:00
|
|
|
" we got no usable uid back. APPENDUID reponse was "
|
|
|
|
"'%s'"% str(resp))
|
2011-03-04 17:34:23 +01:00
|
|
|
else:
|
2016-06-28 18:46:57 +02:00
|
|
|
# We don't support UIDPLUS.
|
2014-03-16 13:27:35 +01:00
|
|
|
uid = self.__savemessage_searchforheader(imapobj, headername,
|
2015-01-08 17:13:33 +01:00
|
|
|
headervalue)
|
2012-02-24 08:35:59 +01:00
|
|
|
# See docs for savemessage in Base.py for explanation
|
2016-06-28 18:46:57 +02:00
|
|
|
# of this and other return values.
|
2011-03-04 17:34:23 +01:00
|
|
|
if uid == 0:
|
2012-01-20 14:33:16 +01:00
|
|
|
self.ui.debug('imap', 'savemessage: attempt to get new UID '
|
2012-02-16 16:49:06 +01:00
|
|
|
'UID failed. Search headers manually.')
|
2014-03-16 13:27:35 +01:00
|
|
|
uid = self.__savemessage_fetchheaders(imapobj, headername,
|
2015-01-08 17:13:33 +01:00
|
|
|
headervalue)
|
2012-02-16 16:49:06 +01:00
|
|
|
self.ui.warn('imap', "savemessage: Searching mails for new "
|
|
|
|
"Message-ID failed. Could not determine new UID.")
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
2016-07-28 06:51:47 +02:00
|
|
|
if imapobj:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2002-06-21 03:22:40 +02:00
|
|
|
|
2016-06-28 18:46:57 +02:00
|
|
|
if uid: # Avoid UID FETCH 0 crash happening later on
|
2014-08-03 14:47:26 +02:00
|
|
|
self.messagelist[uid] = self.msglist_item_initializer(uid)
|
|
|
|
self.messagelist[uid]['flags'] = flags
|
2006-05-16 05:40:23 +02:00
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
self.ui.debug('imap', 'savemessage: returning new UID %d'% uid)
|
2003-04-18 04:18:34 +02:00
|
|
|
return uid
|
|
|
|
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2015-11-25 07:39:56 +01:00
|
|
|
def _fetch_from_imap(self, uids, retry_num=1):
|
2015-01-08 17:13:33 +01:00
|
|
|
"""Fetches data from IMAP server.
|
2012-10-17 21:45:19 +02:00
|
|
|
|
|
|
|
Arguments:
|
|
|
|
- uids: message UIDS
|
|
|
|
- retry_num: number of retries to make
|
|
|
|
|
2015-01-08 17:13:33 +01:00
|
|
|
Returns: data obtained by this query."""
|
|
|
|
|
2015-11-25 07:39:56 +01:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
|
|
|
try:
|
|
|
|
query = "(%s)"% (" ".join(self.imap_query))
|
2016-06-28 18:46:57 +02:00
|
|
|
fails_left = retry_num # Retry on dropped connection.
|
2015-11-25 07:39:56 +01:00
|
|
|
while fails_left:
|
|
|
|
try:
|
2016-06-28 19:15:07 +02:00
|
|
|
imapobj.select(self.getfullname(), readonly=True)
|
2015-11-25 07:39:56 +01:00
|
|
|
res_type, data = imapobj.uid('fetch', uids, query)
|
|
|
|
break
|
|
|
|
except imapobj.abort as e:
|
|
|
|
fails_left -= 1
|
2016-05-25 03:29:03 +02:00
|
|
|
# self.ui.error() will show the original traceback.
|
2015-11-25 07:39:56 +01:00
|
|
|
if fails_left <= 0:
|
|
|
|
message = ("%s, while fetching msg %r in folder %r."
|
|
|
|
" Max retry reached (%d)"%
|
|
|
|
(e, uids, self.name, retry_num))
|
|
|
|
severity = OfflineImapError.ERROR.MESSAGE
|
|
|
|
raise OfflineImapError(message,
|
|
|
|
OfflineImapError.ERROR.MESSAGE)
|
2016-05-25 03:29:03 +02:00
|
|
|
# Release dropped connection, and get a new one.
|
2015-11-25 07:39:56 +01:00
|
|
|
self.imapserver.releaseconnection(imapobj, True)
|
|
|
|
imapobj = self.imapserver.acquireconnection()
|
|
|
|
self.ui.error("%s. While fetching msg %r in folder %r."
|
|
|
|
" Retrying (%d/%d)"%
|
|
|
|
(e, uids, self.name, retry_num - fails_left, retry_num))
|
|
|
|
finally:
|
|
|
|
# The imapobj here might be different than the one created before
|
|
|
|
# the ``try`` clause. So please avoid transforming this to a nice
|
|
|
|
# ``with`` without taking this into account.
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
|
|
|
|
IMAP: don't take junk data for valid mail content
OfflineIMAP frequently delivers mail files to the Maildir consisting exclusively
of a single ASCII digit in IDLE mode. IMAPFolder.getmessage expects 'data' to be
of the form
[(fetch-info, message-body)]
However, the imapobj.uid call in getmessage returns a list of *all* pending
untagged FETCH responses. If any message flags were changed in the selected
IMAP folder since the last command (by another client or another thread in
OfflineIMAP itself), the IMAP server will issue unsolicited FETCH responses
indicating these flag changes (RFC3501, section 7). When this happens, 'data'
will look like, for example
['1231 (FLAGS (\\Seen) UID 5300)',
'1238 (FLAGS (\\Seen) UID 5318)',
('1242 (UID 5325 BODY[] {7976}', message-body)]
Unfortunately, getmessage retrieves the message body as data[0][1], which in
this example is just the string "2", and this is what gets stored in the mail
file.
Multi-threaded OfflineIMAP with IDLE or holdconnectionopen is particularly
susceptible to this problem because flag changes synced back to the IMAP server
on one thread will appear as unsolicited FETCH responses on another thread if it
happens to have the same folder selected. This can also happen without IDLE or
holdconnectionopen or even in single-threaded OfflineIMAP with concurrent access
from other IMAP clients (webmail clients, etc.), though the window for the bug
is much smaller.
Ideally, either imaplib2 or getmessage would parse the fetch responses to find
the response for the requested UID. However, since IMAP only specifies
unilateral FETCH responses for flag changes, it's almost certainly safe to
simply find the element of 'data' that is a tuple (perhaps aborting if there is
more than one tuple) and use that.
Github-fix: https://github.com/OfflineIMAP/offlineimap/issues/162
Based-on-patch-by: Austin Clements <amdragon@MIT.EDU>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2016-07-28 07:18:23 +02:00
|
|
|
# Ensure to not consider unsolicited FETCH responses caused by flag
|
|
|
|
# changes from concurrent connections. These appear as strings in
|
|
|
|
# 'data' (the BODY response appears as a tuple). This should leave
|
|
|
|
# exactly one response.
|
|
|
|
if res_type == 'OK':
|
|
|
|
data = [res for res in data if not isinstance(res, str)]
|
|
|
|
# Could not fetch message.
|
|
|
|
if data == [None] or res_type != 'OK' or len(data) != 1:
|
2012-10-17 21:45:19 +02:00
|
|
|
severity = OfflineImapError.ERROR.MESSAGE
|
|
|
|
reason = "IMAP server '%s' failed to fetch messages UID '%s'."\
|
2015-01-08 17:13:33 +01:00
|
|
|
"Server responded: %s %s"% (self.getrepository(), uids,
|
2012-10-17 21:45:19 +02:00
|
|
|
res_type, data)
|
|
|
|
if data == [None]:
|
2016-05-25 03:29:03 +02:00
|
|
|
# IMAP server did not find a message with this UID.
|
2012-10-17 21:45:19 +02:00
|
|
|
reason = "IMAP server '%s' does not have a message "\
|
2016-06-28 18:46:57 +02:00
|
|
|
"with UID '%s'"% (self.getrepository(), uids)
|
2012-10-17 21:45:19 +02:00
|
|
|
raise OfflineImapError(reason, severity)
|
|
|
|
|
|
|
|
return data
|
|
|
|
|
|
|
|
|
|
|
|
def _store_to_imap(self, imapobj, uid, field, data):
|
2015-01-08 17:13:33 +01:00
|
|
|
"""Stores data to IMAP server
|
2012-10-17 21:45:19 +02:00
|
|
|
|
|
|
|
Arguments:
|
|
|
|
- imapobj: instance of IMAPlib to use
|
|
|
|
- uid: message UID
|
|
|
|
- field: field name to be stored/updated
|
|
|
|
- data: field contents
|
|
|
|
"""
|
|
|
|
imapobj.select(self.getfullname())
|
|
|
|
res_type, retdata = imapobj.uid('store', uid, field, data)
|
|
|
|
if res_type != 'OK':
|
|
|
|
severity = OfflineImapError.ERROR.MESSAGE
|
|
|
|
reason = "IMAP server '%s' failed to store %s for message UID '%d'."\
|
2015-01-08 17:13:33 +01:00
|
|
|
"Server responded: %s %s"% (
|
IMAP: don't take junk data for valid mail content
OfflineIMAP frequently delivers mail files to the Maildir consisting exclusively
of a single ASCII digit in IDLE mode. IMAPFolder.getmessage expects 'data' to be
of the form
[(fetch-info, message-body)]
However, the imapobj.uid call in getmessage returns a list of *all* pending
untagged FETCH responses. If any message flags were changed in the selected
IMAP folder since the last command (by another client or another thread in
OfflineIMAP itself), the IMAP server will issue unsolicited FETCH responses
indicating these flag changes (RFC3501, section 7). When this happens, 'data'
will look like, for example
['1231 (FLAGS (\\Seen) UID 5300)',
'1238 (FLAGS (\\Seen) UID 5318)',
('1242 (UID 5325 BODY[] {7976}', message-body)]
Unfortunately, getmessage retrieves the message body as data[0][1], which in
this example is just the string "2", and this is what gets stored in the mail
file.
Multi-threaded OfflineIMAP with IDLE or holdconnectionopen is particularly
susceptible to this problem because flag changes synced back to the IMAP server
on one thread will appear as unsolicited FETCH responses on another thread if it
happens to have the same folder selected. This can also happen without IDLE or
holdconnectionopen or even in single-threaded OfflineIMAP with concurrent access
from other IMAP clients (webmail clients, etc.), though the window for the bug
is much smaller.
Ideally, either imaplib2 or getmessage would parse the fetch responses to find
the response for the requested UID. However, since IMAP only specifies
unilateral FETCH responses for flag changes, it's almost certainly safe to
simply find the element of 'data' that is a tuple (perhaps aborting if there is
more than one tuple) and use that.
Github-fix: https://github.com/OfflineIMAP/offlineimap/issues/162
Based-on-patch-by: Austin Clements <amdragon@MIT.EDU>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
2016-07-28 07:18:23 +02:00
|
|
|
self.getrepository(), field, uid, res_type, retdata)
|
2012-10-17 21:45:19 +02:00
|
|
|
raise OfflineImapError(reason, severity)
|
|
|
|
return retdata[0]
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-06-21 03:55:06 +02:00
|
|
|
def savemessageflags(self, uid, flags):
|
2011-09-16 11:44:50 +02:00
|
|
|
"""Change a message's flags to `flags`.
|
|
|
|
|
|
|
|
Note that this function does not check against dryrun settings,
|
|
|
|
so you need to ensure that it is never called in a
|
|
|
|
dryrun mode."""
|
2015-01-14 22:58:25 +01:00
|
|
|
|
2002-07-04 05:59:19 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
2002-07-04 03:35:05 +02:00
|
|
|
try:
|
2015-01-08 17:13:33 +01:00
|
|
|
result = self._store_to_imap(imapobj, str(uid), 'FLAGS',
|
|
|
|
imaputil.flagsmaildir2imap(flags))
|
2012-10-17 21:45:19 +02:00
|
|
|
except imapobj.readonly:
|
2014-05-06 23:12:50 +02:00
|
|
|
self.ui.flagstoreadonly(self, [uid], flags)
|
2012-10-17 21:45:19 +02:00
|
|
|
return
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2012-10-17 21:45:19 +02:00
|
|
|
|
2002-07-12 15:20:09 +02:00
|
|
|
if not result:
|
|
|
|
self.messagelist[uid]['flags'] = flags
|
|
|
|
else:
|
|
|
|
flags = imaputil.flags2hash(imaputil.imapsplit(result)[1])['FLAGS']
|
|
|
|
self.messagelist[uid]['flags'] = imaputil.flagsimap2maildir(flags)
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-07-12 15:20:09 +02:00
|
|
|
def addmessageflags(self, uid, flags):
|
|
|
|
self.addmessagesflags([uid], flags)
|
2002-06-21 03:55:06 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __addmessagesflags_noconvert(self, uidlist, flags):
|
|
|
|
self.__processmessagesflags('+', uidlist, flags)
|
2003-01-09 03:16:07 +01:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2003-04-18 04:18:34 +02:00
|
|
|
def addmessagesflags(self, uidlist, flags):
|
|
|
|
"""This is here for the sake of UIDMaps.py -- deletemessages must
|
|
|
|
add flags and get a converted UID, and if we don't have noconvert,
|
|
|
|
then UIDMaps will try to convert it twice."""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__addmessagesflags_noconvert(uidlist, flags)
|
2003-04-18 04:18:34 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2003-01-09 03:16:07 +01:00
|
|
|
def deletemessageflags(self, uid, flags):
|
|
|
|
self.deletemessagesflags([uid], flags)
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2003-01-09 03:16:07 +01:00
|
|
|
def deletemessagesflags(self, uidlist, flags):
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__processmessagesflags('-', uidlist, flags)
|
2003-01-09 03:16:07 +01:00
|
|
|
|
2014-07-08 10:23:05 +02:00
|
|
|
def __processmessagesflags_real(self, operation, uidlist, flags):
|
2002-07-04 04:14:07 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
2002-07-04 03:35:05 +02:00
|
|
|
try:
|
2002-08-08 03:57:17 +02:00
|
|
|
try:
|
|
|
|
imapobj.select(self.getfullname())
|
|
|
|
except imapobj.readonly:
|
2011-01-05 17:00:57 +01:00
|
|
|
self.ui.flagstoreadonly(self, uidlist, flags)
|
2008-03-04 04:20:53 +01:00
|
|
|
return
|
2002-07-04 03:35:05 +02:00
|
|
|
r = imapobj.uid('store',
|
2015-01-08 17:13:33 +01:00
|
|
|
imaputil.uid_sequence(uidlist), operation + 'FLAGS',
|
|
|
|
imaputil.flagsmaildir2imap(flags))
|
2007-07-07 05:51:02 +02:00
|
|
|
assert r[0] == 'OK', 'Error with store: ' + '. '.join(r[1])
|
2002-07-12 01:35:51 +02:00
|
|
|
r = r[1]
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2002-07-12 01:35:51 +02:00
|
|
|
# Some IMAP servers do not always return a result. Therefore,
|
|
|
|
# only update the ones that it talks about, and manually fix
|
|
|
|
# the others.
|
2011-09-06 13:27:48 +02:00
|
|
|
needupdate = list(uidlist)
|
2002-07-03 07:05:49 +02:00
|
|
|
for result in r:
|
2002-07-12 01:35:51 +02:00
|
|
|
if result == None:
|
2002-07-12 04:04:04 +02:00
|
|
|
# Compensate for servers that don't return anything from
|
|
|
|
# STORE.
|
2002-07-12 01:35:51 +02:00
|
|
|
continue
|
2002-07-12 04:04:04 +02:00
|
|
|
attributehash = imaputil.flags2hash(imaputil.imapsplit(result)[1])
|
|
|
|
if not ('UID' in attributehash and 'FLAGS' in attributehash):
|
|
|
|
# Compensate for servers that don't return a UID attribute.
|
|
|
|
continue
|
2011-08-16 12:16:46 +02:00
|
|
|
flagstr = attributehash['FLAGS']
|
2016-05-08 16:42:52 +02:00
|
|
|
uid = int(attributehash['UID'])
|
2011-08-16 12:16:46 +02:00
|
|
|
self.messagelist[uid]['flags'] = imaputil.flagsimap2maildir(flagstr)
|
2002-07-12 01:35:51 +02:00
|
|
|
try:
|
|
|
|
needupdate.remove(uid)
|
2016-06-28 18:46:57 +02:00
|
|
|
except ValueError: # Let it slide if it's not in the list.
|
2002-07-12 01:35:51 +02:00
|
|
|
pass
|
|
|
|
for uid in needupdate:
|
2003-01-09 03:16:07 +01:00
|
|
|
if operation == '+':
|
2011-08-16 12:16:46 +02:00
|
|
|
self.messagelist[uid]['flags'] |= flags
|
2003-01-09 03:16:07 +01:00
|
|
|
elif operation == '-':
|
2011-08-16 12:16:46 +02:00
|
|
|
self.messagelist[uid]['flags'] -= flags
|
2002-07-03 07:05:49 +02:00
|
|
|
|
2014-07-08 10:23:05 +02:00
|
|
|
|
|
|
|
def __processmessagesflags(self, operation, uidlist, flags):
|
2016-06-28 18:46:57 +02:00
|
|
|
# Hack for those IMAP servers with a limited line length.
|
2014-07-08 10:23:05 +02:00
|
|
|
batch_size = 100
|
2016-05-08 17:32:51 +02:00
|
|
|
for i in range(0, len(uidlist), batch_size):
|
2014-07-10 08:24:11 +02:00
|
|
|
self.__processmessagesflags_real(operation,
|
|
|
|
uidlist[i:i + batch_size], flags)
|
2014-07-08 10:23:05 +02:00
|
|
|
return
|
|
|
|
|
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2011-08-30 10:52:11 +02:00
|
|
|
def change_message_uid(self, uid, new_uid):
|
|
|
|
"""Change the message from existing uid to new_uid
|
|
|
|
|
2013-07-21 21:00:23 +02:00
|
|
|
If the backend supports it. IMAP does not and will throw errors."""
|
2015-01-08 17:13:33 +01:00
|
|
|
|
2011-08-30 10:52:11 +02:00
|
|
|
raise OfflineImapError('IMAP backend cannot change a messages UID from '
|
2015-01-08 17:13:33 +01:00
|
|
|
'%d to %d'% (uid, new_uid), OfflineImapError.ERROR.MESSAGE)
|
2013-07-21 21:00:23 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-06-21 03:55:06 +02:00
|
|
|
def deletemessage(self, uid):
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__deletemessages_noconvert([uid])
|
2002-07-03 07:05:49 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
# Interface from BaseFolder
|
2002-07-03 07:16:56 +02:00
|
|
|
def deletemessages(self, uidlist):
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__deletemessages_noconvert(uidlist)
|
2003-04-18 04:18:34 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
def __deletemessages_noconvert(self, uidlist):
|
2002-07-03 07:05:49 +02:00
|
|
|
if not len(uidlist):
|
2011-04-11 18:33:11 +02:00
|
|
|
return
|
2002-07-04 03:35:05 +02:00
|
|
|
|
2014-03-16 13:27:35 +01:00
|
|
|
self.__addmessagesflags_noconvert(uidlist, set('T'))
|
2002-07-04 03:35:05 +02:00
|
|
|
imapobj = self.imapserver.acquireconnection()
|
|
|
|
try:
|
2008-03-04 15:13:48 +01:00
|
|
|
try:
|
|
|
|
imapobj.select(self.getfullname())
|
|
|
|
except imapobj.readonly:
|
2011-01-05 17:00:57 +01:00
|
|
|
self.ui.deletereadonly(self, uidlist)
|
2002-08-08 03:57:17 +02:00
|
|
|
return
|
2002-11-12 22:36:34 +01:00
|
|
|
if self.expunge:
|
|
|
|
assert(imapobj.expunge()[0] == 'OK')
|
2002-07-04 03:35:05 +02:00
|
|
|
finally:
|
|
|
|
self.imapserver.releaseconnection(imapobj)
|
2002-07-03 07:05:49 +02:00
|
|
|
for uid in uidlist:
|
2002-07-12 01:35:51 +02:00
|
|
|
del self.messagelist[uid]
|