MESSAGE/RFC822 and Base64

Zbierski Christophe Christophe.Zbierski at
Wed Sep 29 03:36:50 EDT 2010

Hello, according to RFC 2045, it is not possible to have an attachment of type message/rfc822 encoded in base64.

5.2.1.  RFC822 Subtype
   No encoding other than "7bit", "8bit", or "binary" is permitted for
   the body of a "message/rfc822" entity.  The message header fields are
   always US-ASCII in any case, and data within the body can still be
   encoded, in which case the Content-Transfer-Encoding header field in
   the encapsulated message will reflect this.  Non-US-ASCII text in the
   headers of an encapsulated message can be specified using the
   mechanisms described in RFC 2047.

But, sometimes attachments are Base64. In this case, cyrus considers that the base64 is the header of email (which is attached).
So, some commands such as:
A1 FETCH 1 BODY[2.HEADER.FIELDS TO] can take a long time and cpu (in case of the attachment is large).

Is it possible to change cyrus consider this particular case.

Christophe Zbierski

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

More information about the Cyrus-devel mailing list