On Sun, May 30, 2021 at 12:04:41PM -0400, Bill Cole wrote:
> It's named collate.pl, included in the Postfix source distribution:
>
> sc1:bill$ cat postfix-3.6.0/auxiliary/collate/README
> This script, by Viktor Dukhovni, untangles a Postfix logfile and
> groups the records one "
On 2021-05-29 at 10:22:23 UTC-0400 (Sat, 29 May 2021 10:22:23 -0400)
Timo Geusch
is rumored to have said:
The fix/workaround in my case is relatively easy as I mostly need to
update the configuration for my local DNS server. That said, I'm not
sure if postscreen should treat this kind of error
On 2021-05-30 at 09:32:03 UTC-0400 (Sun, 30 May 2021 15:32:03 +0200)
Matus UHLAR - fantomas
is rumored to have said:
On 05-29-2021 1:16 pm, Shawn Heisey wrote:
Adding to the reply from Wietse, which I have to agree with:
On 29.05.21 16:40, post...@ptld.com wrote:
I was just assuming that a c
On 05-29-2021 1:16 pm, Shawn Heisey wrote:
Adding to the reply from Wietse, which I have to agree with:
On 29.05.21 16:40, post...@ptld.com wrote:
I was just assuming that a connection happens first before postfix
could know if the PTR resolves or not.
Otherwise how does postfix know a client
On 30/05/2021 12:47, Laura Smith wrote:
It is a fairly recent change, perhaps a year ago, that they return the .254 and
.255
codes rather than just ignoring the request, as a hint that you need to fix your
configuration.
Seems the change is dated 11/2/2021
(https://www.spamhaus.org/news/ar
> It is a fairly recent change, perhaps a year ago, that they return the .254
> and .255
> codes rather than just ignoring the request, as a hint that you need to fix
> your
> configuration.
>
>
Seems the change is dated 11/2/2021
(https://www.spamhaus.org/news/article/807/using-our-public-mi
