Mailinglist Archive: opensuse (2831 mails)
| < Previous | Next > |
Re: [SLE] spamassassin and rbl checks in SuSE V9.2
- From: Sandy Drobic <suse-linux-e@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Jul 2006 18:28:16 +0200
- Message-id: <44B52320.9030707@xxxxxxxxxxxxxxxxxxxxxxx>
Peter Sutter wrote:
The reason is that RBL checks can only be done on the first Server that accepts Mails for your domain. In your case this is the Server of your provider. Unless you decide to accept Mail on your suse server, you don't need to bother with RBL checks.
RBL only checks the current IP of the client. In your case this would be fetchmail on localhost! A lot of mail originates from dynamic IPs, practically every private mail send by a mailclient. The relevant lookup though will only check the current ip of the client.
The basic understanding how smtp communication and restrictions work. You can't have fetchmail and RBLs both. Either you use fetchmail, accept all mail and discard or mark and deliver the mail, or you accept mails directly submitted to your server and then you can use RBLs, Postfix restrictions and all the luxury of your own smtp server.
You can't have the cake and eat it at the same time. (^-^)
Sandy
--
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
I am trying to get rbl filtering of my incoming mail. I tried to configure sendmail to do rbl checks, but since I dislike opening the smtp port on my router, I decided to use fetchmail to periodically poll my external mail sources, and use spamassassin for rbl checks.
Unfortunately this doe not work for me for some reason.
The reason is that RBL checks can only be done on the first Server that accepts Mails for your domain. In your case this is the Server of your provider. Unless you decide to accept Mail on your suse server, you don't need to bother with RBL checks.
spamassassin -D --lint reports:
debug: config: read file /usr/share/spamassassin/20_dnsbl_tests.cf
...
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.48
so I conclude that the rbl test are available as are the perl dns modules are available to spamassassin.
Yet mail messages originating from sources which are listed in sorbs as spam-sources, pass through, I never get any RCVD_IN_SORBS results, i.e. the following received header should trigger RCVD_IN_SORBS_DUL
RBL only checks the current IP of the client. In your case this would be fetchmail on localhost! A lot of mail originates from dynamic IPs, practically every private mail send by a mailclient. The relevant lookup though will only check the current ip of the client.
Received: from unknown (HELO keatingjones.com) (84.97.25.132)
by anchovy2.45ru.net.au with SMTP; 9 Jul 2006 13:36:23 -0000
because the dns reverse lookup returns a result
# nslookup 132.25.97.84.dnsbl.sorbs.net
Server: 192.168.1.186
Address: 192.168.1.186#53
Non-authoritative answer:
Name: 132.25.97.84.dnsbl.sorbs.net
Address: 127.0.0.10
What am I overlooking?
The basic understanding how smtp communication and restrictions work. You can't have fetchmail and RBLs both. Either you use fetchmail, accept all mail and discard or mark and deliver the mail, or you accept mails directly submitted to your server and then you can use RBLs, Postfix restrictions and all the luxury of your own smtp server.
You can't have the cake and eat it at the same time. (^-^)
Sandy
--
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
| < Previous | Next > |