I tested with my Entourage which I didn't use so far.
It gave:
Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord
and ends up by processed by mailman email.Header module:
Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord
It looks like they break a statement of RFC-2047:
Ordinary ASCII text and 'encoded-word's may appear
together in the
same header field. However, an 'encoded-word' that
appears in a
header field defined as '*text' MUST be separated from
any adjacent
'encoded-word' or 'text' by 'linear-white-space'.
I tested with my Entourage which I didn't use so far. 8859-1? B?9g==? =g=?ISO- 8859-1? B?5Q==? =sbord 1?q?=F6? = g =?iso-8859- 1?q?=E5? = sbord
It gave:
Sm=?ISO-
and ends up by processed by mailman email.Header module:
Sm =?iso-8859-
It looks like they break a statement of RFC-2047: white-space' .
Ordinary ASCII text and 'encoded-word's may appear
together in the
same header field. However, an 'encoded-word' that
appears in a
header field defined as '*text' MUST be separated from
any adjacent
'encoded-word' or 'text' by 'linear-