Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2006-07-12 at 18:28 +0200, Sandy Drobic wrote:
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. (^-^)
That can't be completely true: I'm using fetchmail and my spamassassin is using some rbl tests and catching spam that way. Look at a report (edited to avoid false triggers - I hope):
The problem with those RBL tests is always which hop in the received lines they use to look up. Often they use the wrong one. Some people have complained that they were rejected because the received lines had a dynamic ip from the time when the user submitted the mail with smtp auth, and in the end they were forced to delete the received lines from the mails to get through. You could probably better write a little script to check the received lines, since you know which lines are from your server and then evaluate the correct line. The use of RBLs in Postfix though can only happen if you accept mails directly.
pts rule name description - ---- ---------------------- -------------------------------------------------- 0.9 URI_NOVOWEL URI: URI hostname has long non-vowel sequence 5.0 BAYES_99 BODY: Bayesian spam probability is 99 to 100% [score: 1.0000] 1.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [169.207.88.67 listed in dnsbl.sorbs.net] 1.0 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP [169.207.88.67 listed in combined.njabl.org]
Now, the question is which hop this ip was. (^-^)
1.6 URIBL_SBL Contains an URL listed in the SBL blocklist [URIs: emerseddm dot com] 4.1 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist [URIs: emerseddm dot com] 2.1 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist [URIs: emerseddm dot com] 3.0 URIBL_OB_SURBL Contains an URL listed in the OB SURBL blocklist [URIs: emerseddm dot com] 4.5 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist [URIs: emerseddm dot com]
Notice that the scoring is a bit unfair: one url is scoring several times for the same motive.
Notice also that I have downgraded some scores, like the one for dynamic addresses: after all, I use one myself.
Especially the sorbs dul list has stirred up some bad feedback due to their policy.
The thing is, the IP that SA checks is the one in the "Return-Path" header: <taxqlnsu at as14.nwbl1.wi.core.com>. The absurd thing is that it is not in fact a dynamic address:
cer@nimrodel:~> host as14.nwbl1.wi.core.com as14.nwbl1.wi.core.com has address 169.207.80.56 cer@nimrodel:~> host 169.207.80.56 56.80.207.169.in-addr.arpa domain name pointer as14.nwbl1.wi.core.com.
It has correct reverse DNS, can't be dynamic. But dnsbl.sorbs.net says it is.
sorbs doesn't care about reverse DNS records, they list blocks as dynamic that they figured are dynamic or which at some time have been reported as dynamic. If the use of that ip block has changed in the meantime it's just your bad luck. :-( Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com