On Mon, 25 Oct 2021 12:36:35 -0400 (EDT),
Wietse Venema wrote :
> This would require a new setting, for example to make smtp_bind_address
> failures a retryable error.
>
> smtp_bind_address_failure_action = warn (or defer)
>
> warn: current behavior
> defer: treat as a faiilure to connect
This
On 25/10/21 2:59 pm, Thomas Anderson wrote:
Here is a clean email:
Received: from example.net (unknown [192.168.1.10])
by mail.example.com (Postfix) with ESMTPSA id D7C3F1980059
for; Mon, 25 Oct 2021 03:42:29 +0200 (CEST)
Here is a non-clean email:
Received: by mail.example.com
Benny Pedersen:
> On 2021-10-25 07:11, Thomas Anderson wrote:
> > The IP it came from was outside my network.
>
> you can reject all evevelope senders if its claims its your domain in
> port 25, you will never send it there, never as never, spf is just a
> global world protection not needed for
Vincent Pelletier:
> I would rather postfix just stop sending emails altogether in such case,
> than send them from an unexpected ip: a delay is preferable to me to
> uncertainty as to how the emails were processed by recipient SMTPs.
>
> Is there something else I should set so postfix stops falli
On 2021-10-25 07:11, Thomas Anderson wrote:
The IP it came from was outside my network.
you can reject all evevelope senders if its claims its your domain in
port 25, you will never send it there, never as never, spf is just a
global world protection not needed for postfix to make thar policy
On Mon, Oct 25, 2021 at 09:35:35AM +, Vincent Pelletier wrote:
> I would rather postfix just stop sending emails altogether in such
> case, than send them from an unexpected ip: a delay is preferable to
> me to uncertainty as to how the emails were processed by recipient
> SMTPs.
>
> Is there
On 25/10/2021 11:35, Vincent Pelletier wrote:
I would rather postfix just stop sending emails altogether in such case,
than send them from an unexpected ip: a delay is preferable to me to
uncertainty as to how the emails were processed by recipient SMTPs.
As a categorical prevention of postfix
Hello,
I have a server with multiple IPv4 routes to the internet (multipath
over tunnels, plus the default route). The multipath route is picked for
outgoing connections based on the IP the client socket is bound to:
ip rule from lookup
ip route add table default nexthop via ... [nexthop vi
