Thanks Greyhat. I'm already doing that. The domain that's listed in senderbase is in the white sender file, preceded with a \b with the dots escaped \.
I do have ForceRBL enabled for early DNSBL checks. Is >THAT< the problem? ValidateRBL is set to score with 50 as a threshold (the same score that rejects for us). I don't even see that senderbase is running for these. (this isn't urgent, it's just an annoyance) On Thu, Oct 8, 2015 at 11:32 AM, Grayhat <gray...@gmx.net> wrote: > :: On Thu, 8 Oct 2015 11:23:49 -0400 > :: <CALhpkAmtwqyPRS5HvCPkWVtjx4EOP6o==U9O8=gvg9n2vwa...@mail.gmail.com> > :: K Post <nntp.p...@gmail.com> wrote: > > > and for clarification, it looks like the organization sends from > > something like 98 different IP's that I know about - I'm sure there > > are others - and some of them are blacklisted. > > > > If I could skip dnsbl either using a wildcard reverse dns match for > > the server, say *.thesenderdomain.com or matching the domain of the > > from line, that would allow me to easily let these through without > > constantly updating norbl. > > you may use the senderbase/whois query to retrieve the IP owner and > then whitelist it using the name (or a matching regexp) > > > ------------------------------------------------------------------------------ > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test >
------------------------------------------------------------------------------
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
