Re: client hostname resolution

2014-08-26 Thread Martin Vegter
On 08/26/2014 12:56 AM, Viktor Dukhovni wrote: Are there any reasons against using chrooted smtp ? Chroot jails require an expert administrator, able to trouble-shoot problems with plugins or system libraries that depend on resources that may not exist in the jail. Debian made the

Re: client hostname resolution

2014-08-26 Thread Wietse Venema
Martin Vegter: On 08/26/2014 12:56 AM, Viktor Dukhovni wrote: Are there any reasons against using chrooted smtp ? Chroot jails require an expert administrator, able to trouble-shoot problems with plugins or system libraries that depend on resources that may not exist in the jail.

Re: client hostname resolution

2014-08-26 Thread Martin Vegter
On 08/26/2014 03:13 PM, Wietse Venema wrote: Martin Vegter: On 08/26/2014 12:56 AM, Viktor Dukhovni wrote: Are there any reasons against using chrooted smtp ? Chroot jails require an expert administrator, able to trouble-shoot problems with plugins or system libraries that depend on

Re: client hostname resolution

2014-08-26 Thread Wietse Venema
Martin Vegter: May I ask list members an opinion? Now when chroot works, is it recommended to use it? Does it provide an extra layer of security? That depends on what else is running in your system. Besides a small unprivileged Postfix network daemon inside a chroot jail, do you

client hostname resolution

2014-08-25 Thread Martin Vegter
Hello, I have noticed that my Postfix never resolves client IP Addresses into hostnames. In the logs I have always entries like the following: connect from unknown[173.194.40.54] I can resolve the IP manually into FQDN, using dig or host commands: host 173.194.40.54 So any DNS

Re: client hostname resolution

2014-08-25 Thread Wietse Venema
Martin Vegter: Hello, I have noticed that my Postfix never resolves client IP Addresses into hostnames. In the logs I have always entries like the following: connect from unknown[173.194.40.54] I can resolve the IP manually into FQDN, using dig or host commands: host

Re: client hostname resolution

2014-08-25 Thread Wietse Venema
Wietse Venema: Martin Vegter: Hello, I have noticed that my Postfix never resolves client IP Addresses into hostnames. In the logs I have always entries like the following: connect from unknown[173.194.40.54] I can resolve the IP manually into FQDN, using dig or host

Re: client hostname resolution

2014-08-25 Thread Martin Vegter
On 08/25/2014 11:28 PM, Wietse Venema wrote: Do I ned to change any settings in postfix, so that client IPs are resolved into hostnames? You need the correct DNS server in /etc/resolv.conf. You must not have disable_dns_lookups=yes in main.cf or master.cf. You must not have

Re: client hostname resolution

2014-08-25 Thread li...@rhsoft.net
Am 26.08.2014 um 00:04 schrieb Martin Vegter: On 08/25/2014 11:28 PM, Wietse Venema wrote: Do I ned to change any settings in postfix, so that client IPs are resolved into hostnames? You need the correct DNS server in /etc/resolv.conf. You must not have disable_dns_lookups=yes in main.cf

Re: client hostname resolution

2014-08-25 Thread Martin Vegter
On 08/26/2014 12:11 AM, li...@rhsoft.net wrote: Am 26.08.2014 um 00:04 schrieb Martin Vegter: I have turned off chroot for smtp and now it works. But that is not an optimal solution. I would like to keep chrooted smtp. why? you need to have a good reason besides i want chroot watching

Re: client hostname resolution

2014-08-25 Thread Viktor Dukhovni
On Tue, Aug 26, 2014 at 12:25:02AM +0200, Martin Vegter wrote: Are there any reasons against using chrooted smtp ? Chroot jails require an expert administrator, able to trouble-shoot problems with plugins or system libraries that depend on resources that may not exist in the jail. Debian made

Re: client hostname resolution

2014-08-25 Thread Scott Kitterman
On Tuesday, August 26, 2014 00:04:31 Martin Vegter wrote: On 08/25/2014 11:28 PM, Wietse Venema wrote: Do I ned to change any settings in postfix, so that client IPs are resolved into hostnames? You need the correct DNS server in /etc/resolv.conf. You must not have