eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

225
active users

#antispam

0 posts0 participants0 posts today

Should I Stop Caring and Let IP Address Reputation Sort Them Out? nxdomain.no/~peter/should_i_st

How long does data on misbehaving hosts on the Internet stay relevant in an IP Address Reputation context?

Link to poll within (on for a week, 4 days left, please *do* vote).

#security #passwordguessing #antispam #sshgropers #pop3gropers #blacklists #blocklists #bruteforcers #spam #cybercrime #ipreputation

(repost for the CET-ish crowd, some still in holiday mode, and with graphics of sorts added)

nxdomain.noShould I Stop Caring and Let IP Address Reputation Sort Them Out?

I interpret the following

Apr 20 18:38:09 skapet spamd[52874]: (GREY) 117.53.153.22: <> -> <spfilter-2.sel01.mschosting.com-1745167076-testing@ehtrib.org>

As a sign there are still, er, individuals out there who think SMTP callbacks were a good idea.

Please have them read "Twenty-plus years on, SMTP callbacks are still pointless and need to die" (2017) nxdomain.no/~peter/twenty-plus

nxdomain.noTwenty-plus years on, SMTP callbacks are still pointless and need to die
#spam#spamd#smtp

Welcome new imaginary friends glenn.finch@bsdly.net and stewart.ashton@bsdly.net to the cast of millions at nxdomain.no/~peter/traplist.sh (served up to us today by mxtest@serverscannerpro.com and mxtest@emailengineexpert.com, respectively).

My favorite new imaginary friend (aka spamtrap) today was however Noreplyadmin@bsdly.net, a faked sender address.

Logs for the interested at nxdomain.no/~peter/blogpix/new

nxdomain.nobsdly.net - A traplist collected by Peter Hansteen

The other horribly nonsensical thing I saw during the last 24 hours was the error messages GNU Emacs emits when it is faced with a file of a size that exceeds its expected per-buffer memory allocation.

Fortunately a sane solution was found for that particular problem (split that big hand generated log into smaller pieces) - search for "this log directory" in nxdomain.no/~peter/traplist.sh #spamtraps #greyptrapping #spamd #antispam #cybercrime #imaginaryfriends

nxdomain.nobsdly.net - A traplist collected by Peter Hansteen

In another thread, @puppygirlhornypost2@transfem.social talks about challenges regarding proliferation of spam (or other unwanted content) on the fediverse:

... I was talking about reddit's "posts require approval" mode. Something that might be of use for new accounts registering on pixelfed instances to prevent things like gorespam from occurring.

NodeBB has the post queue (our name for it), and it works really well to stop drive-by spammers. Most cheap spam is easily identified as such, and it's only a couple clicks to send them to /dev/null.

More recently, and especially since we've been federating posts outward, we've started encountering possibly LLM generated content entering our post queue. It could be that these accounts are legitimate users creating an account to respond to remote content, but it's equally likely that they're attempting to create plausible content in order to pass validation, before proceeding to post spam.

At least here on community.nodebb.org it's trivial to discover, because this forum is for NodeBB support/discussion, and a post out of the blue responding to a post about Trump or Israel/Palestine is very obviously not meant to be on this forum, although it's definitely one of those "hard problems" for more general instances.

NodeBB Community · As the @PixelFed platform grows, we see the need to leverage our communal resources to tackle some of the more challenging issues, like instance blocks, spam and moderation issues.As the @PixelFed platform grows, we see the need to leverage our communal resources to tackle some of the more challenging issues, like instance blocks, spam...

Is SPF Simply Too Hard For Application Developers?
The Sender Policy Framework (SPF) is unloved by some, because it conflicts with some long-established SMTP email use cases. But is it also just too hard to understand and to use correctly for application developers? nxdomain.no/~peter/is_spf_too_
(2016 but still holds) #smtp #spf #mail #spam #antispam #security #openbsd #spamd

nxdomain.noIs SPF Simply Too Hard For Application Developers?

Likely not blogworthy in itself, but #openbsd #spamd aficionados will get a light chuckle from hearing that some scraping and massaging relevant logs had the number of imaginary friends at nxdomain.no/~peter/traplist.sh for our not-friends to play with roll past the one million mark in the early hours of today CET.

The recent update of nxdomain.no/~peter/harvesting_ has links to more info. #spam #antispam #greytrapping #blocklists #cybercrime

nxdomain.nobsdly.net - A traplist collected by Peter Hansteen

Why can't we agree on a #FirstContactProtocol for #Email?

That the first time someone sends you an email, your email app checks if this address is in the allow-list. If it's not your client will ask you to add this person to the allow- or block-list

If the email is signed with OpenPGP your email app checks if the key is in the allowed-keys list and if not ask to add it to this list or to the blocked-keys list. This way people can change email address w/o re-applying