That should do it, assuming you also have a line in your main configuration
file that says:
However, from the rDNS name, it looks like that sender could come from a huge
list of IPs. You might consider turning off the filter for the domain instead,
And it's always possible you found a bug. If you still can't make it work with
the _sender_ folder, let me know and I'll do some testing too.
For what it's worth -- tz.changeyourflight.com doesn't just have no MX records,
it has no DNS records at all. I don't see any way that return address could
-- Sam Clippinger
On May 5, 2017, at 3:24 AM, Quinn Comendant via spamdyke-users
> I've gotten this error:
> 2017-05-05 03:16:52.533029500 spamdyke: DENIED_SENDER_NO_MX from:
> bounces+1818979-7ef3-quinn=strangecode[.]c...@tz.changeyourflight.com to:
> quinn[@]strangecode[.]com origin_ip: 188.8.131.52 origin_rdns:
> o1678972x110.outbound-mail.sendgrid.net auth: (unknown) encryption: TLS
> reason: (empty)
> Indeed, "tz.changeyourflight.com" has no MX records.
> I have tried to apply a custom setting for this sender's IP address by adding
> a config file at:
> Then restarting qmail smtp with `qmailctl restart`.
> I've used this method successfully in the past for `reject-empty-rdns=0` and
> `reject-unresolvable-rdns=0`. However, it's not working for the
> DENIED_SENDER_NO_MX error. The sending error continues to occur.
> Have I set this up wrong?
> spamdyke-users mailing list
spamdyke-users mailing list