Den 31-01-2021 kl. 21:11 skrev Riccardo Alfieri:
>
> On 1/31/21 8:28 PM, Arne Jensen wrote:
>
>> Spamhaus (blacklist) will return 127.255.255.x responses, if you're
>> over quota, using public resolvers or otherwise incorrect queries.
>>
>>
> this is not completely true. As stated here:
>
I'm working on a rule to up the spam score for messages that contain a
large number (>=30) of Mailchimp CSS declarations and a link shortener,
since all links in something actually sent through Mailchimp are forced
through their click tracking, this is turning out to be a decent indicator.
In
On 01/02/2021 04:59, Axb wrote:
On 1/31/21 7:57 PM, Jared Hall wrote: On 1/31/2021 6:58 AM, Axb wrote:
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe! OK. Thanks.
Issue
Anyone got an goss on where they went?
Been down since late last year, haven't seen any messages about closing
up shop.
--
Regards,
Noel Butler
This Email, including attachments, may contain legally privileged
information, therefore at all times remains confidential and subject to
100% ? Something's amiss...
First time in 10 years I've gotten this:
"An error occurred while processing your request.
Reference #30.24721cb8.1612134453.1a374d81"
from here: https://www.spamcop.net/
Something has changed.
On 2021/01/31 15:50 PM, Pedro David Marco wrote:
spamcop
spamcop seems back.. but... we need to be 100% sure that people behind it who
should be
-
Pedreter
On Sunday, January 31, 2021, 08:11:30 PM GMT+1, Axb
wrote:
On 1/31/21 8:04 PM, Bill Cole wrote:
> On 31 Jan 2021, at 6:58, Axb wrote:
>
>> Happy Sunday !!!
>>
>> Cisco forgot to
On 1/31/21 8:28 PM, Arne Jensen wrote:
Spamhaus (blacklist) will return 127.255.255.x responses, if you're
over quota, using public resolvers or otherwise incorrect queries.
Hi,
this is not completely true. As stated here:
Den 31-01-2021 kl. 18:43 skrev Matus UHLAR - fantomas:
> On 31.01.21 16:30, Arne Jensen wrote:
>> If this one causes false positives for anyone, then that actual
>> person/organisation (obviously, MX operator side) that it causes false
>> positives for, are the one to blame.
>>
>> Spamcop hasn't
On 1/31/21 8:04 PM, Bill Cole wrote:
On 31 Jan 2021, at 6:58, Axb wrote:
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe!
SpamAssassin was already "safe" in that it
On 31 Jan 2021, at 6:58, Axb wrote:
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe!
SpamAssassin was already "safe" in that it checks the SpamCop BL for a
TXT record
On 1/31/21 7:57 PM, Jared Hall wrote:
On 1/31/2021 6:58 AM, Axb wrote:
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe!
OK. Thanks.
Issue has been FIXED.. all looks
On 31 Jan 2021, at 10:04, Matus UHLAR - fantomas wrote:
On 31.01.21 15:43, Axb wrote:
On 1/31/21 3:35 PM, Matus UHLAR - fantomas wrote:
On 31.01.21 12:02, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
On 1/31/2021 6:58 AM, Axb wrote:
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe!
OK. Thanks.
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
On 31.01.21 12:02, Georg Faerber wrote:
That's still one year to go, isn't it?
Den 31-01-2021 kl. 15:35 skrev Matus UHLAR - fantomas:
seems that this has been overtaken by
Den 31-01-2021 kl. 16:52 skrev RW:
> On Sun, 31 Jan 2021 16:30:21 +0100
> Arne Jensen wrote:
>
>
>> If everyone had done proper return code checking, e.g. response =
>> 127.0.0.2, and not been triggering on anything else, then everyone's
>> mail systems would have kept running just fine, without
On Sun, 31 Jan 2021 16:30:21 +0100
Arne Jensen wrote:
> If everyone had done proper return code checking, e.g. response =
> 127.0.0.2, and not been triggering on anything else, then everyone's
> mail systems would have kept running just fine, without any issues,
> at all.
SpamAssassin does a
Den 31-01-2021 kl. 15:35 skrev Matus UHLAR - fantomas:
> On 31.01.21 12:02, Georg Faerber wrote:
>> On 21-01-31 12:58:48, Axb wrote:
>>> Cisco forgot to renew spamcop.net
>>> Registry Expiry Date: 2022-01-30T05:00:00Z
>>
>> That's still one year to go, isn't it?
>
> seems that this has been
On 31.01.21 15:43, Axb wrote:
On 1/31/21 3:35 PM, Matus UHLAR - fantomas wrote:
On 31.01.21 12:02, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
That's still one year to go, isn't it?
seems that this has
On 1/31/21 3:35 PM, Matus UHLAR - fantomas wrote:
On 31.01.21 12:02, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
That's still one year to go, isn't it?
seems that this has been overtaken by someone who
On 31.01.21 12:02, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
That's still one year to go, isn't it?
seems that this has been overtaken by someone who provides false positives
for anyhing:
;; ANSWER
I get someone over there know.
Udeme - LinkedIn
On Sun, Jan 31, 2021 at 7:16 AM Noel Butler wrote:
> On 31/01/2021 22:06, Matus UHLAR - fantomas wrote:
>
> On 21-01-31 12:58:48, Axb wrote:
>
> Cisco forgot to renew spamcop.net
> Registry Expiry Date: 2022-01-30T05:00:00Z
>
>
> On 31.01.21
On 2021-01-31 13:05, Matus UHLAR - fantomas wrote:
SPF
basicly REJECT envelope sender if its local domain
and only on port 25, not elsewhere
DKIM
DMARC
but not with DKIM, DMARC
On 31/01/2021 22:06, Matus UHLAR - fantomas wrote:
On 21-01-31 12:58:48, Axb wrote: Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
On 31.01.21 12:02, Georg Faerber wrote:
That's still one year to go, isn't it?
Updated Date: 2021-01-31T09:40:42Z
they fixed it
On 1/31/21 1:02 PM, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
That's still one year to go, isn't it?
That is when the domain will be free for takers.
see https://spamcop.net/
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
On 31.01.21 12:02, Georg Faerber wrote:
That's still one year to go, isn't it?
Updated Date: 2021-01-31T09:40:42Z
they fixed it in the meantime.
--
Matus UHLAR - fantomas,
On 30.01.21 14:30, Kenneth Porter wrote:
What do others do about backscatter to their role addresses? It seems
spammers have recently discovered the role addresses noc, hostmaster,
and webmaster for one of my business domains and are forging them as
senders. As a result, I'm seeing lots of
On 21-01-31 12:58:48, Axb wrote:
> Cisco forgot to renew spamcop.net
> Registry Expiry Date: 2022-01-30T05:00:00Z
That's still one year to go, isn't it?
Happy Sunday !!!
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z
Better disable till it's fixed
score RCVD_IN_BL_SPAMCOP_NET 0
Stay safe!
28 matches
Mail list logo
