Quoth Philip Hazel on Wed, Nov 10, 1999:
> On Wed, 10 Nov 1999, Dave Holland wrote:
>
> > To: inet:joe@???, inet:fred@???
>
> <groan>
Oh my. Novell must be LARTed on their heads with a copy of
RFC822 printed on large stone tablets. Dave, just submit a bug
report.
> You could set headers_check_syntax, and then it would reject these
> messages, making this Somebody Else's Problem. :-)
> Other than that, the only thing would be to run an expensive transport
> filter on outgoing messages and fix them up by hand.
There are several problems with that.
1. This transport should run from every director and router, once
per recipient. It's easier to run another copy of exim and
pass fixed messages to it.
2. The filter must parse RFC822 headers, _and_ get them right,
which is not trivial. And, in case somebody decides one day
to create a list called 'inet', it must not fix the headers
when they are correct (Philip, see your own .sig file). Too
hard. Although for simple cases, you can just read a full
header (i.e., all lines if it's multi-line) and do:
s/inet://g if !/;/;
which I define as dirty hack.
> I'm afraid I've
> made so many concessions in Exim for accommodating software that can't
> cope that my sympathy is running low...
I don't think that fixing these horros is needed. Again, this is
not trivial even if you do have a parser of RFC822 headers (which
you do).
Vadik.
--
Real software engineers don't debug programs, they verify correctness.
This process doesn't necessarily involve execution of anything on a
computer, except perhaps a Correctness Verification Aid package.
