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 Tue, 19 Sep 2017 10:06:58 -0500
David Jones wrote:
> header ENA_SUBJ_IS_SPACE Subject =~ /^ $/
> >>>
> >>> The OP said there was a space after 'Subject:', so that rule
> >>> wouldn't detect it.
> My point was supposed to be a single space should hit
> MISSING_SUBJECT and
My recommendation as a first step is to go to mail-tester.com. They will
tell you to send an email to a temp email address, and they will analyze
and grade your email as to 'spamy-ness'. Outlook, gmail, etc were
flagging a lot of my emails. After I finally fixed everything and got
mail-tester.
On 09/19/2017 09:35 AM, RW wrote:
On Tue, 19 Sep 2017 10:05:44 -0400
Kevin A. McGrail wrote:
On 9/19/2017 9:11 AM, David Jones wrote:
I have had these in place for years. Maybe Kevin can consolidate
and integrate this into his KAM.cf so I could remove them or we
could eventually get them into
On 09/19/2017 09:03 AM, RW wrote:
On Tue, 19 Sep 2017 08:32:12 -0500
David Jones wrote:
On 09/19/2017 08:20 AM, RW wrote:
On Tue, 19 Sep 2017 08:11:03 -0500
David Jones wrote:
header ENA_SUBJ_IS_SPACE Subject =~ /^ $/
The OP said there was a space after 'Subject:', so that
On Tue, 19 Sep 2017 10:05:44 -0400
Kevin A. McGrail wrote:
> On 9/19/2017 9:11 AM, David Jones wrote:
> > I have had these in place for years. Maybe Kevin can consolidate
> > and integrate this into his KAM.cf so I could remove them or we
> > could eventually get them into the default SA ruleset
On 9/19/2017 9:11 AM, David Jones wrote:
I have had these in place for years. Maybe Kevin can consolidate and
integrate this into his KAM.cf so I could remove them or we could
eventually get them into the default SA ruleset after some testing.
Hi David,
Thanks. In addition to KAM.cf, I mai
On Tue, 19 Sep 2017 08:32:12 -0500
David Jones wrote:
> On 09/19/2017 08:20 AM, RW wrote:
> > On Tue, 19 Sep 2017 08:11:03 -0500
> > David Jones wrote:
> >> header ENA_SUBJ_IS_SPACE Subject =~ /^ $/
> >
> > The OP said there was a space after 'Subject:', so that rule
> > wouldn'
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:20 AM, RW wrote:
On Tue, 19 Sep 2017 08:11:03 -0500
David Jones wrote:
On 09/19/2017 07:23 AM, Kevin A. McGrail wrote:
Is it purposeful extra space though that might indicate spaminess?
Spample? Regards,
KAM
On September 19, 2017 8:13:09 AM EDT, RW
wrote:
On Tue, 19 Se
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, 19 Sep 2017 08:11:03 -0500
David Jones wrote:
> On 09/19/2017 07:23 AM, Kevin A. McGrail wrote:
> > Is it purposeful extra space though that might indicate spaminess?
> > Spample? Regards,
> > KAM
> >
> > On September 19, 2017 8:13:09 AM EDT, RW
> > wrote:
> >
> > On Tue, 19 Sep 201
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 Tue, 19 Sep 2017 13:13:09 +0100
RW wrote:
> On Tue, 19 Sep 2017 09:27:13 +0100
> Sebastian Arcus wrote:
>
> > I've had a number of emails with no subject not triggering the
> > MISSING_SUBJECT rule - only to discover that the spammers have added
> > a white space after 'Subject:'
> Some pe
On 09/19/2017 07:23 AM, Kevin A. McGrail wrote:
Is it purposeful extra space though that might indicate spaminess? Spample?
Regards,
KAM
On September 19, 2017 8:13:09 AM EDT, RW wrote:
On Tue, 19 Sep 2017 09:27:13 +0100
Sebastian Arcus wrote:
I've had a number of emails with n
On 09/19/2017 01:25 AM, Sebastian Arcus wrote:
This is a bit off topic as it is not directly related to SA, but I'm
hoping that with the email and spam expertise on this group, someone
might throw in a useful idea - which would be much appreciated.
I have this problem on one site where most em
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,
Is it purposeful extra space though that might indicate spaminess? Spample?
Regards,
KAM
On September 19, 2017 8:13:09 AM EDT, RW wrote:
>On Tue, 19 Sep 2017 09:27:13 +0100
>Sebastian Arcus wrote:
>
>> I've had a number of emails with no subject not triggering the
>> MISSING_SUBJECT rule - onl
On Tue, 19 Sep 2017 09:27:13 +0100
Sebastian Arcus wrote:
> I've had a number of emails with no subject not triggering the
> MISSING_SUBJECT rule - only to discover that the spammers have added
> a white space after 'Subject:' - which appears to fool the code into
> thinking that there is an act
Microsoft use their own methods of detection including based on
reputation and 'length of service' - ie, if you have only just started
sending emails out from your own address (which you have) then they may
well consider you suspicious. Theres not much yo can do about it. More
info here: http
I've had a number of emails with no subject not triggering the
MISSING_SUBJECT rule - only to discover that the spammers have added a
white space after 'Subject:' - which appears to fool the code into
thinking that there is an actual subject. Would it be possible to
'smarten up' the code a bit
35 matches
Mail list logo
