Re: writing own rbl rules

2014-08-28 Thread Reindl Harald
Am 29.08.2014 um 02:29 schrieb Karsten Bräckelmann: > On Fri, 2014-08-29 at 01:59 +0200, Reindl Harald wrote: > You can easily run RBL tests against IPs from within the local network > and treat them like any other sending SMTP client, by (a) excluding > them from the appropriate *_networks setti

Re: writing own rbl rules

2014-08-28 Thread Karsten Bräckelmann
On Fri, 2014-08-29 at 01:59 +0200, Reindl Harald wrote: > Am 29.08.2014 um 01:51 schrieb Karsten Bräckelmann: > > On Fri, 2014-08-29 at 01:06 +0200, Reindl Harald wrote: > > > the question was just "how can i enforce RBL tests inside the own LAN" > > > > RBL tests cannot be enforced. Internal and

Re: writing own rbl rules

2014-08-28 Thread Reindl Harald
Am 29.08.2014 um 01:51 schrieb Karsten Bräckelmann: > On Fri, 2014-08-29 at 01:06 +0200, Reindl Harald wrote: >> the question was just "how can i enforce RBL tests inside the own LAN" > >> the question was just "how can i enforce RBL tests inside the own LAN" > >> the question was just "how can

Re: writing own rbl rules

2014-08-28 Thread Karsten Bräckelmann
On Fri, 2014-08-29 at 01:06 +0200, Reindl Harald wrote: > the question was just "how can i enforce RBL tests inside the own LAN" > the question was just "how can i enforce RBL tests inside the own LAN" > the question was just "how can i enforce RBL tests inside the own LAN" RBL tests cannot be e

Re: writing own rbl rules

2014-08-28 Thread Reindl Harald
Am 29.08.2014 um 00:57 schrieb Karsten Bräckelmann: >> the simple answer to my question would have been "no, in no case SA does >> any RBL check if the client is from the same network range and there is >> no way to change that temporary even for development" [...] > > That would have been simpler

Re: writing own rbl rules

2014-08-28 Thread Karsten Bräckelmann
On Fri, 2014-08-29 at 00:22 +0200, Reindl Harald wrote: > the simple answer to my question would have been "no, in no case SA does > any RBL check if the client is from the same network range and there is > no way to change that temporary even for development" [...] That would have been simpler in

Re: writing own rbl rules

2014-08-28 Thread Reindl Harald
besides that the setup is now in production Am 27.08.2014 um 03:48 schrieb Karsten Bräckelmann: > Again: Craft your samples to match real-life (production) environment. > Do not configure or try to fake an environment that will not match > production later. It won't work. > > You want to configur

Re: writing own rbl rules

2014-08-26 Thread Karsten Bräckelmann
On Wed, 2014-08-27 at 03:01 +0200, Reindl Harald wrote: > > If it's internal, it's internal. There is a reason you are setting up > > lastexternal DNSxL rules. > > the intention is to handle the internal IP like it would be external Again: Craft your samples to match real-life (production) enviro

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 27.08.2014 um 02:24 schrieb Karsten Bräckelmann: > On Wed, 2014-08-27 at 01:08 +0200, Reindl Harald wrote: >> below the stdout/sterr of following script filtered for "dns" >> so the lists are asked, but the question remains why that >> don't happen from a IP in the same network > > Nope, no R

Re: writing own rbl rules

2014-08-26 Thread Karsten Bräckelmann
On Wed, 2014-08-27 at 01:08 +0200, Reindl Harald wrote: > below the stdout/sterr of following script filtered for "dns" > so the lists are asked, but the question remains why that > don't happen from a IP in the same network Nope, no RBL queries. See below. > in the meantime there are a lot of "c

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 22:23 schrieb Matthias Leisi: > On Tue, Aug 26, 2014 at 9:25 PM, Reindl Harald wrote: > >>> spamc -your_normal_spamc_options > >> are we really talking about the same? >> that won't involve the network > > You need a full message, include any Received: etc headers, as it > woul

Re: writing own rbl rules

2014-08-26 Thread Matthias Leisi
On Tue, Aug 26, 2014 at 9:25 PM, Reindl Harald wrote: >> spamc -your_normal_spamc_options > are we really talking about the same? > that won't involve the network You need a full message, include any Received: etc headers, as it would appear on your MTA when it would pass it on to spamc (or wha

Re: writing own rbl rules

2014-08-26 Thread Martin Gregorie
On Tue, 2014-08-26 at 21:25 +0200, Reindl Harald wrote: > Am 26.08.2014 um 21:08 schrieb Martin Gregorie: > > Under the same directory as spamass-milter run: > > > > spamc -your_normal_spamc_options > are we really talking about the same? > that won't involve the network > Of course it will.

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 21:08 schrieb Martin Gregorie: > On Tue, 2014-08-26 at 20:08 +0200, Reindl Harald wrote: >> Am 26.08.2014 um 18:11 schrieb Axb: >>> On 08/26/2014 05:42 PM, Reindl Harald wrote: they are *not* i sepecially added the following lines to prevent the automatic adding to "trus

Re: writing own rbl rules

2014-08-26 Thread John Wilcock
Le 26/08/2014 21:03, Reindl Harald a écrit : i just don't know how to do that with the setup and mailflow by just start "spamassassin -D dns" which runs the process but how to get the mail there? You need a copy of the message as a text file on your SA machine, then you simply run, from the co

Re: writing own rbl rules

