Re: [SOLVED] A bug, maybe?

2016-02-23 Thread Bill Cole
On 23 Feb 2016, at 15:44, Peter wrote: On 23/02/16 08:57, Curtis Maurand wrote: The problem was in the /etc/nsswitch.conf. I changed the line hosts: files dns to hosts:dns files and that solved the trouble. You likely want this to be, "files dns", otherwise with dns listed

Re: [SOLVED] Re: A bug, maybe?

2016-02-23 Thread Peter
On 23/02/16 08:57, Curtis Maurand wrote: > The problem was in the /etc/nsswitch.conf. > > I changed the line > > hosts: files dns > > to > > hosts:dns files > > and that solved the trouble. You likely want this to be, "files dns", otherwise with dns listed first you will find t

Re: [SOLVED] Re: A bug, maybe?

2016-02-22 Thread Curtis Maurand
On 2/22/2016 3:03 PM, Viktor Dukhovni wrote: On Mon, Feb 22, 2016 at 02:57:23PM -0500, Curtis Maurand wrote: The problem was in the /etc/nsswitch.conf. I changed the line hosts: files dns to hosts:dns files and that solved the trouble. Is "delivery.mailspamprotection.

Re: [SOLVED] Re: A bug, maybe?

2016-02-22 Thread Viktor Dukhovni
On Mon, Feb 22, 2016 at 02:57:23PM -0500, Curtis Maurand wrote: > The problem was in the /etc/nsswitch.conf. > I changed the line > hosts: files dns > to > hosts:dns files > and that solved the trouble. Is "delivery.mailspamprotection.com" listed in /etc/hosts? If so, then

Re: [SOLVED] Re: A bug, maybe?

2016-02-22 Thread Danny Horne
On 22/02/2016 7:57 pm, Curtis Maurand wrote: > > The problem was in the /etc/nsswitch.conf. > > I changed the line > > hosts: files dns > > to > > hosts:dns files > > and that solved the trouble. Interesting, I got the IP result Viktor got, but have the same nsswitch.conf setting as

[SOLVED] Re: A bug, maybe?

2016-02-22 Thread Curtis Maurand
On 2/20/2016 5:19 PM, Curtis Maurand wrote: On 2/20/2016 1:46 PM, Viktor Dukhovni wrote: On Sat, Feb 20, 2016 at 01:37:39PM -0500, Curtis Maurand wrote: Nothing is chrooted. resolv.conf is world readable. Wietse's program returns a valid address. It might not match the reverse, but it d

Re: A bug, maybe?

2016-02-20 Thread Curtis Maurand
On 2/20/2016 1:46 PM, Viktor Dukhovni wrote: On Sat, Feb 20, 2016 at 01:37:39PM -0500, Curtis Maurand wrote: Nothing is chrooted. resolv.conf is world readable. Wietse's program returns a valid address. It might not match the reverse, but it did return an address. # ./getaddr delivery.mail

Re: A bug, maybe?

2016-02-20 Thread Viktor Dukhovni
On Sat, Feb 20, 2016 at 01:37:39PM -0500, Curtis Maurand wrote: > Nothing is chrooted. resolv.conf is world readable. Wietse's program > returns a valid address. It might not match the reverse, but it did return > an address. > # ./getaddr delivery.mailspamprotection.com > Hostname: deliv

Re: A bug, maybe?

2016-02-20 Thread Curtis Maurand
On 2/20/2016 12:17 PM, Viktor Dukhovni wrote: On Sat, Feb 20, 2016 at 11:40:09AM -0500, Curtis Maurand wrote: i just sent myself a test message from the client's system. Here is what I got. I immediately ran the lookups using dig. postfix can't seem to resolve things properly. Running Ubu

Re: A bug, maybe?

2016-02-20 Thread Viktor Dukhovni
On Sat, Feb 20, 2016 at 11:40:09AM -0500, Curtis Maurand wrote: > i just sent myself a test message from the client's system. Here is what I > got. I immediately ran the lookups using dig. postfix can't seem to > resolve things properly. Running Ubuntu Server 14.04 LTS with ispconfig > install

Re: A bug, maybe?

2016-02-20 Thread Wietse Venema
Curtis Maurand: > Feb 19 16:30:29 ispconfig postfix/smtpd[18437]: warning: hostname > delivery.mailspamprotection.com does not resolve to address > 108.163.243.188 The problem of testing with nslookup, dig, etc., is that they don't use the getaddrinfo() system library function that Postfix uses to

Re: A bug, maybe?

2016-02-20 Thread Curtis Maurand
On 2/20/2016 11:26 AM, Curtis Maurand wrote: On 2/20/2016 11:12 AM, Christian Kivalo wrote: On 2016-02-20 16:45, Curtis Maurand wrote: Not sure if I found something or not. A client tried to send email to one of my other addresses. The requisite portion of the main.cf follows at the end o

Re: A bug, maybe?

2016-02-20 Thread Curtis Maurand
On 2/20/2016 11:12 AM, Christian Kivalo wrote: On 2016-02-20 16:45, Curtis Maurand wrote: Not sure if I found something or not. A client tried to send email to one of my other addresses. The requisite portion of the main.cf follows at the end of the message. The logs are telling me: Feb 19

Re: A bug, maybe?

2016-02-20 Thread Christian Kivalo
On 2016-02-20 16:45, Curtis Maurand wrote: Not sure if I found something or not. A client tried to send email to one of my other addresses. The requisite portion of the main.cf follows at the end of the message. The logs are telling me: Feb 19 16:30:29 ispconfig postfix/smtpd[18437]: warning:

Re: A bug, maybe?

2016-02-20 Thread Viktor Dukhovni
On Sat, Feb 20, 2016 at 10:45:42AM -0500, Curtis Maurand wrote: > Feb 19 16:30:29 ispconfig postfix/smtpd[18437]: > warning: hostname delivery.mailspamprotection.com > does not resolve to address 108.163.243.188 > Feb 19 16:30:29 ispconfig postfix/smtpd[18437]: > connect from unknown[1

A bug, maybe?

2016-02-20 Thread Curtis Maurand
Not sure if I found something or not. A client tried to send email to one of my other addresses. The requisite portion of the main.cf follows at the end of the message. The logs are telling me: Feb 19 16:30:29 ispconfig postfix/smtpd[18437]: warning: hostname delivery.mailspamprotection.com