Ben's notes

Linux, Unix, network, radio...

User Tools

Site Tools

Trace:
iredmail_helo_reject

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
iredmail_helo_reject [2015/04/09 11:26] – [iRedMail - helo reject] adminiredmail_helo_reject [2015/04/09 11:55] – [iRedMail - helo reject] admin
Line 6: Line 6:
 //Helo command rejected: ACCESS DENIED. Your email was rejected because the sending mail server does not identify itself correctly (.local);// //Helo command rejected: ACCESS DENIED. Your email was rejected because the sending mail server does not identify itself correctly (.local);//
  
 +  * Edit /etc/postfix/helo_access.pcre if needed.
 +  * Restart postfix.
  
  
 +__Quote from forum:__
  
 It means your client's MTA uses a FQDN hostname which ends with '.local' as HELO identity. It means your client's MTA uses a FQDN hostname which ends with '.local' as HELO identity.
Line 14: Line 17:
 You have two solutions: You have two solutions:
  
-1) Ask your client to change their HELO identity which sent by MTA to a valid one. +  * Ask your client to change their HELO identity which sent by MTA to a valid one. 
-2) Remove this HELO check rule on YOUR server, in file /etc/postfix/helo_access.pcre.+  * Remove this HELO check rule on YOUR server, in file /etc/postfix/helo_access.pcre.
  
 Personally, i suggest you try #1 first. Personally, i suggest you try #1 first.
  
iredmail_helo_reject.txt · Last modified: 2021/10/09 15:14 by 127.0.0.1