• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle
  • digdilem@feddit.uktoProgramming@beehaw.orgEmail is Dead
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    As long as you set up SPF and DKIM records on your mailserver, you’ll never get marked as spam.

    Sorry - that’s factually incorrect. If your IP is on a residential block, you’ll be downscored. If you’re on a dynamic IP, same again, but weighted even more harshly, by pretty much every antispam service. In addition, every commercial service is very secretive about what methods they use, for good reason, so you cannot claim with any accuracy that “you just need to do this $thing to get read”. (Although I do agree the original post is not well researched, knowledgeable nor particularly useful to anyone)

    SPF and DKIM are essential to getting your email out, but it’s not the only thing, and sometimes no matter what you do do, your hit rate is going to be low.

    Source: Me. Been running mail servers privately and commercially for over twenty years. Before then, I ran fidonet and netmail services through the 90s and into the tail end of the 80s. There’s many things I know bugger all about, but email is not one of them. (And if anyone’s interested what I do for personal email now - I use gmail, because it works and maintaining it is somebody else’s problem)


  • digdilem@feddit.uktoProgramming@beehaw.orgEmail is Dead
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    AI’s been in use in commercial anti-spam for quite a while now - and on the flip side is also being used by the spam senders. Just another front on the unending war.

    But spam (and phishing, and all malware) happens because humans get fooled by it. No reason to think AI will be any smarter.






  • I agree, the parasitic nature of this relationship has been sharpened in the past week and made many of us think more critically of it.

    My question is - what happens if several significant FOSS projects change their licence to “Sources must be publically available if repackaged” or even “Cannot be packaged for sale”, specifically to prevent a non-freely available distro profiting from it.

    Yes, that distro could fork the software at the point before the new licence is applied, but they they would be responsible for maintaining that fork going forwards, no? And that would take a lot of resources and need it to be called something else.