(To the list admins, this is a 3rd party software announcement, which I
believe to be relevant to Postfix users, but please let me know you
consider it as inappropriate use of this list)
For those who don't know it yet, Lightmeter Control Center is a web
based open source monitoring tool for P
post...@ptld.com:
> Without recompiling postfix, is there a way to get the PTR hostname
> warning to come after the connect message in the logs?
That would be wrong.
As a matter or principle, Postfix logs a warning for a bad condition
(for example client name unavailable), before doing somethin
Hello,
I just noticed this particular behaviour as I was trying to track down
some issues as apparently my mail server was bouncing legitimate emails
from a few senders (including some freebsd mailing lists and also
postfix-users as I discovered afterwards). This is on the FreeBSD port
of Pos
Timo Geusch:
> Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
> actually error codes and not indicators of allow/denylisting - in this
> case, their error is that I was querying via a public resolver, see link
> here: https://www.spamhaus.org/faq/section/DNSBL%20Usage#200
So
On 5/29/21 10:22 AM, Timo Geusch wrote:
> Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
> actually error codes and not indicators of allow/denylisting - in this
> case, their error is that I was querying via a public resolver, see link
> here: https://www.spamhaus.org/faq/sec
On 5/29/21 11:03 AM, Wietse Venema wrote:
Timo Geusch:
Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
actually error codes and not indicators of allow/denylisting - in this
case, their error is that I was querying via a public resolver, see link
here: https://www.spamhaus.org
On 5/29/21 11:40 AM, Phil Stracchino wrote:
On 5/29/21 10:22 AM, Timo Geusch wrote:
Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
actually error codes and not indicators of allow/denylisting - in this
case, their error is that I was querying via a public resolver, see link
Wietse Venema wrote:
IL Ka:
If you want to choose transport based on sender, you probably want
"sender_dependent_default_transport_maps"
http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps
It seems that this option doesn't support wildcards.
Yes it does. Use a
On Saturday, 29 May 2021 16:55, Timo Geusch wrote:
> On 5/29/21 11:03 AM, Wietse Venema wrote:
>
> > Timo Geusch:
> >
> > > Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
> > > actually error codes and not indicators of allow/denylisting - in this
> > > case, their error is tha
David Favor:
[ Charset ISO-8859-1 converted... ]
> Wietse Venema wrote:
> > IL Ka:
> >>>
> If you want to choose transport based on sender, you probably want
> "sender_dependent_default_transport_maps"
>
>
> >>> http://www.postfix.org/postconf.5.html#sender_dependent_default_tra
On Sat, May 29, 2021 at 11:55:02AM -0400, Timo Geusch wrote:
> On 5/29/21 11:03 AM, Wietse Venema wrote:
> > Timo Geusch:
> > > Based on zen.spamhaus.org's documentation 127.255.255.25[245] are
> > > actually error codes and not indicators of allow/denylisting - in this
> > > case, their error is t
Wietse Venema wrote:
David Favor:
[ Charset ISO-8859-1 converted... ]
Wietse Venema wrote:
IL Ka:
If you want to choose transport based on sender, you probably want
"sender_dependent_default_transport_maps"
http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps
It
On 5/28/2021 6:24 PM, post...@ptld.com wrote:
Without recompiling postfix, is there a way to get the PTR hostname
warning to come after the connect message in the logs?
Adding to the reply from Wietse, which I have to agree with:
On my Ubuntu 18 mail server, everything that postfix sends to sy
On Sat, May 29, 2021 at 11:30:51AM -0500, David Favor wrote:
> # cat /etc/postfix/sender_dependant_default_transport
> /.*@davidfavor.com/ :
> /.*@fixdeliver.com/ :
> /.*/ discard:
>
> 7) Sending message still allows random sending domains...
The transport table only selects a delivery channel,
According to Bastian Blank :
>> Already addressed it, however I figured it would be worth mentioning on here
>> as it seem to be a fairly recent change at SpamHaus's end.
>
>No, it is not a recent change. SpamHaus rejects requests via done
>public resolvers since a long time.
It is a fairly recen
On 5/29/21 2:19 PM, John Levine wrote:
According to Bastian Blank :
Already addressed it, however I figured it would be worth mentioning on here
as it seem to be a fairly recent change at SpamHaus's end.
No, it is not a recent change. SpamHaus rejects requests via done
public resolvers since a
On 05-29-2021 1:16 pm, Shawn Heisey wrote:
Adding to the reply from Wietse, which I have to agree with:
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 hostname needs to be checked if
it has ne
Viktor Dukhovni wrote:
On Sat, May 29, 2021 at 11:30:51AM -0500, David Favor wrote:
# cat /etc/postfix/sender_dependant_default_transport
/.*@davidfavor.com/ :
/.*@fixdeliver.com/ :
/.*/ discard:
7) Sending message still allows random sending domains...
The transport table only selects a del
David Favor:
[ Charset ISO-8859-1 converted... ]
> Viktor Dukhovni wrote:
> > On Sat, May 29, 2021 at 11:30:51AM -0500, David Favor wrote:
> >
> >> # cat /etc/postfix/sender_dependant_default_transport
> >> /.*@davidfavor.com/ :
> >> /.*@fixdeliver.com/ :
> >> /.*/ discard:
> >>
> >> 7) Sending me
Wietse Venema wrote:
David Favor:
[ Charset ISO-8859-1 converted... ]
Viktor Dukhovni wrote:
On Sat, May 29, 2021 at 11:30:51AM -0500, David Favor wrote:
# cat /etc/postfix/sender_dependant_default_transport
/.*@davidfavor.com/ :
/.*@fixdeliver.com/ :
/.*/ discard:
7) Sending message still a
20 matches
Mail list logo
