|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: .sub.domain matching problem in client_access
From: James Garrison (jhg
athensgroup.com)
Date: Tue Jul 13 2004 - 13:53:18 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wietse Venema wrote:
> James Garrison:
>
>>Wietse Venema wrote:
>>
>>
>>>What exactly is not clear of the following two words:
>>>
>>> instead of
>>>
>>
>>The full context is "instead of requiring", which can be read as
>>
>>1) With parent_domain_matches_subdomains set, you are
>> no longer required to provide a leading dot.
>>
>>OR
>>
>>2) With parent_domain_matches_subdomains set, you
>> MUST NOT provide a leading dot.
>>
>>Either interpretation is correct without more explicit
>>information.
>
>
> X "instead of" Y implies EXCLUSION, not CO-EXISTENCE.
>
> This machine boots BSD instead of Windows.
>
> War instead of peace.
>
> Freedom instead of slavery.
>
> Wietse
>
Please don't take this personally. All the examples you quote
are correct, but when you say "instead of requiring" there
are two possible interpretations, both equally valid:
required/optional
required/forbidden
It is not clear which of these is implied in the documentation.
I assumed the first, and Postfix implements the latter.
Won't you at least consider the possibility that this might
be ambiguous?
--
James Garrison Athens Group, Inc.
mailto:jhg
athensgroup.com 5608 Parkcrest Dr
http://www.athensgroup.com Austin, TX 78731
PGP: RSA=0x92E90A3B DH/DSS=0x498D331C (512) 345-0600 x150
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]