IMAP Server Compliancy Status

• Checkpoint: checkpoint parameter works. When issuing a CHECK command in all sessions, their state looks identical.
  • It would actually be better to be consistent across all IMAP commands, but especially when NOOP or IDLE is used. Some servers have inconsistent IMAP session states because the client connections end up in e.g. different servers that don't synchronize immediately. This can cause problems with clients that rely on the different sessions seeing the same state.
• \Recent: Exactly one session sees a new message as \Recent - no more and no less.

  • imaptest prints an error if it notices multiple sessions having the same \Recent flag ("Message seq=.. UID=.. has \Recent flag in multiple sessions"). This happens automatically when running imaptest with multiple clients for the same user, e.g. imaptest user=testuser clients=10

  • But missing \Recent flags isn't detected with any tests
• Atomic flags: Flags and keywords can be added/removed in multiple sessions without one session dropping changes made by other

  • Test by running stress test with own_flags parameter and multiple clients for the same user, e.g. imaptest user=testuser clients=10 own_flags

• Expunge fetch: If message is expunged in one session, can another session that still sees the message fetch its contents?
  • Yes: Yes, everything can be fetched
  • Cached: Only cached data can be fetched. Message header or body can't be.
  • No: Nothing but flags can be fetched.
  • This needs to be tested manually to see how it behaves - there is no ready imaptest test for this.
• Expunge store: If message is expunged in one session, can another session update its flags?
  • Yes: Yes, and a 3rd session also sees the change
  • Session: Yes, but a 3rd session won't see the change

  • Delayed: Yes, but a 3rd session won't see any changes until EXPUNGEs are reported

  • Ignored: STORE command replies OK, but no change is made
  • No: STORE command replies NO
  • This needs to be tested manually to see how it behaves - there is no ready imaptest test for this.

• Failures (failures/total): Number of failures using scripted tests. These numbers may not be exact all the time, because the tests are still changing.

  • Failure groups: Each test belongs to a wider group of tests, typically testing a command or part of a command. If this count is low but individual command failure count is high, it probably means that the server has failed to implement wrong only a couple of commands.
  • Base fails: Number of individual base IMAP4rev1 protocol commands that failed.
  • Ext fails: Number of individual IMAP extension commands that failed. Extensions not supported aren't included in the numbers.

  • Test using e.g. imaptest user=testuser test=tests/

Fully compliant servers:

Non-compliant servers:

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