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 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 <axb.li...@gmail.com> 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 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 containing 'spamcop' rather than simply for the existence of > an A record. For other DNSBLs, specific values are required in A records. > had forgotten the TXT thing... was a warning for ppl in general.. even for such using spamcop at MTA level. whatever..
