Send only configuration best practices?

What's the best configuration for a web server that does not receive mail but needs to send mail? Password resets. Bug ticket update notifications. That type of email. (Plus admin mail such as cron output to root. But I can ensure that is delivered to me and read.) But the host never needs to

Re: [EXTERNAL] Re: Forward mail and obey SPF and DKIM

On 9/16/20 6:18 AM, Nick Tait wrote: > Thank you. > I see "SPF: SOFTFAIL" in my gmail message. > > Authentication results: > spf=softfail (google.com : domain of transitioning some_user@sender_domain does not designate MY_IP_ADDR as permitted sender) > > While the message

Re: syn flood generated by a postfix transaction

Hi, just for the curious, we could solve it by using a rule on the bsd firewall lan to pass TCP using "synproxy". The mail  transaction passes and goes on quickly without generating the syn/ack flood.   Hope this is enough for any situation...   Gabriele     Sonicle S.r.l.  :  http://www.sonicle.

Re: Forward mail and obey SPF and DKIM

> Thank you. > I see "SPF: SOFTFAIL" in my gmail message. > > Authentication results: > spf=softfail (google.com : domain of transitioning some_user@sender_domain does not designate MY_IP_ADDR as permitted sender) > > While the message is not blocked, it is still not good to

Re: put message on HOLD based on sender & recipient

September 16, 2020 12:30 AM, "Wietse Venema" wrote: > Patrick Proniewski: > >> Hello, >> >> What would be the best way to hold an incoming email that match both >> criteria From=foo and To=bar? >> First I thought about header_checks with something like: >> >> if /^From:.*foo.*/ >> /^To:.*bar.

Re: put message on HOLD based on sender & recipient

September 15, 2020 11:52 PM, "Bill Cole" wrote: > On 15 Sep 2020, at 16:55, Patrick Proniewski wrote: > >> Hello, >> >> What would be the best way to hold an incoming email that match both > >> criteria From=foo and >> To=bar? >> First I thought about header_checks with something like: >> >>