I've configured a project to use a different email address when notifications are sent by that project (according to directions at https://confluence.atlassian.com/display/JIRA/Configuring+Email+Notifications#ConfiguringEmailNotifications-emailaddress ).
However, editing the notification scheme email address seems to have no effect. No matter what it is set to, emails still come from "email@example.com" (the default set in Admin->Outgoing Email) Is something else affecting this? Is there another action I need to take before this setting is recognized?
Just to follow up on this: The problem did up being my gmail configuration. See https://support.google.com/a/answer/22370?hl=en
My default jira email account uses a google business doman alias, and you have to specficially allow a different email address to be used as an alias (and thus have the "reply-to" be recognized). So, I added my project email address in the "Send mail as" / "Add another email address" section of the above link, and it now works fine.
The usual source of this problem is that you are expecting your mailserver to honour a change in the from: address. The Mail Server people may not be happy with you to do that without some specific request as it is a spamming vector.
Gmail will allow different from: addresses if specific two way trust email-pong has been setup first. Without this, Gmail will just rest the outbound address to the default relating to the account you are sending through.
You need to talk to your Mail Server people and ask for your JIRA server to be allowed to masquerade as other users.
But. you need to be aware of course, that users will reply to such mails, so your inbound mail handler better be up to the scalability issues of that approach if they span physical mailboxes.
Thanks Andy for the extra info. One thing to note is that when I send an email from the "Send Email" administration screen, and modify the "Reply to" field, it works fine. And yet setting the project notification email doesn't seem to have any effect.
So, this looks like it's a bug, which I will log with Atlassian.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs