Scott, does IMail do it's ip4r checking after the whole message is received and the connection terminated or does check on the HELO/EHLO and send an error code back to the remote server?
IMail v8 runs the spam tests after the whole E-mail is received. Each ip4r test is run one after another (Declude instead runs the ip4r tests in parallel, sending all the queries at the same time, then awaiting the results).
If it does that latter, the remote timeout settings may be a concern. I have been tracking the tarpitting features of our gateway and found that a lot of servers time out at 30 seconds, and more at 60.
FWIW, the original teergrubing concept was designed for ultra-long (hours to days) delays that all mailservers should be able to handle. Rather than simply waiting X seconds, it would use multi-line responses, waiting X seconds between each one. For example:
> RCPT TO: <[EMAIL PROTECTED]>
< 220-OK, you can send to [EMAIL PROTECTED] But you will have to
[25 second delay]
< 220-wait and
[25 second delay]
< 220-wait and
...
< 220 wait for a very long time! Glad that's over!
> DATA
...This allows you to keep the connection open for days if needed (and it has been done for days).
The 30- or 60-second timeout is very short, though, and against RFC2821 (which specifies 2-5 minutes as the "SHOULD" minimum for the various commands).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
