On Fri, 18 Apr 2003, Mark Bergsma wrote:
> 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.
It appears that this bug has always been present in Exim 4. I must have
broken the code when converting from Exim 3, and there appears not to
have been anything in the test suite to pick it up. The patch to fix it
is below, and (needless to say) the test suite now checks this feature.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
*** exim-4.14/src/rda.c Tue Mar 11 12:20:22 2003
--- rda.c Tue Apr 22 09:53:58 2003
***************
*** 376,382 ****
options, /* specials that are allowed */
generated, /* where to hang them */
error, /* for errors */
! qualify_domain_recipient, /* to qualify \name */
include_directory, /* restrain to directory */
eblockp); /* for skipped syntax errors */
}
--- 388,394 ----
options, /* specials that are allowed */
generated, /* where to hang them */
error, /* for errors */
! deliver_domain, /* to qualify \name */
include_directory, /* restrain to directory */
eblockp); /* for skipped syntax errors */
}
