On February 18, 2022 3:44:08 PM GMT+01:00, Stuart Henderson
<[email protected]> wrote:
>On 2022/02/18 15:26, Mark Patruck wrote:
>> On 18.02.2022 10:11, Alexander Hall wrote:
>> > Hi!
>> >
>> > Lately I've seen ports@ email in my spam folder, if they contain
>> > "bad.port.mk", since apparently "port.mk" is considered a domain name, and
>> > a harmful such, too.
>> >
>> > I've tried to whitelist "bad.port.mk" but it does not seem to help.
>> >
>> > I'm assuming this might be a common issue for other ports@ subscribers, so
>> > if anyone has any suggested remedy, is be happy to hear it.
>> >
>> > /Alexander
>>
>> No issues here with ports@ mails. I've also checked the symbol table
>> for scanned mails (rspamc analyse), but didn't find a bigger increase
>> of the final score due to potential spam.
>>
>> Out of interest...what does your scan results say for relevant mails?
>
>It hit gonzalo's nextcloud updates the other day. Relevant bit on mine
>was URIBL_BLACK(7.50)[port.mk:url];
Yup, exactly that.
While seemingly self-healed now, it would be nice to know how to avoid or
workaround this in the future.
/Alexander
