Tony Finch wrote:
The only safe thing to do with HELO is to examine it for properties that
definitely indicate that the software at the other end is malware.
Misconfiguration does not imply malice! Our checks are slightly more
aggressive than those recommended by others on this list (particularly the
all-numeric check), but they seem to be pretty reliable.
deny
message = Please use your name when saying HELO (not
$sender_helo_name)
condition = ${if or{{ eq{$ACL_HELO}{bad} } \
{ eq{$sender_helo_name}{$local_part} } \
{ match{$sender_helo_name}{^[0-9.-]+\$} } \
{ match{$sender_helo_name}{\N[.][.]|.{55}\N} } \
{ match_domain{$sender_helo_name}{+our_domains} }}
}
set ACL_HELO = bad
What's ACL_HELO used for? It is to short-circuiting the string
comparisons for subsequent RCPT's on the same connection?
- Marc
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/