Hi my name is Nancy and I'm a PM on Confluence Cloud- I'm very excited to announce that starting this week, all product/org admins will have access to configuring custom email address for their Confluence site. 
We realize this has been a long awaited feature, and I'm excited to have you all test it out and provide any additional feedback. 

Feel free to read more about this on the Community Post here.
Please reach out via Community/Support if there are any additional questions. 

4+ years this is open. Blindingly obvious it must be provided, and indeed should have been there before the forced migration to Cloud. We were told the reason for a move to Cloud was feature addition and bug fixes would go into high gear! Less waiting!

Happy 4 year birthday, CONFCLOUD-68551 (sorry, belated, was in November). 

I wonder if Atlassian will ever deign to provide a response ?

Only for Jira? This can`t be real...

Reminder: https://www.atlassian.com/company/values

Another very old issue that has huge customer demand, but will not be addressed by Atlassian. Seems reasonable considering the purpose of the Confluence product (internal wiki), and likely relatively trivial to implement, but Atlassian is not a customer focused company. Those of us who are forced to migrate to Cloud will start seeing update and digest messages from "Confluence", something we never wanted. 

This is a downside to cloud migrations right now, especially for the more security minded clients.

please implement

I'm surprised this is not already available as it is for Jira. It's not even assigned yet??

Disappointed to see this not being a feature, despite it being available in Jira Cloud

I don't understand why this is possible with Cloud Jira, but not with Confluence? In times of phishing and co. it is even more important to send mails from trustworthy sources and to mark them. For large companies that use both products, this is a huge problem. Especially because these problems did not exist on premise.

Having the ability to change who the sender is would be very helpful. Google flags emails that use a person's name that doesn't match their email address with a big banner. We've trained our users to pay attention to these banners and act accordingly. Having exceptions to this policy is moving in the wrong direction. https://www.dropbox.com/s/cfj1z5q2rth876z/Google%20-%20report%20as%20phishing.png?dl=0

+14 

Let's go, stop wasting time!

+1

Mails sent from confluence@mail-eu.atlassian.net is highly likely to be ignored by many of our users, or end up in Spam folders. We need this to be configurable somehow.

Not having this ability means we're stuck with Jira batching notification emails on their own schedule, instead of users being able to receive notifications of page edits immediately.

Exceptions listed https://confluence.atlassian.com/jirakb/jira-cloud-email-notifications-are-delayed-1102614971.html pointed to using custom email addresses so it's disappointing this still can't be done.

Not holding my breath this will come anytime soon either as this request is 3 years old.

+1

I've already express our need for this voting it. Today I wish a Happy Birthday (3 years!) to this request .

+1

Definitely upvoting this one.  Makes no sense just having Jira working this way and not Confluence too.

Why is this available in Jira and not Confluence? 

I'm on the same boat in regards to compliance. 

Please prioritize this feature. 

Our compliance teams are flagging the lack of this feature as an issue as all company communication should be using our verified domain.  Aside from that our mail system is very strictly configured so emails from confluence cloud often get flagged as spam.

+1

This is a problem as we have confluence notification emails incorrectly get caught as spam due to external domain sending email with the user's name when sending notification for adding someone into teams.

Upvote here too. This is a problem as we have strict email security and are constantly needing to release emails that incorrectly get caught as spam due to external domain sending email with the user's name when a comment notification is sent.

I vote up this feature. We have similar experiences to the others who commented. 

This feature should be implemented. Jira has it, Confluence should as well.

Without this feature, it is impacting our SOC 2 and ISO 27001 audit as we need to have all of our SaaS platforms that send/receive emails on behalf of our domain and organization to be DMARC compliant.

+1 for this feature request.

To be clear this impacts our business use - email notifications are used as part of the review workflow for documents. When the Confluence system sends these messages they are received as 'external' content and are therefore considered untrusted. As with most enterprise email solutions such messages are flagged and presented to the end user as a possible threat. We now have to instruct our users to ignore this very important banner and 'trust' the email. The challenge is clear: we are teaching users that messages appearing to come from this email address are trustworthy. Even if the users are diligent and only trust this email address we still have opened a hole in what should be a secure path. With Jira we are able to configure trusted messages and Confluence should be the same. It is time to put any excuse about Jira and Confluence being 'different' aside and take security seriously.

Quite surprised to see this was not already part of the solution, and more over shocked that there is no answer from Atlassian after being raised for nearly three years.

Seriously! Just went through the process to getting email domain verified only to realise that Confluence isnt included and its the most common email that gets flagged as spoofing. One step forward, two steps back argh!

Definitely looking for this as well.

+1 to all of this, surprised that this feature wasn't mirrored from Jira already :/ 

I agree as well. The majority of our Confluence notifications go directly to Spam for our Google Workspace users and I am constantly going into our Spam quarantine and releasing those messages. Having a custom notification (and should be able to piggyback off the settings already set for JIRA) would remove the management overhead of having to manually release spam messages that are indeed valid. I have the confluence email set to skip spam, but Google is still aggressive and flags them as Spam (or at least a majority of the notifications).

Please add this possibility as it is a basic feature nowdays. Jira allows to do so already. Now make the next step with Confluence Cloud after gathering interest for 2,5 years. Thank you.

This functionality already exists in Jira, but I discovered when trying to perform this action on our Atlassian Cloud applications that custom emails could only be assigned to Jira products.

This is a huge problem for us because emails from Atlassian Cloud products that go to internal email addresses and are redirected to external email addresses for those users are triggering a limit in Exchange Online and they are blocking outbound email from the Atlassian mail domain as it is not a registered domain in our tenant. We must change these products to send from a custom domain registered to our M365 tenant to avoid triggering this block.

Products not supporting the most basic and obvious features, especially when they were supported in the soon to be unsupported on-premises server versions of the same products, is a frequent occurrence. As an IT practitioner and systems architect, Atlassian never ceases to disappoint.

Hi

yes, I have the same problem

Agree with Mark and Adrian here, very disappointing considering one can now finally configure it for Jira with custom domain even (e.g. atlassian.domain.com).

We basically tag these as spoofing because that's exactly what it is, an external mail server sending an email on behalf of an internal employee without proper authorization/authentication.

These days SPF/DKIM & email configuration in SaaS are just very basic. Would love to see Atlassian step up their game here.

Seconded -  Gmail/Google will flag Confluence page updates/mention emails as suspicious.
We are trialing a move to Cloud, however our end users have all been trained on email best practices and recognizing phishing etc so this would create an influx of helpdesk tickets from concerned end users.

It is not really acceptable to be unable to configure outbound email flow these days in an "enterprise" type cloud product.

Big oversight here considering how many high severity Atlassian CVEs/security vulnerabilities have been disclosed lately and the general state of malicious activity for anything connected to the internet.
This really should be a no brainer for Atlassian to prioritize if they wish to stay relevant on good security practices.

We should be able to configure our own email server/user for notification emails. Having emails originate form outside of the organization for internal notifications is an information security threat. We will train end users that emails from outside the organization are okay to click on.