On Fri, 18 Apr 2003, Mark Bergsma wrote:
> > If an item begins with ``\'' and the rest of the item parses as a
> > valid RFC 2822 address that does not include a domain, the item is
> > qualified using the domain of the incoming address. In the absence of
> > a leading ``\'', unqualified addresses are qualified using the value
> > in qualify_recipient, but you can force the incoming domain to be
> > used by setting qualify_preserve_domain.
>
> However, when I have something like:
>
> a: somelocalpart@somedomain
> b: \a
>
> in an aliasfile, and qualify_preserve_domain is not set, Exim qualifies
> it to the setting of qualify_domain.
>
> I can't find any support for this in the Exim sourcecode, so I think
> this is either a bug in the documentation, or a missing Exim feature,
> depending on how you look at it. ;) Probably a leftover from Exim 3?
The support is around line 1504 in the parse.c source file. However,
there does seem to be a bug somewhere else in the code because the
correct domain is not getting passed to that code. I will investigate
this as soon as I can and post a patch.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
