Hi,
I'm having a problem with emails with short body text and a link to
malware that automatically downloads when the link is clicked. What's
the difference between the short body tests, besides the actual
character lengths:
72_active.cf
body__KAM_BODY_LENGTH_LT_128eval:check_
On 6 Jul 2017, at 18:48, jdow wrote:
No A or PTR record:
===8<---
[jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all
1. What is the reason to expect the name "ns1.apache.org" to have any
DNS records?
2. Using "all" as the final RRTYPE argument (or any other word beginning
Did you read any of the thread?
There shouldn't be an A record, and there literally can't be a (valid)
PTR record.
On Thu, Jul 6, 2017, at 15:48, jdow wrote:
> No A or PTR record:
>
> ===8<---
> [jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all
>
> ; <<>> DiG 9.9.4-RedHat-9.9.
No A or PTR record:
===8<---
[jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all
; <<>> DiG 9.9.4-RedHat-9.9.4-50.el7_3.1 <<>> updates.spamassassin.org
ns1.apache.org all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7892
;; flags: qr
On 6 Jul 2017, Marc Perkel outgrape:
> Hi Ted,
>
> You know what's interesting is that the adaptive immune system seems
> to work a lot like a spam filter or an antivirus program.
Heh, only if your spamfilters and/or antivirus programs intentionally
launch computer viruses at themselves to corrup
On Thu, 6 Jul 2017 12:14:02 -0500
David Jones wrote:
> On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
> >
> >> Am 06.07.2017 um 18:55 schrieb David Jones :
> >
> >> You can also run 'sa-update -vvv' to see more information on what
> >> it's looking for.
> >
> > Now I'm really confused: it
> Am 06.07.2017 um 19:19 schrieb Bill Cole
> :
>
> On 6 Jul 2017, at 4:06, Rainer Sokoll wrote:
>> Meaning: no updates for SA anymore?
>
> That's quite a leap of illogic...
OK, my fault.
I saw cron's error mail and thought that there could be a DNS problem.
Now I've learned from all of you th
> On Jul 6, 2017, at 9:48 AM, Kevin A. McGrail
> wrote:
>
> And my firm has put a lot of time into this which is still half the time
> David has in fixing ruleqa. So buy him a beer.
Done!
On 6 Jul 2017, at 4:06, Rainer Sokoll wrote:
> Hi,
>
> for at least the last 2 days, updates.spamassin.org does not resolve anymore:
>
> ~$ host updates.spamassassin.org.
Which means the name has no A record, but does have other records and/or
subdomains.
> But note:
>
> ~$ host nonexistent.spa
On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
Am 06.07.2017 um 18:55 schrieb David Jones :
You can also run 'sa-update -vvv' to see more information on what it's looking
for.
Now I'm really confused: it works the way described in this thread:
root@mx1:~# sa-update -vvv
DNS TXT query: 0.4.
On Thursday 06 July 2017 at 18:59:19, Rainer Sokoll wrote:
> > Am 06.07.2017 um 18:55 schrieb Antony Stone:
> >
> > "apt-get policy spamassassin" should show you which one really is
> > installed
>
> apt-cache ;-)
Oops :)
Yeah, I knew it was one of those apt-something commands which I wish apt
> Am 06.07.2017 um 18:55 schrieb David Jones :
> You can also run 'sa-update -vvv' to see more information on what it's
> looking for.
Now I'm really confused: it works the way described in this thread:
root@mx1:~# sa-update -vvv
DNS TXT query: 0.4.3.updates.spamassassin.org -> 1799552
Update
> Am 06.07.2017 um 18:55 schrieb Antony Stone
> :
>
> If you're using Jessie-backports as well (and have deliberately installed the
> backports version of this package) then you have 3.4.1
>
>
> "apt-get policy spamassassin" should show you which one really is installed
apt-cache ;-)
~$ ss
On 07/06/2017 11:53 AM, Rainer Sokoll wrote:
Am 06.07.2017 um 18:50 schrieb David Jones :
What version of SA are you running?
3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact
3.4.1, because I've never understood Debian's backporting strategy :-(
Rainer
Run 'sp
On Thursday 06 July 2017 at 18:53:10, Rainer Sokoll wrote:
> > Am 06.07.2017 um 18:50 schrieb David Jones :
> >
> > What version of SA are you running?
>
> 3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact
> 3.4.1, because I've never understood Debian's backporting strate
> Am 06.07.2017 um 18:50 schrieb David Jones :
> What version of SA are you running?
3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact
3.4.1, because I've never understood Debian's backporting strategy :-(
Rainer
signature.asc
Description: Message signed with OpenPGP
On 07/06/2017 11:27 AM, Rainer Sokoll wrote:
Am 06.07.2017 um 10:33 schrieb Tobi :
afaik updates.spamassassin.org does not need to be resolvable
The two important records for updates exist and resolve:
$dig mirrors.updates.spamassassin.org txt +short
"http://spamassassin.apache.org/updates/MIR
> Am 06.07.2017 um 10:33 schrieb Tobi :
>
> afaik updates.spamassassin.org does not need to be resolvable
>
> The two important records for updates exist and resolve:
>
> $dig mirrors.updates.spamassassin.org txt +short
> "http://spamassassin.apache.org/updates/MIRRORED.BY";
>
> $dig 0.4.3.upd
Hi Ted,
You know what's interesting is that the adaptive immune system seems to
work a lot like a spam filter or an antivirus program. Technically what
I did was a database update to my immune system to reclassify my cancer
as enemy. And the code to kill the cancer is in the cancer.
On 07/05
As David says, we use TXT and CNAME records not A records. We did switch to
cnames which broke sa 3.3.0 update resolution but that was fixed.
We know rulegen is turned off but rule distribution is working.
This means you can install SA and use sa-update to get current rules.
And they are curr
afaik updates.spamassassin.org does not need to be resolvable
The two important records for updates exist and resolve:
$dig mirrors.updates.spamassassin.org txt +short
"http://spamassassin.apache.org/updates/MIRRORED.BY";
$dig 0.4.3.updates.spamassassin.org txt +short
"1799552"
Am 06.07.2017 um
On 07/06/2017 04:54 AM, Merijn van den Kroonenberg wrote:
Hi
I get the same, who do we report it to
David, who works on these issues will read it here, he follows the list.
Michael
On 06/07/17 09:06, Rainer Sokoll wrote:
Hi,
for at least the last 2 days, updates.spamassin.org does not
> Am 06.07.2017 um 11:54 schrieb Merijn van den Kroonenberg :
>
> There have not really been updates since March due to server migration and
> such. Hopefully soon again.
The last update I see is from Apr 5 15:23 CET according the to time stamp.
Never noticed that until yesterday…
Rainer
s
> Hi
>
> I get the same, who do we report it to
David, who works on these issues will read it here, he follows the list.
>
>
> Michael
>
>
> On 06/07/17 09:06, Rainer Sokoll wrote:
>> Hi,
>>
>> for at least the last 2 days, updates.spamassin.org does not resolve
>> anymore:
>>
>> ~$ host updates.
Hi
I get the same, who do we report it to
Michael
On 06/07/17 09:06, Rainer Sokoll wrote:
Hi,
for at least the last 2 days, updates.spamassin.org does not resolve anymore:
~$ host updates.spamassassin.org.
~$
But note:
~$ host nonexistent.spamassassin.org.
Host nonexistent.spamassassin.o
Hi,
for at least the last 2 days, updates.spamassin.org does not resolve anymore:
~$ host updates.spamassassin.org.
~$
But note:
~$ host nonexistent.spamassassin.org.
Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
~$
Meaning: no updates for SA anymore?
Rainer
signature.asc
Descri
26 matches
Mail list logo
