GitLab

Apparently when building without Kerberos support the entire contents of
camel-sasl-gssapi.c is omitted, which breaks generating API docs because
camel-scan.c expects a camel_sasl_gssapi_get_type() regardless.

With this commit, when building with Kerberos support, CamelSaslGssapi
is still a registered CamelSasl subclass but it does absolutely nothing
and is never used by Camel's SASL support.

For some reason, cached mail message files are sometimes winding up as
zero-length files.  Still need to figure out how this is happening, but
in the meantime teach Camel to disregard zero-length cache files.

Should have been commited to master

This reverts commit 28feecc3.

The default for the 'filter' option in imapx was set to False.
Now we make the default be True.  This means that incoming
messages through imapx will be filtered with Evolution's normal
filters.  A default of False means that your configuration doesn't
work - people have no idea why their filters aren't working.
Signed-off-by: Federico Mena Quintero <federico@novell.com>

On Debian sid, using binutils-gold, a couple missing links are discovered.

Commit e02cb958 ("Fix QRESYNC protocol violation (RH #648082))
introduced a potential leak of the 'lastuid' and 'firstuid' strings.

It would almost never happen, because it would require that we're
selecting a folder on a QRESYNC-capable server where we *have*
previously seen messages in that folder, but for some reason we don't
have a record of the uidvalidity and previous modification sequence
(modseq). The only time that's ever likely to happen is perhaps the
first time we connect to the server after QRESYNC is enabled. But that's
no excuse.

Fix this by simplifying the logic. There's no point in using QRESYNC if
our local cache knows of no messages in the folder *anyway*, so remove
that separate check and merge the 'if (total)' part into the existing
condition for actually issuing QRESYNC.

Spotted by Bojan Smojver.

The sequence-set '1:*' isn't valid in QRESYNC, and newer versions of
Dovecot (>=2.0) have started to object to it.

Ideally we'd omit the parameter completely, since it's supposed to be
optional — but *older* versions of Dovecot (<=1.2.13) require it.

We only really care about messages which we already knew about. For any
*new* messages, we're going to fetch the headers and the flags in an
explicit FETCH command anyway, and we'll ignore anything that QRESYNC
tells us about them. So just use the first and last UID from our existing
summary cache as the range for the QRESYNC command.

Fix a shadow declaration of the 'uid' variable in an inner block, while
we're at it.