Yeah.
It need to get increment on delivery. Maybe it would worth to re-think
our design todo this directly in the underlying storage in one step
(if possible).
Currently we do this:
1) Get mailbox
2) increment lastuid
3) persist changes
The problem here is that we need to make sure other
Hi Norman,
As discussed, it may be worth to reread the RFC requirements:
I've copy/paste the RFC paragraph here after.
Can we deduce from that that the uid must be incremented by one for each
mail arriving in a mailbox?
Tks,
Eric
2.3.1.1.Unique Identifier (UID) Message Attribute
A
Hi,
Section 2.3.1.1 of IMAP RFC (http://www.faqs.org/rfcs/rfc3501.html)
states that Unique identifiers MUST be strictly ascending in the mailbox
at all times.
This is currently enforced in
org.apache.james.imap.store.mail.model.Mailbox#consumeUid() for the JPA
store.
A JPAStressTest has
Hi Eric,
thx to follow up on this. Comments inside
2010/5/11 Eric Charles eric.char...@u-mangate.com:
Hi,
Section 2.3.1.1 of IMAP RFC (http://www.faqs.org/rfcs/rfc3501.html) states
that Unique identifiers MUST be strictly ascending in the mailbox at all
times.
This is currently enforced in
