¿Qué indicadores IMAP son compatibles de manera confiable en la mayoría de los servidores de correo?

Estoy escribiendo una aplicación que reacciona a los correos electrónicos enviados a un buzón. Recupera los correos electrónicos a través de IMAP. Se implementará en varios sistemas donde no controlo la configuración del servidor de correo.

Me gustaría usar banderas IMAP para indicar qué mensajes se han manejado. ¿Los indicadores del sistema son lo suficientemente compatibles como para que pueda confiar razonablemente en ellos en mi aplicación? ¿Las banderas definidas por el usuario son suficientemente compatibles?

(Si la respuesta es "ja, ja, no una oportunidad", entonces usaré carpetas en su lugar).

Gracias

-Ben

Eche un vistazo a esta colección de sesiones de ejemplo del servidor IMAP . Esencialmente, cada vez que vea PERMANENTFLAGScontener \*, el servidor admitirá indicadores definidos por el usuario.

Para agregar a esa lista, aquí hay un extracto de una sesión de Gimap (IMAP de Google Mail):

* OK Gimap ready for requests from 192.0.2.1 5if380490pzk.17
a login username password
* CAPABILITY IMAP4rev1 UNSELECT LITERAL+ IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE
a OK [email protected] authenticated (Success)
b select inbox
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]
* OK [UIDVALIDITY 2]
* 1089 EXISTS
* 0 RECENT
* OK [UIDNEXT 2371]
b OK [READ-WRITE] inbox selected. (Success)
c logout
* BYE LOGOUT Requested
c OK 73 good day (Success)

Y de manera similar, una sesión de Exchange 2007:

* OK Microsoft Exchange Server 2007 IMAP4 service ready
00000000 CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI IDLE NAMESPACE LITERAL+
00000000 OK CAPABILITY completed.
   [...]
00000003 SELECT INBOX
* 1 EXISTS
* 0 RECENT
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
* OK [UIDVALIDITY 472] UIDVALIDITY value
* OK [UIDNEXT 7] The next unique identifier value
00000003 OK [READ-WRITE] SELECT completed.

No pude encontrar una sesión de Exchange 2010.

Por lo tanto, no es universal, con Exchange como el abstinencia notable, pero seguro que es más común que no.

El documento principal del protocolo IMAP es RFC3501. La Sección 2.3.2 describe los indicadores estándar con los que toda implementación IMAP debe trabajar.

¿Los indicadores del sistema son lo suficientemente compatibles como para que pueda confiar razonablemente en ellos en mi aplicación?

De hecho, RFC3501 describe las banderas del sistema universal.

¿Las banderas definidas por el usuario son suficientemente compatibles?

No hay ningún RFC sobre el tema de las banderas definidas por el usuario, solo propuestas .

RFC 3501                         IMAPv4                       March 2003

2.3.2.  Flags Message Attribute

   A list of zero or more named tokens associated with the message.  A
   flag is set by its addition to this list, and is cleared by its
   removal.  There are two types of flags in IMAP4rev1.  A flag of
   either type can be permanent or session-only.

   A system flag is a flag name that is pre-defined in this
   specification.  All system flags begin with "\".  Certain system
   flags (\Deleted and \Seen) have special semantics described
   elsewhere.  The currently-defined system flags are:

        \Seen
           Message has been read

        \Answered
           Message has been answered

        \Flagged
           Message is "flagged" for urgent/special attention

        \Deleted
           Message is "deleted" for removal by later EXPUNGE

        \Draft
           Message has not completed composition (marked as a draft).

        \Recent
           Message is "recently" arrived in this mailbox.  This session
           is the first session to have been notified about this
           message; if the session is read-write, subsequent sessions
           will not see \Recent set for this message.  This flag can not
           be altered by the client.

           If it is not possible to determine whether or not this
           session is the first session to be notified about a message,
           then that message SHOULD be considered recent.

           If multiple connections have the same mailbox selected
           simultaneously, it is undefined which of these connections
           will see newly-arrived messages with \Recent set and which
           will see it without \Recent set.

   A keyword is defined by the server implementation.  Keywords do not
   begin with "\".  Servers MAY permit the client to define new keywords
   in the mailbox (see the description of the PERMANENTFLAGS response
   code for more information).

   A flag can be permanent or session-only on a per-flag basis.
   Permanent flags are those which the client can add or remove from the
   message flags permanently; that is, concurrent and subsequent
   sessions will see any change in permanent flags.  Changes to session
   flags are valid only in that session.

    Note: The \Recent system flag is a special case of a
    session flag.  \Recent can not be used as an argument in a
    STORE or APPEND command, and thus can not be changed at
    all.

Exchange 2010 tiene el mismo conjunto de BANDERAS PERMANENTES

* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Perman
ent flags