On 12.03.2014 18:16, Pete wrote:
> On Wed, Mar 12, 2014 at 05:28:38PM +0530, tejas sarade wrote:
>>
>>No. Not the hostname that client pretends, I am talking about valid DNS A
>>record throuch DNS lookup.
>>
>>I just want to creat and access control system where I will provide the
>>
On Wed, Mar 12, 2014 at 05:28:38PM +0530, tejas sarade wrote:
>> how should that be possible?
>> the hostname the client pretends?
>> how could you trust that?
>> how could you trust any hostname?
>> there is nothing else trustable than the connecting real IP
>
>No. Not the
tejas sarade:
> I just want to creat and access control system where I will provide the
> list of valid hostname(FQDN).
> Postfix will lookup the IP of that FQDN through public DNS and consider
> that IP as trusted IP.
Access control by hostname is not reliable if you rely on remote
DNS servers.
-
Am 12.03.2014 12:58, schrieb tejas sarade:
>> how should that be possible?
>> the hostname the client pretends?
>> how could you trust that?
>> how could you trust any hostname?
>> there is nothing else trustable than the connecting real IP
>
> No. Not the hostname that client pretends, I am talki
> how should that be possible?
> the hostname the client pretends?
> how could you trust that?
> how could you trust any hostname?
> there is nothing else trustable than the connecting real IP
No. Not the hostname that client pretends, I am talking about valid DNS A
record throuch DNS lookup.
>
>
Am 12.03.2014 12:06, schrieb tejas sarade:
> I want to allow a machine with dynamic IP address but static hostname through
> DynDNS.
> I know that hostname in smtpd_client_restricions works only through reverse
> DNS lookup.
> Is there any way, I can allow the client based on hostname which has
Hello,
I want to allow a machine with dynamic IP address but static hostname
through DynDNS.
I know that hostname in smtpd_client_restricions works only through reverse
DNS lookup.
Is there any way, I can allow the client based on hostname which has
dynamic IP?
