[Exim] bug in foranyaddress, Exim 3.33?

Hi,

I wrote a system message filter and make use of the
foranyaddress phrase.

netscape (even the latest release) creates illegal To: headers, containing
a unquoted special characters, e.g.:

To: 12345: my name <my_name@???>

foranyaddress gives up on such illegal addresses returning a "false".
Anyway, Exim delivers such emails correct, so foranyaddress seems
to use a different parser.

Is there a way to
- work around this problem (unfortunately foranyaddress ${tr{$h_to:}{:}{_}}
does not work
- patch foranyaddress

Any ideas?

Regards, Markus Stoll