On 11 January 2017 at 00:29, Wietse Venema wrote:
> Dominic Raferd:
>> On 10 January 2017 at 14:41, Wietse Venema wrote:
>> > Dominic Raferd:
>> >> # Example 1: response from gmail at end of smtp transmission is
>> >> checked using dns_filter_lookup - as intended, and not found - as
>> >
>> > $ p
Dominic Raferd:
> On 10 January 2017 at 14:41, Wietse Venema wrote:
> > Dominic Raferd:
> >> # Example 1: response from gmail at end of smtp transmission is
> >> checked using dns_filter_lookup - as intended, and not found - as
> >
> > $ postconf dns_filter_lookup
> > postconf: warning: dns_filter
On 09/01/17 21:06, @lbutlr wrote:
> 640K RAM ought to be enough for everybody.
>> No even similar. The address space for 128bit is in the general neighborhood
>> of the number of atoms in the universe.
> Sorry, that's 256 bits. 128 bits is the number of stars in
> 100,000,000,000,000,000 universe
On 10 January 2017 at 14:41, Wietse Venema wrote:
> Dominic Raferd:
>> # Example 1: response from gmail at end of smtp transmission is
>> checked using dns_filter_lookup - as intended, and not found - as
>
> $ postconf dns_filter_lookup
> postconf: warning: dns_filter_lookup: unknown parameter
>
>
Dominic Raferd:
> # Example 1: response from gmail at end of smtp transmission is
> checked using dns_filter_lookup - as intended, and not found - as
$ postconf dns_filter_lookup
postconf: warning: dns_filter_lookup: unknown parameter
No surprise, then, that nothing is matched.
To cite the mail
I am puzzling over why postfix fails to pass a response from gmail at
the end of an outgoing transmission through to
smtp_delivery_status_filter.
I am trying to trap a transient failure code response from gmail and
replace it with a permanent code and to do this I am using
smtp_delivery_status_fil
