Silmar, the reason your RBL lookup was wrong is you forgot to reverse
your IP address. So if your IP is 200.181.255.20, your lookup should be
as follows:
nslookup -q=txt 20.255.181.200.country-rirdata.dnsiplists.completewhois.com
Non-authoritative answer:
20.255.181.200.country-rirdata.dnsiplists.completewhois.com
text = "BR - Brazil"
/\---/\ Eric J Fox
/ o o \ Small Business Computer Support
\.\ /./ in the Phoenix Metropolitan Area
\@/ http://www.bsdsystems.com/support/
Silmar A. Marca wrote:
Im use RBL only to add Headers mark. In my clause i verify the "heloname", and
"rbl". If all is set, the Subject are changed to SPAM. I verify spamassassin
marks (i have soft and manual clauses).
Many databases are inconsistent. For example:
nslookup -query=TXT 200.181.255.20.country-rirdata.dnsiplists.completewhois.com
200.181.255.20.country-rirdata.dnsiplists.completewhois.com text = "US -
United States"
My ip is 200.181.255.20 and I not in US - United States, but in Brasil, City of
Iguassu Falls/Itaipu (Foz do Iguaçu).
part of system_filter:
#Spam HEADER spam para piores casos (nao pessoais)
if not personal then
if $h_X-Spam-Report: is not "" then
headers add "New-Subject: [SPAM]: $h_subject:"
headers remove subject
headers add "Subject: $h_new-subject:"
headers remove new-subject
#Spam HEADER spam para piores casos
elif $h_X-HLO-Warning: is not "" and $h_X-RBL-Warning: is not "" then
headers add "New-Subject: [SPAM]: $h_subject:"
headers remove subject
headers add "Subject: $h_new-subject:"
headers remove new-subject
endif
endif
Cordialmente, Silmar A. Marca
------------------------------------------------------------
Se algo nao lhe faz mal (fisico, moral ou psicologicamente),
experimente! O maximo e voce perder tempo! E tempo, e
o que voce tem a vida toda pra perder.....
Mais vale um instante de prazer que uma eternidade futil!
------------------------------------------------------------
Citando Mar Matthias Darin <[EMAIL PROTECTED]>:
Hello,
I have read this dabate over the real time black list and have this to say
about them... This is my approach as a server administrator and from the
stand point of having my domain blocked because my "neighbors" didn't "play"
nice.
I use the warn clause as follows at the server level:
To identify the sending country, I use:
warn message = X-Location: $dnslist_text
dnslists = country-rirdata.dnsiplists.completewhois.com
to identify blacklisted entries, I use:
warn condition = ${lookup
{${lc:$sender_helo_name}}lsearch{/usr/exim/MyIP}{no}{yes}}
condition = ${lookup
{${lc:$sender_host_address}}lsearch{/usr/exim/MyIP}{no}{yes}}
dnslists = abuse.rfc-ignorant.org
message = X-BlackList: Listed in
$dnslist_domain/$dnslist_text
I repeat this for ~135 different RBLs... Overkill perhaps, but the more
information I can provide my users, the better their choices will be. My
experience with using deny with RBLs is an automatic loss of 10% good mail.
on my personal account, I filter anything and everything to the max. This
gives me all my mail, and I don't get all the trash... I've educated all my
users to do the same. Its an effective and effecient way of getting the
best of both worlds: the good mail and no spam. My server handles anywhere
from 25,000 to 1 million emails a day.
My official opinion of RBLs: They have their plaace if used wisely, but
they are usually used in the worst ways. Often, they block large groups of
innocent people suffer from there misuse and even when you try to get
innocent domains removed from them, the respose is usually, "tough [EMAIL
PROTECTED]" or
"Thats your problem". This is where RBL owners truely fail in their goals
and where RBLs tend to fail the most in general.
--
## 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/
