Le 7 juil. 09 à 22:04, Timo Sirainen a écrit :
On Wed, 2009-07-01 at 17:48 +0200, Axel Luttgens wrote:
In fact, any additional mailbox is created with that unique and
persistent UIDVALIDITY of 1.
Fixed: http://hg.dovecot.org/dovecot-1.2/rev/568ddefd7c18
Many thanks!
Axel
On Wed, 2009-07-01 at 17:48 +0200, Axel Luttgens wrote:
> In fact, any additional mailbox is created with that unique and
> persistent UIDVALIDITY of 1.
Fixed: http://hg.dovecot.org/dovecot-1.2/rev/568ddefd7c18
signature.asc
Description: This is a digitally signed message part
Le 2 juil. 09 à 18:12, Timo Sirainen a écrit :
On Jul 1, 2009, at 5:48 PM, Axel Luttgens wrote:
* OK [UIDVALIDITY 1] UIDs valid
Hmm. Wonder when that got broken. It used to work, but yes, I can
reproduce it with v1.2 too. I'll take a look at it in a few days.
Hello Timo,
Anxious
On Jul 1, 2009, at 5:48 PM, Axel Luttgens wrote:
* OK [UIDVALIDITY 1] UIDs valid
Hmm. Wonder when that got broken. It used to work, but yes, I can
reproduce it with v1.2 too. I'll take a look at it in a few days.
Going further with my question... ;-)
It stemmed from that consideration (and related ones) of RFC3501:
2.3.1.1.Unique Identifier (UID) Message Attribute
A 32-bit value assigned to each message, which when used with the
unique identifier validity value (see below) forms a
My base concern may be illustrated with the help of that simple telnet
session:
# telnet 127.0.0.1 imap
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
AUTH=PLAIN] Dove
