You can map your own domain to your Ning site at the "Domain Mapping" page of your admin pages. From that time Ning will be sending mail on behalf of your domain e.g. www.yourdomain.com. Your From address will be mail@www.yourdomain.com and your Reply-To address will be do-not-reply@www.yourdomain.com.
Are any of you using DKIM (https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) to prevent your domain from being used for phishing and email spam? I noticed Ning is DKIM signing their emails sent on behalf of my domain but the DKIM signing fails. For succesful DKIM signing you need a DKIM record to be added to the DNS of your domain. Ning is not answering my requests for this DKIM DNS record. I asked them 6 weeks ago but I am kept waiting. The helpdesk informed me that the tech team would contact me directly but they didn't. I contacted Ning several times about this. I don't understand why this takes so long.
So if there is anybody who has received their DKIM DNS record from Ning, please let me know.
You can check if Ning is DKIM signing your outgoing mail by sending yourself an invitation from your network and check the email headers. Adding a failing DKIM signature to outgoing mails results in higher chances your outgoing mails being marked as spam. So effectively Ning is increasing the risk of their outgoing mail being marked as spam by not handing over the necessary DKIM DNS records to the Network Creators of their networks having mapped domains.
Let me know if you have a mapped domain and if Ning is troubling your outgoing email too by adding a failing DKIM signature.
Regards,
Bart
Replies
Hi Bart,
I wonder if you got the DKIM entry from the technicians and if it worked for you.
I also asked about this and got the DKIM code, but it doesn't look like Ning is applying DKIM signature to the email when they send on their side.
I am still waiting for an answer to my question about this from the technical guys.
Boris
Hi Boris,
Just this week, after almost 4 months of asking, complaining, begging, demanding, I finally received the required DKIM DNS entry, and in addition they sent me the necessary SPF DNS entry.
SPF DNS record: @ 300 IN TXT "v=spf1 ip4:208.82.16.0/22 ip4:8.6.19.94 a mx -all"
Ning was applying a DKIM-Signature header to their outgoing email from the moment I mapped my domain to Ning.
To prevent spammers using your domain for their spam you can add a DMARC DNS record blocking your domain to be used for email that fails either the SPF validation or the DKIM validation or both. More info: https://www.uriports.com/dmarc
Bart
Hi Boris,
I can share it with you. The DNS is publicly readable, so I don't think it is a problem to share it:
default._domainkey IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCmBn+4lwWqZ5dGeMltUqvZdPHfuoc1XmQFALIiBr3Eu/wVvDaoi1TTdxiwNa9smf1QTcCH6TUpb+v1emgukRmgkVXkBdaRmShNNpAFy5FF2hIrib+598jEi4wixUJoAd6qltF7D+EWq5p3bBAYunygM0BPSwc0XoRX/tEa168mJwIDAQAB"
Depending on the DNS editor you possibly have to remove the double quotes around the DKIM TXT record.
Bart
Hi Bart,
If this DKIM works for you, can I use the same DKIM as you, or is it unique for each domain?
I got a different DKIM code and it didn't work for me even after I removed the asterisks
Boris
Hi Boris,
You can try if it works for you. It depends on the configuration Ning is using if every mapped domain gets the same DKIM DNS record or not.
I noticed Ning is not yet adding the DKIM-Signature header to your outgoing email. I signed up for your community and checked the email headers. This is something Ning should solve for you. Adding the DNS record without a DKIM-Signature header has no effect.
Bart