Craig Whitmore wrote:
> Hi there.. I have a rule in exim which is below..
> I've found out that this blocks Amercian Express Emails as the Subject has:
>
> Subject: Your American Express® Online Statement Is Ready To View
> instead of:
> Subject:
> =?iso-8859-1?Q?Your_American_Express=AE_Online_Statement_Is_Ready_To_View?=
>
> The RFC's says chars like the ® have to be encoded into ASCII in headers or
> they are not valid
>
> Has anyone contacted American Express about this before?
>
> Thanks
> Craig
>
> deny message = Message headers contain non ASCII chars
> log_message = Message headers contain non ASCII chars
> condition = ${if \
> or { \
> {match{$rh_bcc:}{\N[\x80-\xff]\N}}\
> {match{$rh_cc:}{\N[\x80-\xff]\N}}\
> {match{$rh_from:}{\N[\x80-\xff]\N}}\
> {match{$rh_reply-to:}{\N[\x80-\xff]\N}}\
> {match{$rh_sender:}{\N[\x80-\xff]\N}}\
> {match{$rh_subject:}{\N[\x80-\xff]\N}}\
> {match{$rh_to:}{\N[\x80-\xff]\N}}\
> } \
> {yes}{no} \
> }
> hosts = !+relay_from_hosts
>
>
I have just cut'n pasted that subject, '®' included, and sent it via a non-Exim
MX in Zurich thru an Exim MX in Hong Kong, MUA Mozilla on Mac OS X in Virginia
at both ends, and nary a problem.
Header shows encoding as UTF-8, though. Not iso-8859-1
Your ruleset will block a great of 'pragmatically allowable' message traffic,
even if you think the whole universe ends at US borders and runs only on US-Windows.
Either of which would be an odd stance for a Kiwi.
;-)
Bill Hacker
