Community weekly digest ends up in SPAM

donho

I just created don.ho@notepad-plus-plus.org (and it’s the only one account on notepad-plus-plus.org so far.

And here is the log of email:

I’m wondering if I should create the account like admin and news-noreply ?

donho

@PeterJones said in Community weekly digest ends up in SPAM:

and if you want the forum emails to properly have the SPF, it will have to be more like what I showed in January (edited for the new hostinger-default text): v=spf1 include:_spf.mail.hostinger.com include:relay.mailchannels.net include:digitalocean.com ip4:104.131.212.184 ~all – the extra includes, and the ip4, will allow addresses associated with the emails from the Community Forum to also be allowed.

So should I edit it to the value you suggested?

donho

@donho said in Community weekly digest ends up in SPAM:

So should I edit it to the value you suggested?

I’ve just edited the entry I showed you on the screenshot above to the value you suggested, and back to the email section:

PeterJones

@donho ,

Yes, I would say to Edit the one you have highlighted to the value I supplied.

And if there’s an Add or New button not shown, I would use that to create a new TXT record with the name _dmarc and the value v=DMARC1; p=none; rua=mailto:don.ho@notepad-plus-plus.org

Also, if you could send me an email (I believe you can look at my profile and see my configured email) from the don.ho@notepad-plus-plus.org address, it should put useful information in the headers, which I can use to help you confirm whether that’s gotten set up right or not.

PeterJones

@donho said in Community weekly digest ends up in SPAM:

I’ve just edited the entry

and I can already confirm that change has propagated:

C:\>nslookup -type=TXT notepad-plus-plus.org
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
notepad-plus-plus.org   text =

        "v=spf1 include:_spf.mail.hostinger.com include:relay.mailchannels.net include:digitalocean.com ip4:104.131.212.184 ~all"

that alone should help. And I think if you can add the _dmarc entry, that will help also.

donho

@PeterJones said in Community weekly digest ends up in SPAM:

that alone should help. And I think if you can add the _dmarc entry, that will help also.

There’s control for adding entry:

But what kind of info should I provide to the 3 first case?

PeterJones

@donho ,

TYPE should be TXT
NAME should be _dmarc or _dmarc. (different interfaces differ on whether or not they want the . after the name)
POINTS TO should be the value v=DMARC1; p=none; rua=mailto:don.ho@notepad-plus-plus.org

donho

Done:

Could you check now?

PeterJones

@PeterJones said in Community weekly digest ends up in SPAM:

if you could send me an email (…, it should put useful information in the headers, which I can use to help you confirm whether that’s gotten set up right or not.

I can confirm that the email arrived and had a valid DKIM signature. (It also told me that it’s under hostingermail-a._domainkey.notepad-plus-plus.org, so it is using a different selector than I was looking for.)

C:\Users\peter.jones\Downloads\TempData\nppCommunity\garden>nslookup -type=TXT hostingermail-a._domainkey.notepad-plus-plus.org
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
hostingermail-a._domainkey.notepad-plus-plus.org        canonical name = hostingermail-a.dkim.mail.hostinger.com
hostingermail-a.dkim.mail.hostinger.com text =

        "v=DKIM1;k=rsa;p=MIIBIjANB...."

So yes, DKIM is now set up correctly on those.

I will give a bit of time to allow more propagation of DNS (it’s not instant all over), and then try to get the Community to send me another confirmation email, and see if it’s now doing the DKIM correctly from the forum as well.

PeterJones

@donho said in Community weekly digest ends up in SPAM:

Could you check now?

C:\>nslookup -type=TXT _dmarc.notepad-plus-plus.org
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
_dmarc.notepad-plus-plus.org    text =

        "v=DMARC1; p=none; rua=mailto:don.ho@notepad-plus-plus.org"

Yes, the DMARC has gone through as well.

Thank you for going through this process.

I think at this point, there is a good chance that the confirmation emails will start working better. But I’ll give you more feedback later today.

donho

@PeterJones
Good! Let’s wait & see.
Thank you very much for helping community configuration!

PeterJones

@timint01 and All,

Don and I have been working back and forth. I think we’ve finally got it set up right, so that the DKIM and DMARC will be set correctly – at least, it has in the test emails I’ve sent.

I was able to send a test message to an alternate gmail account, and that accound received the email (which it never did before).

Please let us know if it’s still showing up as spam. And thanks to @donho for his patience while I kept dreaming up new experiments for him to try.

donho

Rather thank @PeterJones for his guide for setting up!