2014-08-26 Thread Martin Gregorie
On Tue, 2014-08-26 at 20:08 +0200, Reindl Harald wrote: > > Am 26.08.2014 um 18:11 schrieb Axb: > > On 08/26/2014 05:42 PM, Reindl Harald wrote: > >> they are *not* i sepecially added the following lines > >> to prevent the automatic adding to "trusted_networks" > >> since the IP range is outside

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 20:29 schrieb Axb: > On 08/26/2014 08:08 PM, Reindl Harald wrote: >> >> Am 26.08.2014 um 18:11 schrieb Axb: >>> On 08/26/2014 05:42 PM, Reindl Harald wrote: they are *not* i sepecially added the following lines to prevent the automatic adding to "trusted_networks"

Re: writing own rbl rules

2014-08-26 Thread Axb
On 08/26/2014 08:08 PM, Reindl Harald wrote: Am 26.08.2014 um 18:11 schrieb Axb: On 08/26/2014 05:42 PM, Reindl Harald wrote: they are *not* i sepecially added the following lines to prevent the automatic adding to "trusted_networks" since the IP range is outside clear_trusted_networks trust

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 18:11 schrieb Axb: > On 08/26/2014 05:42 PM, Reindl Harald wrote: >> they are *not* i sepecially added the following lines >> to prevent the automatic adding to "trusted_networks" >> since the IP range is outside >> >> clear_trusted_networks >> trusted_networks 192.168.168.0/24 >

Re: writing own rbl rules

2014-08-26 Thread Axb
On 08/26/2014 05:42 PM, Reindl Harald wrote: they are*not* i sepecially added the following lines to prevent the automatic adding to "trusted_networks" since the IP range is outside clear_trusted_networks trusted_networks 192.168.168.0/24 there was no trust at all in the headers and no hint wh

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 17:30 schrieb Axb: > On 08/26/2014 05:25 PM, Reindl Harald wrote: >> Am 26.08.2014 um 17:18 schrieb Axb: >>> On 08/26/2014 04:28 PM, Reindl Harald wrote: header RCVD_IN_RP_TLDNS1 eval:check_rbl('tldns1-lastexternal', 'dnswl.thelounge.net.') describe RCVD_IN_RP_TL

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 17:18 schrieb Axb: > On 08/26/2014 04:28 PM, Reindl Harald wrote: >> header RCVD_IN_RP_TLDNS1 eval:check_rbl('tldns1-lastexternal', >> 'dnswl.thelounge.net.') >> describe RCVD_IN_RP_TLDNS1 Custom DNSBL/DNSWL >> tflags RCVD_IN_RP_TLDNS1 net >> scoreRCVD_IN_RP_TLDNS1 -5 >>

Re: writing own rbl rules

2014-08-26 Thread Axb
On 08/26/2014 05:25 PM, Reindl Harald wrote: Am 26.08.2014 um 17:18 schrieb Axb: On 08/26/2014 04:28 PM, Reindl Harald wrote: header RCVD_IN_RP_TLDNS1 eval:check_rbl('tldns1-lastexternal', 'dnswl.thelounge.net.') describe RCVD_IN_RP_TLDNS1 Custom DNSBL/DNSWL tflags RCVD_IN_RP_TLDNS1 net s

Re: writing own rbl rules

2014-08-26 Thread Axb
On 08/26/2014 04:28 PM, Reindl Harald wrote: Am 26.08.2014 um 15:54 schrieb Axb: On 08/26/2014 03:00 PM, Reindl Harald wrote: Am 26.08.2014 um 14:25 schrieb Joe Quinn: On 8/26/2014 8:04 AM, Reindl Harald wrote: sadly the Wiki don't refer to check_rbl() https://wiki.apache.org/spamassassin/Wr

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 15:54 schrieb Axb: > On 08/26/2014 03:00 PM, Reindl Harald wrote: >> Am 26.08.2014 um 14:25 schrieb Joe Quinn: >>> On 8/26/2014 8:04 AM, Reindl Harald wrote: sadly the Wiki don't refer to check_rbl() https://wiki.apache.org/spamassassin/WritingRules >>> You can use

Re: writing own rbl rules

2014-08-26 Thread Axb
On 08/26/2014 03:00 PM, Reindl Harald wrote: Am 26.08.2014 um 14:25 schrieb Joe Quinn: On 8/26/2014 8:04 AM, Reindl Harald wrote: i am tyring to write own RBL rules for blacklisting and especially whitelisting using internal DNSBL/DNSWL but my first try results in warnings at startup sadly t

Re: writing own rbl rules

2014-08-26 Thread Reindl Harald
Am 26.08.2014 um 14:25 schrieb Joe Quinn: > On 8/26/2014 8:04 AM, Reindl Harald wrote: >> i am tyring to write own RBL rules for blacklisting and >> especially whitelisting using internal DNSBL/DNSWL but >> my first try results in warnings at startup >> >> sadly the Wiki don't refer to check_rbl(

Re: writing own rbl rules

2014-08-26 Thread Joe Quinn
On 8/26/2014 8:04 AM, Reindl Harald wrote: Hi i am tyring to write own RBL rules for blacklisting and especially whitelisting using internal DNSBL/DNSWL but my first try results in warnings at startup sadly the Wiki don't refer to check_rbl() https://wiki.apache.org/spamassassin/WritingRules i

writing own rbl rules

2014-08-26 Thread Reindl Harald
Hi i am tyring to write own RBL rules for blacklisting and especially whitelisting using internal DNSBL/DNSWL but my first try results in warnings at startup sadly the Wiki don't refer to check_rbl() https://wiki.apache.org/spamassassin/WritingRules ifplugin Mail::SpamAssassin::Plugin::DNSEval