Re: Access table lookup not as expected

2016-12-23 Thread John Fawcett
ignore the previous message it was sent in the wrong thread, apologies for the noise.

Re: Access table lookup not as expected

2016-12-23 Thread John Fawcett
On 12/23/2016 05:29 PM, John Fawcett wrote: > On 12/23/2016 03:34 PM, Dominic Raferd wrote: >> On 23/12/2016 14:27, John Fawcett wrote: >>> On 12/23/2016 03:13 PM, Dominic Raferd wrote: Obviously I am being thick but can someone explain why this does not work as I would expect. Basically

Re: Access table lookup not as expected

2016-12-23 Thread John Fawcett
On 12/23/2016 03:34 PM, Dominic Raferd wrote: > On 23/12/2016 14:27, John Fawcett wrote: >> On 12/23/2016 03:13 PM, Dominic Raferd wrote: >>> Obviously I am being thick but can someone explain why this does not >>> work as I would expect. Basically email addresses are not matching >>> against domai

Re: Access table lookup not as expected

2016-12-23 Thread Dominic Raferd
On 23/12/2016 14:27, John Fawcett wrote: On 12/23/2016 03:13 PM, Dominic Raferd wrote: Obviously I am being thick but can someone explain why this does not work as I would expect. Basically email addresses are not matching against domain names in a hashed database: $ postconf|grep "^parent_doma

Re: Access table lookup not as expected

2016-12-23 Thread John Fawcett
On 12/23/2016 03:13 PM, Dominic Raferd wrote: > Obviously I am being thick but can someone explain why this does not > work as I would expect. Basically email addresses are not matching > against domain names in a hashed database: > > $ postconf|grep "^parent_domain_matches_subdomains.*smtpd_access