>1. The documentation says "You can define as many different IP blacklists as
>you like, ..." and I'm taking it at its word. As a practical matter, has
>anyone noticed an IP address file size where performance seems to degrade?
>This morning, I think I saw a couple of messages in my spam hold directory
>from over the weekend that came from addresses I've already blacklisted.
Although we haven't run performance tests on the blacklists, you should be
able to have a very large number of them before performance becomes an
issue. I would expect you should be able to easily have hundreds or
several thousand IPs listed.
>2. Where does the IP blacklist get the IP address to test? From the message
>header, or the message ID, or the SMTP envelope, or from somewhere else?
Declude JunkMail uses the IP address of the remote mail server for the IP
blacklists.
By default, it will get this from the first Received: header of the E-mail
(the one that IMail adds, which is a trusted header). It's possible that
this may change in certain situations, such as if you use the IPBYPASS or
HOP options (for example, if you have it set up so that Declude JunkMail
will bypass a backup mail server, the IP blacklist will look at the IP
address that connected to your backup mail server instead).
-Scott
---
[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". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
