<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eino Tuominen wrote:
<blockquote cite="mid:48FD9F6E.7050608@utu.fi" type="cite">
<pre wrap="">Jeff Chan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
For these few days, I went over the top and ran an experiement to
greylist senders with bad helo strings using grossd. I did this
because I found many obvious spams slipped through the RBLs undetected
(as trusted). Those were the ones with bad helo strings, either with
non-ascii characters, illegal domain name characters, non-fully
qualified hostnames, or with IP addresses whether bracketed or not.
</pre>
</blockquote>
<pre wrap=""><!---->
Hi Jeff,
Sorry for a very late response...
I have now incorporated your piece of code in the new check_helo.c in
svn version.
This will be relased in version 1.1, which I plan to release next (with
the 1.0.2 patch release).
</pre>
</blockquote>
<br>
Is this configurable?<br>
What is the logic? I assume something like:<br>
<br>
if (<IP address SMTP client> on DNSBL) or (we_greylist_everything
turned on)<br>
then<br>
perform greylist action<br>
else<br>
if <bad helo/ehlo><br>
then<br>
perform greylist action<br>
else<br>
OK<br>
fi<br>
fi<br>
<br>
Or?<br>
<br>
/rolf<br>
<br>
<br>
</body>
</html>