Differences between revisions 36 and 37
Revision 36 as of 2008-06-13 06:35:20
Size: 3211
Editor: TimoSirainen
Comment:
Revision 37 as of 2008-06-21 15:52:02
Size: 3211
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
|| [http://www.dovecot.org/ Dovecot] 1.0.14 || Yes || Unreliable || Bugs || B || 2/34 || || [http://www.dovecot.org/ Dovecot] 1.0.15 || Yes || Unreliable || Bugs || B || 1/34 ||

IMAP Server Compliance

  • Checkpoint: checkpoint parameter works. When issuing a CHECK command in all sessions, their state looks identical.
  • \Recent: Exactly one session sees a new message as \Recent - no more and no less.
  • Atomic flags: Flags and keywords can be added/removed in multiple sessions without one session dropping changes made by other (own_flags test)
  • Expunges: How messages expunged by another session are handled.
    • A: Expunging a message from one session keeps it available for other sessions until they can be notified that it's expunged. Flag updates to expunged messages may not be visible to other sessions though.
    • B: Some cached fields may be returned for expunged messages, but message bodies can't be retrieved anymore. Flags can still be updated within the session (but updates may not be visible to other sessions).
    • C: Even message flags can't be updated for expunged messages.
  • Failures: Number of failures using [:ImapTest/Tests:command/reply tests] (failures / number of tests). These numbers may not be exact all the time, because the tests are still changing.

Fully compliant servers:

Server

Checkpoint

\Recent

Atomic flags

Expunges

Failures

[http://www.dovecot.org/ Dovecot] 1.1.rc10+

Yes

Yes

Yes

B

0/34

Non-compliant servers:

Server

Checkpoint

\Recent

Atomic flags

Expunges

Failures

[http://www.dovecot.org/ Dovecot] 1.0.15

Yes

Unreliable

Bugs

B

1/34

[http://www.washington.edu/imap/ UW-IMAP] 2007b, mix format

Yes

Yes

Yes

A

2/34

[http://www.isode.com/products/m-box.html Isode M-Box] 14.3a0

No

Unreliable

Yes

C

6/34

[http://www.communigate.com/community/ CommuniGate Pro] 5.2.1

Yes

Yes

Yes

C

8/34

[http://www.zimbra.com/ Zimbra] 5.0.5

Yes

Yes

Yes

C

8/34

[http://cyrusimap.web.cmu.edu/ Cyrus] 2.3.12p2

No

Unreliable

Bugs

B? Buggy

9/34

[http://www.sun.com/software/products/messaging_srvr/index.xml Sun Java Messenging Server] 6.3-0.15

No

Unreliable

Bugs

A

9/34

[http://www.courier-mta.org/imap/ Courier] 4.3.1

Yes

Unreliable

Yes

C

18/34

[http://www.citadel.org/ Citadel] 7.36

No

No

Yes

A

19/34

[http://www.dbmail.org/ dbmail] 2.3.3

Crashes too early to test. APPEND missing EXISTS replies.

Major problems with multiple connections (makes further testing difficult and MAY CAUSE ACCIDENTAL MAIL LOSS!):

Server

Checkpoint

\Recent

Atomic flags

Expunges

Failures

[http://www.archiveopteryx.org/ Archiveopteryx] 2.10

?

?

?

C - EXPUNGEs are sent wrong

[http://www.ibm.com/software/lotus/products/notes/ IBM Domino] 8.0

No

Unreliable

?

C - Too many EXPUNGEs are sent, EXISTS is dropped before sending EXPUNGEs, FETCHing with valid messagesets produce errors

16/34

[http://www.kerio.eu/kms_home.html Kerio Mail Server] 6.5.1

?

?

?

EXPUNGEs are sent wrong

18/34

None: ImapTest/ServerStatus (last edited 2023-11-07 21:14:12 by TimoSirainen)