The email confirmation I received had this as a header from protonmail.com:

This email has failed its domain’s authentication requirements. It may be spoofed or improperly forwarded. Learn more

It worked fine, but I thought you should know.

  • David Emerson
    link
    English
    121 year ago

    Yeah, there’s a few things going on here with the ones I’ve received so far -

    • no dmarc for the subdomain (lemmy.sdf)
    • no spf record for the source (205.166.94.11)
    • no dkim

    I’m sure it’s early times, but this’ll end up in the spam folders of a ton of mail services with the header as it stands today.

    • KonQuesting
      link
      English
      41 year ago

      Indeed. Currently all emails from this instance have been landing in my spam folder.

  • @SDFMA
    link
    English
    31 year ago

    Do you have a link for applying to get off of protonmail.com’s blacklist?

    • @SDFMA
      link
      English
      31 year ago

      • David Emerson
        link
        English
        31 year ago

        Do you know for sure you’re on it? Might just be the recent registration time of the subdomain… some mailservers are especially unenthusiastic about novel domain names, even subdomains, and then when they’ve seen enough mail from them in circulation they calm down a bit.

  • Oliver Lowe
    link
    English
    11 year ago

    I see a SPF record for lemmy.sdf.org:

    % host -t txt lemmy.sdf.org
    lemmy.sdf.org descriptive text "v=spf1 mx ip4:209.160.32.187 -all"
    

    From the header of recent mail I received:

    Authentication-Results: aspmx1.migadu.com;
    	dkim=none;
    	dmarc=pass (policy=quarantine) header.from=sdf.org;
    	spf=pass (aspmx1.migadu.com: domain of lemmy@lemmy.sdf.org designates 205.166.94.11 as permitted sender) smtp.mailfrom=lemmy@lemmy.sdf.org
    X-Spam-Score: -3.18