-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document sender address for notifications #38
Comments
Ah, how convenient, a notification just got sent 😁. So, notices@ is the address for new notifications, it seems. FYI: On my system (Office 365, Outlook) the last two notifications were both flagged as junk. I don't know if there is anything you can do about that, but I'm happy to provide an email, including headers, for further analysis if that helps. |
Please do! Thanks @malexmave |
Here's the headers of the message, as shown by Outlook Web Access (after I had already explicitly marked it as "not spam"):
|
Hi there!
I'm planning to hook up the bugalert email alerts to our Jira security service desk, which requires me to create a "customer account" for the sender of the message (otherwise the email will be discarded). Can you document somewhere which email address will be used to send the notifications? Is it a single address that is used for account verification and all future notifications, or are there different email addresses for different purposes, which would all have to be set up as customers in Jira?
Thanks for this awesome project, I really hope it takes off and sticks around :).
The text was updated successfully, but these errors were encountered: