a.16bit.sysop at gmail.com
Sat Feb 8 11:41:28 UTC 2020
Thanks, I think that is postscreen. I tried changing postscreen greet
action to enforce instead of drop and still got MX_INVALID
Have tried turning off postscreen and will try again later as now rspamd
has MX_INVALID cached
On Sat, 8 Feb 2020, 09:16 Alexander Moisseev via Users, <
users at lists.rspamd.com> wrote:
> 07.02.2020 23:23, Duncan Bellamy пишет:
> > Hi,
> > I have just upgraded to rspamd 2.3 and have been checking out the
> results history and noticed when I send mail to my rspamd server from
> another domain (denkimushi.com <http://denkimushi.com/>) I get
> MX_INVALID, I have checked the mx and compared it to ones that pass and it
> looks the same. Namecheap can’t find any problems with the mx record
> > I changed to the banner in postfix to just "$myhostname ESMTP
> $mail_name” but this didn’t help either.
> > I have postscreen enabled, but it uses the same banner.
> > I can’t seem to get a valid mx status from rspamd.
> > Thanks,
> > Duncan
> Something is wrong with the sender MTA (or firewall). I am getting double
> greeting from it.
> # telnet vikavolt.denkimushi.com 25
> Trying 126.96.36.199...
> Connected to vikavolt.denkimushi.com.
> Escape character is '^]'.
> 220-vikavolt.denkimushi.com ESMTP Postfix
> 220 vikavolt.denkimushi.com ESMTP Postfix
> 221 2.0.0 Bye
> Connection closed by foreign host.
> Users mailing list
> Users at lists.rspamd.com
More information about the Users