> On Jan 5, 2019, at 10:03 PM, Lefteris Tsintjelis wrote:
>
> The remote servers of yahoo is mostly the problem. I rarely see this issue
> with any other servers but it usually applies to the whole domain whenever I
> see it, possibly because of their broken SMTP firewalls.
For destination-dom
On 6/1/2019 4:48 π.μ., John Fawcett wrote:
Only thing is that you'll have to specify ip addresses not domain names,
since dns lookups are not available for these maps.
The remote servers of yahoo is mostly the problem. I rarely see this
issue with any other servers but it usually applies to th
On 06/01/2019 03:24, Lefteris Tsintjelis wrote:
> Is there a possible way to turn off command pipelining completely for
> a whole domain based on DNS? The pipelining-firewalling of yahoo.com
> seems to be broken quite often.
>
> Something like:
>
> yahoo.com pipelining
I think you're looking fo
Lefteris Tsintjelis skrev den 2019-01-06 03:24:
Is there a possible way to turn off command pipelining completely for
a whole domain based on DNS? The pipelining-firewalling of yahoo.com
seems to be broken quite often.
Something like:
yahoo.com pipelining
no logs, no problem
:)
Is there a possible way to turn off command pipelining completely for a
whole domain based on DNS? The pipelining-firewalling of yahoo.com seems
to be broken quite often.
Something like:
yahoo.com pipelining
