Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
well, it’s 2018. DKIM is from 2004 and DMARC is 2010.
Any updates on when DMARC might be available. Our cybersecurity insurance is saying we need to be using it.
Absolutely yes, next up is DKIM inbound, SPF and DMARC. Thats why I'll keep this idea open until it is delivered.
Hello Thomas,
thank you for your hard work on this.
I am happy it is on the way.
But Outbound is not enough. When I have "another decent layer" then this layer can also do DKIM signing outbound and I do not need Domino to do it.
I have several customers, very small shops, that do not have the resources for an additional SPAM-gateway. When they ask me: can I bring Domino directly into the internet as the Mail-Exchanger, I have to tell them: "No: you can do SPAM and Virus-checking on Domino (TrendMicro, GBS, etc), but no security-checks that are on the SMTP- or TCP-layer"
For those customers DKIM, TLSRPT, MTA-STS outbound and DKIM, SPF, DMARC inbound would be a major win.
I'm glad to read you're happy with the DKIM inbound functionality.
outbound DKIM signing was indeed absolutely necessary, thanks for that.
Inbound SPF, DKIM and DMARC verification, on the other hand, is not so usefull if you're not having other decent layers of anti-spam checking. These authentication checks + DNS blocklists just aren't enough to fight spam/phishing today.
So I'll leave inbound DKIM, DMARC, SPF as is, because that's part of an more complete anti-spam system (unless you're planning to do that too, like Lotus Protector existed once...).
Greetings y'all!
DKIM support is now available in Domino 12.0.1 - support for DMARC and SPF are next.
DKIM is a 'must-have' if you deliver mails. I expect DKIM status for every incoming mail in the viewer (Notes) - like DKIM plugin in Thunderbird. I'm lucky to have an additional mail server between Domino and Internet generating DKIM. Its ashaming to see that Domino come to a halt with 20 years old mail technology
Implementation of DKIM and DMARC is absolutely necessary and should be quickly done or many will leave Domino as a mail server. Delivery of clean messages to gmail has recently become a nightmare.
DKIM and DMARC should be implemented in Domino. Many are waiting for these features. HCL should look into that. We are in 2021!
On the comment, "I seriously doubt Domino is getting any new customers, and really only has legacy customers left." -->
Our company has done new Notes/Domino customers. All were "small" shops around 200 users or less.
I've already voted for this too, and will be happy to see it natively supported.
The people at maysoft.com are actually working on this. The SPF part is complete to stop people spoofing your own domain, so it's a great start. You can contact their support address. It works 8.5 - 11. They also have good native antispam. Not sure if it's posted on their website yet.
It's so necesary that funcionality
DKIM, DMARC, SPF support is not an idea, but something the system must be able to do to be considered at all.
Someone should just build it if HCL isn't going to.
DKIM and DMARC support for Domino is a must!!!
DKIM and DMARC support for Domino is a must as Domino users are facing issues with spam when interacting with other mail servers.
Domino doesn't do DKIM?
Oh, my God.
It's really embarrassing.
This problem must be resolved quickly.
When will this be implemented. In a couple of weeks, it'll be 2021. This is impacting our inbound SMTP message delivery more and more. we're quickly approaching our time to 'go live'. There needs to be a solution soon, or we'll need to look for a non-Domino messaging solution otherwise.
Our security assessment team recommends using DKIM and our rating is affected because we can't implement something that has been available to other platforms except Domino.