Re: badly broken mx record for bond.com

2012-08-02 Thread Viktor Dukhovni
On Thu, Aug 02, 2012 at 11:27:52AM -0400, Wietse Venema wrote: > > On 2 Aug 2012, at 14:17, Wietse Venema wrote: > > > > > The prime directive for Postfix is to deliver mail reliably without > > > sucking from a performance or human interface point of view, and > > > without granting unnecessary

Re: badly broken mx record for bond.com

2012-08-02 Thread Wietse Venema
Jim Reid: > On 2 Aug 2012, at 14:17, Wietse Venema wrote: > > > The prime directive for Postfix is to deliver mail reliably without > > sucking from a performance or human interface point of view, and > > without granting unnecessary privileges to random strangers. > > Too bad your prime directiv

Re: badly broken mx record for bond.com

2012-08-02 Thread Wietse Venema
Wietse: > If you don't like the result, use one of the following in > the SMTP daemon to block their mail: > > check_client_mx_access (ditto for helo, sender, recipient, etc.) > check_client_mx_access (ditto for helo, sender, recipient, etc.) [the second one should be check_mumble_ns_access, for

Re: badly broken mx record for bond.com

2012-08-02 Thread Wietse Venema
Jim Reid: > On 2 Aug 2012, at 10:44, Varadi Gabor wrote: > > > The log also shows that the "warning: numeric domain name in > > resource data of MX record for bond.com: 0.0.0.0" > > Yes, I saw that. This should have resulted in a hard error, not a > warning. If you don't like the result, use

Re: badly broken mx record for bond.com

2012-08-02 Thread Jim Reid
On 2 Aug 2012, at 10:44, Varadi Gabor wrote: The log also shows that the "warning: numeric domain name in resource data of MX record for bond.com: 0.0.0.0" Yes, I saw that. This should have resulted in a hard error, not a warning. I want solutions not only in this case in particular, but

Re: badly broken mx record for bond.com

2012-08-02 Thread Varadi Gabor
On Thu, Aug 02, 2012 at 10:18:42AM +0100, Jim Reid wrote: > First off, this is not a Postfix problem. The MX record for bond.com is > spectacularly broken. It's an epic fail. That's what needs to be fixed. I did not say that postfix would be a mistake :) The log also shows that the "warning: num

badly broken mx record for bond.com

2012-08-02 Thread Jim Reid
On 2 Aug 2012, at 08:38, Varadi Gabor wrote: Sorry because my English. No problem. It's *far* better than my Hungarian. :-) Besides, you've provided full, unedited information -- log entries, dig output, etc -- which makes it clear exactly what the problem is. If only everyone did that...