On 8.03.2019 19:15, Viktor Dukhovni wrote:
On Mar 8, 2019, at 11:02 AM, Wietse Venema <wie...@porcupine.org> wrote:
Perhaps sender_dependent_default_transport_maps uses the same
null-sender lookup mechanism as other mappings. For example the
transport map has this note:
Note 1: the null recipient address is looked up as
$empty_address_recipient@$myhostname (default: mailer-daemon@hostname).
Yes, it looks like it is.
My concern was more about the OP's relay, it may simply refuse all bounces.
In which case the OP may want to configure a suitable double-bounce sender,
and test that double-bounce delivery works.
Actually, I have a problem which I am trying to solve. I have a server
with Postfix and Apache with a few WordPress websites. The 3rd party
smtp relay provider complains that there are some non-validated emails
coming to their server from my server. I have checked my maillog and
found that every now and then my server is trying to send mail from my
server. This mails originates from Apache through (I think) php mail.
Obviously, my server is compromised. I upgraded all the WordPress
instances and plugins. And removed plugins not needed. But, still my
server sends some mails to relay host.
Hoping to solve this problem, I wanted to block all the sender emails
not defined in sender_relay table. I will do what you advised here. But,
I know that this will also block apache sender eventually. In this case,
I will have another problem in my lap. Contact forms on my websites and
reporting emails generated by the server will stop working.
I don't know what to do. I would appreciate any advise from you.
Thanks.
