Displaying 20 results from an estimated 31 matches for "curecanti".
2012 Mar 03
1
2.1.1: Incorrect quoting of RFC 2822 personal parts in ENVELOPE data
...XXXXXX" (({22}
XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({22}
XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL
NIL "XXXXXXX" "XXXXXXXXX.XXX")) ((NIL NIL "slusarz" "curecanti.org"))
NIL NIL NIL "<1109380587237.1109118788902.20323.7.35190001 at scheduler>"))
It should be:
1 UID FETCH 31734 (ENVELOPE)
* 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)"
"XXXXXX" (({20}
XXXXX "X-XX" XXXXXX NIL &quo...
2013 Feb 05
2
Possible sort optimization (?)
Maybe this is just noise... but I can reproduce this fairly reliably.
Mailbox with 21,000+ messages
This query:
a UID SORT RETURN (ALL COUNT) (DATE) UTF-8 SUBJECT "foo"
is always about 10 percent slower than this split query (I've done
this 4-5 times, and the numbers are similar):
a UID SEARCH RETURN (SAVE) CHARSET UTF-8 SUBJECT "foo"
b UID SORT RETURN (ALL COUNT)
2008 Oct 15
1
Bug: MODSEQ FETCH return (?)
...eturning as follows:
S: * 1 FETCH (UID 1 MODSEQ 3 FLAGS (\Flagged \Deleted \Recent))
Where, under the RFC, I believe it should be:
S: * 1 FETCH (UID 1 MODSEQ (3) FLAGS (\Flagged \Deleted \Recent))
Here is a proposed patch (WARNING: my C skills = zero):
# HG changeset patch
# User root at bigworm.curecanti.org
# Date 1224040830 21600
# Branch HEAD
# Node ID 0c0615bc6bf74ccf109049e251a30b8ab5f8ea67
# Parent 40df4d4cced09fa72d37581d0c526416d2c6e3de
per RFC 4551, MODSEQ FETCH responses need to be wrapped in ().
diff -r 40df4d4cced0 -r 0c0615bc6bf7 src/imap/imap-fetch.c
--- a/src/imap/imap-fetch.c Tue...
2008 Oct 26
1
PATCH: Advertise X-REFERENCES2
Don't see any reason why X-REFERENCES2 should not be advertised in the
CAPABILITY string - the wiki indicates this is a new addition for 1.2,
and RFC 5256 explicitly states that the THREAD= is to be used for
upwards-compatible extensions.
# HG changeset patch
# User root at bigworm.curecanti.org
# Date 1225057043 21600
# Branch HEAD
# Node ID 1f082281f8d4e3d364b85c08ec329cf1be7ba61f
# Parent 88a6a193e2884ac882ecc75e9ae9a242acc6188f
Add X-REFERENCES2 to CAPABILITY string.
diff -r 88a6a193e288 -r 1f082281f8d4 configure.in
--- a/configure.in Sun Oct 26 16:30:50 2008 +0200
+++ b/configur...
2010 Sep 01
2
Broken SELECT ""/EXAMINE ""
a EXAMINE INBOX
[...]
a OK [READ-ONLY] Select completed.
a EXAMINE ""
a NO Empty mailbox name.
[Should be in authenticated mode with no active mailbox. But...]
a STATUS INBOX (UIDVALIDITY)
* STATUS "INBOX" (UIDVALIDITY 1255685337)
a OK [CLIENTBUG] Status on selected mailbox completed.
a UNSELECT
a OK Unselect completed.
a STATUS INBOX (UIDVALIDITY)
* STATUS "INBOX"
2013 May 06
2
Keyword limit?
Running into a weird issue in a mailbox that has 26+ keywords.
In one session, I do this:
S: 2 SELECT "INBOX" (QRESYNC (1255685337 78608 [...uids...]))
S: [...]
S: * OK [HIGHESTMODSEQ 78608] Highest
S: * OK [UIDVALIDITY 1255685337] UIDs valid
S: 2 OK [READ-WRITE] Select completed.
C: 3 UID STORE 48386 (UNCHANGEDSINCE 78608) +FLAGS AAAAAAAA
S: * 8 FETCH (UID 48386 MODSEQ (78609) FLAGS
2013 May 21
1
CATENATE/literal8 issue
Using 2.2.2, I see this:
C: 6 APPEND "INBOX" (\seen) "16-May-2013 22:05:14 -0600" CATENATE (URL
"/INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER" TEXT ~{40}
S: 6 NO [UNKNOWN-CTE] Binary input allowed only when the first part is binary.
Why is there this limitation? It seems to me that CATENATE is
confusing the content-type encoding of the data/part
2013 Jun 13
1
MULTIAPPEND + literal8 issue
Background: importing a mbox file containing ~700 messages (20 MB).
Our program splits MULTIAPPENDS into approx. 5MB chunks. We don't use
literal+ in order to immediately catch errors.
I can reproducibly produce the following error (2.2.2) when doing a
MULTIAPPEND where every append is using literal8:
[...340 messages appended in 7 previous APPEND commands...]
C: 10 APPEND Test
2013 Sep 13
1
SELECT: Bug in untagged response
Dovecot 2.2.5
In selected state:
C: 1 SELECT &#-&#/#
S: 1 NO Mailbox name is not valid mUTF-7
S: * OK [CLOSED] Previous mailbox closed.
I can verify that this only seems to happen when the mailbox name is
incorrect mUTF-7. Things work fine if I access a non-existent mailbox:
C: 1 SELECT non-existent-mailbox
S: * OK [CLOSED] Previous mailbox closed.
S: a NO Mailbox doesn't exist:
2014 Apr 29
1
BINARY FETCH conversion issue
Given this test message, with admittedly incorrect QP encoding:
----
From: Test <test at example.com>
Subject: Test
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain
To: Test <test at example.com>
Date: Tue, 29 Apr 2014 00:54:10 +0000
Message-Id: <1 at example.com>
https://example.com/?from=bsu&url=http%3A//www.example.com/
----
2014 May 03
1
CONTEXT=SORT
Any reason this is not listed in the CAPABILITY string?
I see it listed as a TODO here: http://wiki2.dovecot.org/Roadmap
But it seems to work fine (as of 2.2.12):
1 UID SORT RETURN (CONTEXT COUNT) (SUBJECT) UTF-8 UNDELETED
* ESEARCH (TAG "1") UID COUNT 12
1 OK Sort completed (0.000 secs).
2 UID SORT RETURN (UPDATE COUNT) (SUBJECT) UTF-8 UNDELETED
* ESEARCH (TAG "2") UID
2015 Feb 12
2
Enabling mod-sequences
Hi list!
I have Dovecot 1.2.9 from Ubuntu repositories on my server.
Now I installed Horde and it give me sometimes the error "Mailbox does not
support mod-sequences".
Well, I must say, that I didn't know these mod-sequences, but I can' know
all...
Well, the question now is: how can I enable the support of the mod-sequences
on the mailboxes of my Server?
I searched in the
2014 Sep 04
2
charset-specific searches, and continuation lines
Hi there,
I'm looking into improving IMAP search support for the Gnus Emacs mail
client, and trying to add the ability to search non-ascii characters. So
far as I know, I start this invocation with something like:
. UID SEARCH CHARSET UTF-8 TEXT {NNN}
Where NNN is the number of bytes in my search string. Dovecot then
responds with:
+ OK
So... what do I do then? I don't actually know
2011 Dec 02
8
IMAP SPECIAL-USE extension
It's implemented now in dovecot-2.1 hg. It also deprecates autocreate plugin (but it still works the old way). The idea is that you can now do e.g.:
mailbox Trash {
auto = no
special_use = \Trash
}
mailbox Drafts {
auto = no
special_use = \Drafts
}
mailbox Sent {
auto = subscribe # autocreate, autosubscribe
special_use = \Sent
}
mailbox Spam {
auto = create # autocreate, but
2009 Oct 20
4
IMAP goes down from time to time
Good Afternoon
I?m really new at this and i don?t know if i?m posting at the right place.
My problem is that our Dovecot IMAP is stopping from time to time with
no info in the log, i just realize about this when our support person
call me saying that the whatsup monitor is showing the IMAP4 process
down. I can figure about this too by trying to get in our webmail Horde
and i cannot login.
2011 Apr 22
1
NONEXISTENT handling
As of 2.0.12, looks like NONEXISTENT response code isn't working
properly again. Previously brought up issues relating to this here:
http://markmail.org/message/jxbgdfv26pws66og
With a nonexistent mailbox "FOO", I see this:
1 DELETE "FOO"
1 NO Mailbox doesn't exist: FOO
// Should be: 1 NO [NONEXISTENT] Mailbox doesn't exist: FOO
2 RENAME "FOO"
2015 Feb 13
0
Enabling mod-sequences
Quoting Luca Bertoncello <lucabert at lucabert.de>:
> I have Dovecot 1.2.9 from Ubuntu repositories on my server.
> Now I installed Horde and it give me sometimes the error "Mailbox does not
> support mod-sequences".
This would happen if trying to do obtain MODSEQ on a mailbox that has
mod-sequences disabled. That error should be caught and not be
user-visible (I
2015 Mar 10
0
Outlook 2013/2010 nightmare #2
Quoting David.M.Clark <david at davrom.com>:
> Outlook also has a declaration that as of either version 2010 or
> 2013, they no longer download IMAP headers, they download the whole
> message - thank God for faster Internet connections these days -
> could you imagine that in the older dialup days? Still it is a waste
> of bandwidth and disk space to do this.
Except
2009 Mar 20
1
ESORT broken in Dovecot 1.2
Looks like ESORT is broken (just compiled 1.2 from hg 10 minutes ago).
Here is the command I'm using and the corresponding error message:
C: 5 UID SORT RETURN (ALL COUNT) (ARRIVAL) US-ASCII UNSEEN
S: 5 BAD Error in IMAP command UID: Invalid sort argument.
The corresponding UID SORT command (without the RETURN syntax) works fine:
5 UID SORT (ARRIVAL) US-ASCII UNSEEN
* SORT
5 OK Sort
2008 Dec 03
1
Broken sorting(?)
Somewhere between revision f5554ae61732 (12 days ago) and the release
of 1.2a4 (f53952ac4285; 9 days ago) sorting appears to have broken.
With the older revision, I see the following (using Maildir):
a sort (ARRIVAL) US-ASCII ALL
* SORT 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
49 50 51 52 53 54 55