Imho, iff a leading dot in a local part is defined as illegal by the
relevant RFC(s), then it would make sense to include a check against it
in the default configuration. Unless there is some terribly good reason
to not do so... for example, a significant performance hit, or if there
are many legitimate users in the world currently depending on this
particular violation of the standards.
More generally, I would vote for rigorous enforcement of existing
standards, except in cases of extreme need If you do add it to the
default config, please post the ACL mods to the list, so those of us
already configured can do it the same way.
Jim Roberts
Punster Productions, Inc.
(a very happy Exim user)
----- Original Message -----
From: "Philip Hazel" <ph10@???>
To: "Peter N Lewis" <peter@???>
Cc: <exim-users@???>
Sent: Friday, June 14, 2002 7:00 AM
Subject: Re: [Exim] Dots in local parts
On Fri, 14 Jun 2002, Peter N Lewis wrote:
> Exactly, I check the local part with:
>
> require_files /Users/exim/exim/lists/$local_part
Well, that is fairly unusual, though I now see that it might be less
rare than I thought in connection with mailing lists. Though in those
cases, the delivery normally _reads_ the file rather than writing to it.
Easy enough to block local parts starting with . in the ACL. What do
other people think? Should I make this change to the default
configuration?
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
