Skip to main content
giovinco_06
New Member
November 21, 2010
Question

HELO/EHLO domain is invalid

  • November 21, 2010
  • 6 replies
  • 12734 views
* A problem description I can' t receive the email from the domain catur.com and I got this error report at my customer site => < mail00.ltl.co.id #5.0.0 smtp; 5.1.0 - Unknown address error 554-' 5.7.1 This message has been blocked because the HELO/EHLO domain is invalid.' (delivery attempts: 0)> * A network diagram with the IP addressing clearly indicated Internet <=> Firewall <=> mail Server Anybody knows how to avoid this problem, since the email is not spam. I already try to make some whitelist, but it didn' t work out.. Fortigate still recognizes it as a spam.. thanks, aboe

    6 replies

    Carl_Wallmark
    New Member
    November 21, 2010
    try to uncheck the ehlo check in your spam profile. or else you have invalid domain settings, but not everyone follows the rfc standard regarding ehlo/helo.
    giovinco_06
    New Member
    November 22, 2010
    Dear Selective, Thanks, I already uncheck for HELO DNS check. And i can receive the email. But i must sacrifice that my servers are attacked with a lot of spams. Maybe i will try to make BLfor email filter. thanks a lot bro
    discoveryit
    New Member
    November 22, 2010
    config spamfilter dnsbl edit 1 config entries edit 1 set action reject set server " zen.spamhaus.org" next edit 2 set action reject set server " bl.spamcop.net" next end set name " BlackList" next end also for MR2 config spamfilter profile edit " your spam profile" set spam-rbl-table 1
    giovinco_06
    New Member
    November 23, 2010
    thanks discovery, I' m quite frustrated because my servers still attacked by spammers from hinet.net I will try to edit the DNSBL from CLI using your source code. Hopefully it will work GBU, -aboe-
    giovinco_06
    New Member
    November 25, 2010
    Dear Discovery Thanks for your tips, In couple of days ago, I monitored the traffic, and it really worked. All spams are dissapear now. May I ask for one more question, Do the SPAM problem also related with my " SMTP incoming" policy ? In my " SMTP incoming" mail policy, I checked the NAT. I read couple of old threads, it said that, NAT should not be checked for SMTP incoming. thanks,
    ede_pfau
    SuperUser
    SuperUser
    November 25, 2010
    If you check the NAT option on an incoming policy, the source IP of the internet host will be replaced by the IP of the external interface of your Fortigate (usually wan1). If the spam filter is setup to check the source IP against an IP blacklist (DNSRBL) then it will only check your external IP in every incoming mail against the list...this effectively disables the IP spam check.