I noticed something in our mail logs that I thought was unusual.
What does it mean when smtpd reports a NOQUEUE without any kind of
reject: reason? All that's there is the client.
Aug 5 17:42:58 b1 postfix/smtpd[18503]: NOQUEUE:
client=a26-70.smtp-out.us-west-2.amazonses.com[54.240.26.70]
Aug
On Tue, Sep 29, 2020 at 6:32 PM Viktor Dukhovni
wrote:
> There is perhaps a documentation gap here. The fact that one
> check_mumble_mx_accesss performs table lookups not only on the MX host
> names, but also on their A/ addresses does not appear to be
> documented. The OP might have had
On Tue, Sep 29, 2020 at 3:33 PM Wietse Venema wrote:
> Then use check_recipient_mx_acces?
Yes, after some pretty thorough testing, check_recipient_mx_access
seems to be the perfect fix for our situation. The message gets
refused and the MUA gets a 554 error message.
For reference here are the
On Tue, Sep 29, 2020 at 2:15 PM Wietse Venema wrote:
> One alternative is to set reject_unverified_recipient
Thanks, I will give this a shot and see if it helps our situation.
> Alternatively, if the IP address range is known, check_sender_mx_access
> will control access by MX record (or A
Hello,
We know that a certain IP range contains no MTA's, but hosts websites
for a lot of domains that have no email service, i.e., those domains
have A records in that range but no MX records at all.
Our Postfix server regularly receives messages over MSA where the
sender and recipient
