Hi Guys!
This thread was only just brought to our attention, and the thread is now
several levels deep and a bit old, so if you can help me out with letting me
know what the outstanding issues are, I'd really appreciate it.
As best as I can tell from reading through the thread online, there a
On 9/16/2017 4:36 PM, Chris wrote:
> I'm also seeing issues with ISIPP which is in 20_dnsbl_tests.cf. I've
> attached the message I sent them as well as their reply. Another issue I
> noticed with ISIPP is Sep 16 12:09:38 localhost named[1284]: host unreachable
> resolving 'ns1.ns.isipp.co
On Thu, 2017-09-21 at 11:58 +0100, Martin Gregorie wrote:
> On Wed, 2017-09-20 at 19:39 -0500, Chris wrote:
> >
> > It was installed by default when upgrading from 14.04LTS to
> > 16.04LTS
> >
> Then it may be best to just leave it there.
>
> >
> > I have stopped Network Manager. I've not disab
On Wed, 2017-09-20 at 19:39 -0500, Chris wrote:
> It was installed by default when upgrading from 14.04LTS to 16.04LTS
>
Then it may be best to just leave it there.
> I have stopped Network Manager. I've not disabled or removed it yet
> as I'm watching to see how named does the queries now.
>
I
On Wed, 2017-09-20 at 15:22 -0700, Ian Zimmerman wrote:
> On 2017-09-20 17:02, Chris wrote:
>
> >
> > So, IIUC it would be a good idea to remove the resolv.conf symlink
> > in
> > /run/resolvconf ?
> Definitely _not_ a good idea while the resolvconf package is
> installed.
>
> What I meant was r
On Wed, 2017-09-20 at 19:05 +0100, Martin Gregorie wrote:
> On Wed, 2017-09-20 at 08:48 -0500, Chris wrote:
> >
> > On Wed, 2017-09-20 at 11:15 +0100, Martin Gregorie wrote:
> > >
> > > On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> > > >
> > > >
> > > > Hi Martin, here's what I see:
> > > >
On 2017-09-20 17:02, Chris wrote:
> So, IIUC it would be a good idea to remove the resolv.conf symlink in
> /run/resolvconf ?
Definitely _not_ a good idea while the resolvconf package is installed.
What I meant was remove the package first, then clean up.
--
Please don't Cc: me privately on ma
On Wed, 2017-09-20 at 08:01 -0700, Ian Zimmerman wrote:
> On 2017-09-20 11:15, Martin Gregorie wrote:
>
> >
> > I don't know why you'd want to do that since you should be running
> > named instead of dnsmasq.
> >
> > Delete the version you just installed via the apt package manager
> > and
> > d
On Wed, 2017-09-20 at 08:01 -0700, Ian Zimmerman wrote:
> Finally (and getting really OT), it helps to keep relevant /etc files
> under version control, so you know when the system helpfully shifts
> the ground under you.
>
Really good advice.
I keep a copy of all the configuration files I've man
On Wed, 2017-09-20 at 08:48 -0500, Chris wrote:
> On Wed, 2017-09-20 at 11:15 +0100, Martin Gregorie wrote:
> > On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> > >
> > > Hi Martin, here's what I see:
> > >
> > > sudo systemctl status dnsmasq
> > > [sudo] password for chris:
> > > ● dnsmasq.ser
On 20 Sep 2017, at 9:48, Chris wrote:
> From the locate command I found these - https://pastebin.com/ECjZGX1M
AHA!
Apparently Ubuntu (and Debian?) has a package called "dnsmasq-base" which is
installed as a dependency of libvirt, which manages it independently and
autocratically...
2 maybe u
On 2017-09-20 11:15, Martin Gregorie wrote:
> I don't know why you'd want to do that since you should be running
> named instead of dnsmasq.
>
> Delete the version you just installed via the apt package manager and
> do a search and destroy mission to get rid of both the other copy of
> it and th
On Tue, 2017-09-19 at 21:32 -0700, Ian Zimmerman wrote:
> On 2017-09-19 19:53, David B Funk wrote:
>
> >
> > So now you have -two- dnsmasq kits, one installed by "apt" and
> > managed
> > thru the "systemctl" tools, and another one that somebody put there
> > which is outside the realm of "apt" &
On Tue, 2017-09-19 at 23:04 -0400, Bill Cole wrote:
> On 19 Sep 2017, at 22:36, Chris wrote:
>
> >
> > On Wed, 2017-09-20 at 04:31 +0200, Reindl Harald wrote:
> > >
> > >
> > > Am 20.09.2017 um 02:32 schrieb Chris:
> > > >
> > > >
> > > > I then installed dnsmasq (apparently it wasn't install
On Wed, 2017-09-20 at 11:15 +0100, Martin Gregorie wrote:
> On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> >
> > Hi Martin, here's what I see:
> >
> > sudo systemctl status dnsmasq
> > [sudo] password for chris:
> > ● dnsmasq.service
> > Loaded: not-found (Reason: No such file or directory
On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> Hi Martin, here's what I see:
>
> sudo systemctl status dnsmasq
> [sudo] password for chris:
> ● dnsmasq.service
> Loaded: not-found (Reason: No such file or directory)
> Active: inactive (dead)
> chris@localhost:~$ sudo systemctl enable dns
On 2017-09-19 19:53, David B Funk wrote:
> So now you have -two- dnsmasq kits, one installed by "apt" and managed
> thru the "systemctl" tools, and another one that somebody put there
> which is outside the realm of "apt" & "systemctl" (thus they don't
> know how to manange it).
>
> You should re
On 19 Sep 2017, at 22:36, Chris wrote:
> On Wed, 2017-09-20 at 04:31 +0200, Reindl Harald wrote:
>>
>> Am 20.09.2017 um 02:32 schrieb Chris:
>>>
>>> I then installed dnsmasq (apparently it wasn't installed)
>> frankly clean up your mess - you recently posted dnsmasq as well as
>> named listening
On Wed, 2017-09-20 at 04:31 +0200, Reindl Harald wrote:
>
> Am 20.09.2017 um 02:32 schrieb Chris:
> >
> > I then installed dnsmasq (apparently it wasn't installed)
> frankly clean up your mess - you recently posted dnsmasq as well as
> named listening on different interfaces for DNS, now you say
On 19 Sep 2017, at 16:40, Chris wrote:
> Here's the output now of the dig +trace
> tcp0 0
> 127.0.0.1:530.0.0.0:* LISTEN -
>
> tcp0 0
> 127.0.1.1:530.0.0.0:* LISTEN -
>
> udp
On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> On Wed, 2017-09-20 at 00:40 +0100, Martin Gregorie wrote:
> >
> > On Tue, 2017-09-19 at 16:44 -0500, Chris wrote:
> > >
> > >
> > >
> > > Thanks Martin, here's what I get, it appears to not be running.
> > >
> > > sudo systemctl stop dnsmasq
>
On Tue, 19 Sep 2017, Chris wrote:
On Wed, 2017-09-20 at 00:40 +0100, Martin Gregorie wrote:
On Tue, 2017-09-19 at 16:44 -0500, Chris wrote:
Thanks Martin, here's what I get, it appears to not be running.
sudo systemctl stop dnsmasq
[sudo] password for chris:
Failed to stop dnsmasq.service:
On Wed, 2017-09-20 at 00:40 +0100, Martin Gregorie wrote:
> On Tue, 2017-09-19 at 16:44 -0500, Chris wrote:
> >
> >
> > Thanks Martin, here's what I get, it appears to not be running.
> >
> > sudo systemctl stop dnsmasq
> > [sudo] password for chris:
> > Failed to stop dnsmasq.service: Unit dns
On Tue, 2017-09-19 at 16:44 -0500, Chris wrote:
>
> Thanks Martin, here's what I get, it appears to not be running.
>
> sudo systemctl stop dnsmasq
> [sudo] password for chris:
> Failed to stop dnsmasq.service: Unit dnsmasq.service not loaded.
>
OK, that makes sense
> sudo systemctl disable d
On Tue, 2017-09-19 at 15:40 -0500, Chris wrote:
> On Tue, 2017-09-19 at 08:41 -0500, David Jones wrote:
> >
> > On 09/19/2017 08:25 AM, Chris wrote:
> > >
> > >
> > > On Tue, 2017-09-19 at 08:16 -0500, Chris wrote:
> > > >
> > > >
> > > > On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
>
On Tue, 2017-09-19 at 14:47 -0700, John Hardin wrote:
> On Tue, 19 Sep 2017, Chris wrote:
>
> > I'm getting different outputs each time I run dig +trace
> > 65.43.116.208.iadb.isipp.com
> >
> > 65.43.116.208.iadb.isipp.com. 3600 IN A 127.0.1.255
> > 65.43.116.208.iadb.isipp.com. 3600 IN A
On Tue, 19 Sep 2017, Chris wrote:
I'm getting different outputs each time I run dig +trace
65.43.116.208.iadb.isipp.com
65.43.116.208.iadb.isipp.com. 3600 IN A 127.0.1.255
65.43.116.208.iadb.isipp.com. 3600 IN A 127.0.0.2
65.43.116.208.iadb.isipp.com. 3600 IN A 127.2.255
On Tue, 2017-09-19 at 22:07 +0100, Martin Gregorie wrote:
> On Tue, 2017-09-19 at 15:40 -0500, Chris wrote:
>
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > I've disable dnsmasq in my
> > > > > > > /etc/NetworkManager/NetworkManager.conf
> > via
> > #dns=dnsmasq
> >
> >
On Tue, 2017-09-19 at 15:40 -0500, Chris wrote:
> > > > > > I've disable dnsmasq in my
> > > > > > /etc/NetworkManager/NetworkManager.conf
> via
> #dns=dnsmasq
>
> However, when restarting the network I see:
> dnsmasq[2323]: reading /etc/resolv.conf
> dnsmasq[2323]: using nameserver 127.0.0.1#53
On Tue, 2017-09-19 at 08:41 -0500, David Jones wrote:
> On 09/19/2017 08:25 AM, Chris wrote:
> >
> > On Tue, 2017-09-19 at 08:16 -0500, Chris wrote:
> > >
> > > On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
> > > >
> > > >
> > > > On 09/18/2017 06:03 PM, Chris wrote:
> > > [snip]
> > >
On 09/19/2017 08:25 AM, Chris wrote:
On Tue, 2017-09-19 at 08:16 -0500, Chris wrote:
On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
On 09/18/2017 06:03 PM, Chris wrote:
[snip]
localhost dnsmasq[2323]: started, version 2.75 cachesize 150
localhost dnsmasq[2323]: compile time option
On 09/19/2017 08:16 AM, Chris wrote:
On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
On 09/18/2017 06:03 PM, Chris wrote:
[snip]
localhost dnsmasq[2323]: started, version 2.75 cachesize 150
localhost dnsmasq[2323]: compile time options: IPv6 GNU-getopt DBus
i18n IDN DHCP DHCPv6 no-Lua T
On Tue, 2017-09-19 at 08:16 -0500, Chris wrote:
> On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
> >
> > On 09/18/2017 06:03 PM, Chris wrote:
> [snip]
> >
> > >
> > >
> > > localhost dnsmasq[2323]: started, version 2.75 cachesize 150
> > > localhost dnsmasq[2323]: compile time options: I
On Tue, 2017-09-19 at 07:45 -0500, David Jones wrote:
> On 09/18/2017 06:03 PM, Chris wrote:
[snip]
> >
> > localhost dnsmasq[2323]: started, version 2.75 cachesize 150
> > localhost dnsmasq[2323]: compile time options: IPv6 GNU-getopt DBus
> > i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth
On 09/18/2017 06:03 PM, Chris wrote:
On Mon, 2017-09-18 at 12:32 -0500, David Jones wrote:
On 09/18/2017 11:52 AM, Chris wrote:
On Mon, 2017-09-18 at 11:40 -0500, David Jones wrote:
On 09/18/2017 11:14 AM, Chris wrote:
On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
On 18 Sep 2017,
On Mon, 2017-09-18 at 12:32 -0500, David Jones wrote:
> On 09/18/2017 11:52 AM, Chris wrote:
> >
> > On Mon, 2017-09-18 at 11:40 -0500, David Jones wrote:
> > >
> > > On 09/18/2017 11:14 AM, Chris wrote:
> > > >
> > > >
> > > > On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
> > > > >
> >
On Mon, 18 Sep 2017, Bill Cole wrote:
On 18 Sep 2017, at 12:14, Chris wrote:
[...]
On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
Why are you asking 168.150.251.35 to do DNS resolution for you? It is
not authoritative for isipp.com, so presumably you have a specific
local config causing y
On 09/18/2017 11:52 AM, Chris wrote:
On Mon, 2017-09-18 at 11:40 -0500, David Jones wrote:
On 09/18/2017 11:14 AM, Chris wrote:
On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
On 18 Sep 2017, at 10:57, Chris wrote:
[...]
I am receiving many hits on *_IADB_* rules just fine recentl
On 18 Sep 2017, at 12:14, Chris wrote:
[...]
> On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
>> Why are you asking 168.150.251.35 to do DNS resolution for you? It is
>> not authoritative for isipp.com, so presumably you have a specific
>> local config causing you to use it. It is explicitly r
On Mon, 2017-09-18 at 11:40 -0500, David Jones wrote:
> On 09/18/2017 11:14 AM, Chris wrote:
> >
> > On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
> > >
> > > On 18 Sep 2017, at 10:57, Chris wrote:
> > >
> > > [...]
> > > >
> > > >
> > > > >
> > > > >
> > > > > I am receiving many hits
On 09/18/2017 11:14 AM, Chris wrote:
On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
On 18 Sep 2017, at 10:57, Chris wrote:
[...]
I am receiving many hits on *_IADB_* rules just fine recently for
emails
from constantcontact.com and others.
I'm receiving rule hits:
TOP HAM RULES FIRED
On Mon, 2017-09-18 at 11:11 -0400, Bill Cole wrote:
> On 18 Sep 2017, at 10:57, Chris wrote:
>
> [...]
> >
> > >
> > > I am receiving many hits on *_IADB_* rules just fine recently for
> > > emails
> > > from constantcontact.com and others.
> > I'm receiving rule hits:
> >
> > TOP HAM RULES FI
On 18 Sep 2017, at 10:57, Chris wrote:
[...]
>> I am receiving many hits on *_IADB_* rules just fine recently for
>> emails
>> from constantcontact.com and others.
>
> I'm receiving rule hits:
>
> TOP HAM RULES FIRED
> RANKRULE NAME COUNT %OFMAIL %OFSPAM %OFHAM
> 40
On Mon, 2017-09-18 at 09:28 -0500, David Jones wrote:
> On 09/18/2017 09:12 AM, Kevin A. McGrail wrote:
> >
> > On 9/16/2017 4:36 PM, Chris wrote:
> > >
> > > I'm also seeing issues with ISIPP which is in 20_dnsbl_tests.cf.
> > > I've
> > > attached the message I sent them as well as their reply.
On 09/18/2017 09:12 AM, Kevin A. McGrail wrote:
On 9/16/2017 4:36 PM, Chris wrote:
I'm also seeing issues with ISIPP which is in 20_dnsbl_tests.cf. I've
attached the message I sent them as well as their reply. Another issue
I noticed with ISIPP is
Sep 16 12:09:38 localhost named[1284]: host unr
On 9/16/2017 4:36 PM, Chris wrote:
I'm also seeing issues with ISIPP which is in 20_dnsbl_tests.cf. I've
attached the message I sent them as well as their reply. Another issue
I noticed with ISIPP is
Sep 16 12:09:38 localhost named[1284]: host unreachable resolving
'ns1.ns.isipp.com/A/IN': 67.22
On 09/16/2017 11:52 AM, Alex wrote:
Hi,
On Sat, Sep 16, 2017 at 9:45 AM, Kevin A. McGrail
wrote:
Chris & all,
I have opened a bug about this:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7471
I believe scoring it 0 for now will disable the rule but that's just hiding
the issue.
Thanks
On 9/17/2017 8:35 AM, Benny Pedersen wrote:
i find this simply with postscreen in postfix
I use and love mimedefang. With it, I'm able to record a lot more data,
track things with Redis, etc. I should have been more clear.
I find that throwing immense resources at our spam filtering is bette
Kevin A. McGrail skrev den 2017-09-17 01:30:
I am a bad person to ask because I don't trust most any RBLS to use
them as a poison pill at the smtp level.
start using more WHITELISTS then :=)
i find this simply with postscreen in postfix
The bb list was setup specifically for spamassassin and
I am a bad person to ask because I don't trust most any RBLS to use them as a
poison pill at the smtp level.
The bb list was setup specifically for spamassassin and goes against the spirit
of the free for most policy we use to allow commercial providers to be included
by default. It's a bit of
Hi,
On Sat, Sep 16, 2017 at 9:45 AM, Kevin A. McGrail
wrote:
> Chris & all,
> I have opened a bug about this:
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7471
>
> I believe scoring it 0 for now will disable the rule but that's just hiding
> the issue.
>
> Thanks for bringing it to the li
On Sat, 2017-09-16 at 16:32 +0200, Reindl Harald wrote:
>
> Am 16.09.2017 um 16:27 schrieb Chris:
> >
> > named[1284]: REFUSED unexpected RCODE resolving
> > '165.170.166.108.iadb.isipp.com/A/IN': 168.150.251.35#53
> > named[1284]: host unreachable resolving
> > '165.170.166.108.iadb.isipp.com/A/
On Sat, 2017-09-16 at 09:45 -0400, Kevin A. McGrail wrote:
> Chris & all,
> I have opened a bug about this:
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7471
>
> I believe scoring it 0 for now will disable the rule but that's just
> hiding the issue.
>
> Thanks for bringing it to the li
Chris & all,
I have opened a bug about this:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7471
I believe scoring it 0 for now will disable the rule but that's just
hiding the issue.
Thanks for bringing it to the list, Chris.
Regards,
KAM
;brbl-lastexternal','bb.barracudacentral.org')
That sounds like a mistake. Does it meet our default RBL inclusion
policy? Will look into this.
From:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5984
" Justin Mason 2008-09-22 02:32:24 UTC
...
Normally we&
heck_rbl('brbl-lastexternal','bb.barracudacentral.org')
> That sounds like a mistake. Does it meet our default RBL inclusion
> policy? Will look into this.
From:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5984
" Justin Mason 2008-09-22 02:32:24 UTC
...
On 9/15/2017 8:51 PM, Chris wrote:
Ok, I see now that in 72_active.cf there is
Does adding a score RCVD_IN_BRBL_LASTEXT 0 to your local.cf work?
rbl('brbl-
> > lastexternal','bb.barracudacentral.org')
> >
> That sounds like a mistake. Does it meet our default RBL inclusion
> policy? Will look into this.
Ok, I see now that in 72_active.cf there is
ifplugin Mail::SpamAssassin::Plugin::DNSEval
On 9/15/2017 8:22 PM, RW wrote:
$ grep -ri barracudacentral /var/db/spamassassin/
/var/db/spamassassin/3.004001/updates_spamassassin_org/72_active.cf:header
RCVD_IN_BRBL_LASTEXT
eval:check_rbl('brbl-lastexternal','bb.barracudacentral.org')
That sounds like a mistak
it's NOT included?
$ grep -ri barracudacentral /var/db/spamassassin/
/var/db/spamassassin/3.004001/updates_spamassassin_org/72_active.cf:header
RCVD_IN_BRBL_LASTEXT
eval:check_rbl('brbl-lastexternal','bb.barracudacentral.org')
On 9/15/2017 6:46 PM, Chris wrote:
On Fri, 2017-09-15 at 18:20 -0400, Kevin A. McGrail wrote:
On 9/15/2017 5:50 PM, Chris wrote:
It's not a 'show stopper' it's just annoying to keep seeing this
and
wondering what the cause is.
You have configured your installation with the Baraccuda Reputation
nding something I can't list IP addresses on the access
form. Here is the only rule that I can find in my local.cf referencing
Barracuda but I have it commented out:
# header __RCVD_IN_BRBL eval:check_rbl('brbl',
'bb.barracudacentral.org')
# desc
On 15.09.17 23:50, Chris wrote:
> localhost named[1284]: connection refused resolving
> '190.129.2.198.bb.barracudacentral.org/A/IN': 64.235.154.72#53
According to http://barracudacentral.org/rbl/how-to-use that should be
b.barracudacentral.org, not bb.barracudacentral.org (single 'b').
-Ralph
On 9/15/2017 5:50 PM, Chris wrote:
It's not a 'show stopper' it's just annoying to keep seeing this and
wondering what the cause is.
You have configured your installation with the Baraccuda Reputation
Black List but likely not subscribed your IP address.
See http://barracudacentral.org/rbl
204926.d9a014b97f.eaede...@mail190.atl81.rsgsv.net> for
chris:1000
localhost named[1284]: connection refused resolving
'190.129.2.198.bb.barracudacentral.org/A/IN': 64.235.154.72#53
Is this an issue with an SA rule or some kind of an issue with Bind?
I'm only using it as a caching name
lhost [::1]:57298 to
> > > port
> > > 783, fd 5
> > > localhost spamd[7099]: spamd: setuid to chris succeeded
> > > localhost spamd[7099]: spamd: processing message
> > > for chris:1000
> > > localhost named[25689]: connection refused reso
is succeeded
> > localhost spamd[7099]: spamd: processing message
> > for chris:1000
> > localhost named[25689]: connection refused resolving
> > '166.170.166.108.bb.barracudacentral.org/A/IN': 64.235.145.15#53
> > localhost named[25689]: connection r
localhost named[25689]: connection refused resolving
> '166.170.166.108.bb.barracudacentral.org/A/IN': 64.235.145.15#53
> localhost named[25689]: connection refused resolving
> '167.170.166.108.bb.barracudacentral.org/A/IN': 64.235.145.15#53
> localhost named[256
ugh a years or so of hourly syslog snippets I found that all
was ok on 19 May this year
May 19 11:08:14 localhost named[1081]: success resolving
'205.6.174.108.bb.barracudacentral.org/A' (in
'bb.barracudacentral.org'?) after disabling EDNS
On the 23rd of May the below start
69 matches
Mail list logo
