-
Bug
-
Resolution: Fixed
-
Low
-
38
-
Severity 3 - Minor
-
When sending emails via SendGrid the domain 201701confluence.atlassian.net is used as a sender.
Authentication-Results: spf=none (sender IP is 168.245.48.17) smtp.mailfrom=201701confluence.atlassian.net; arivale.com; dkim=pass (signature was verified) header.d=atlassian.net;arivale.com; dmarc=permerror action=none header.from=arivale.atlassian.net; Received-SPF: None (protection.outlook.com: 201701confluence.atlassian.net does not designate permitted sender hosts)
This causes issues as 201701confluence.atlassian.net does not have a valid SPF record:
$ dig -t txt 201701confluence.atlassian.net @8.8.8.8 +multiline +short "wildcard-placeholder" $ dig -t txt 201701confluence.atlassian.net @9.9.9.9 +multiline +short "wildcard-placeholder" $ dig -t txt 201701confluence.atlassian.net @208.67.222.222 +multiline +short "wildcard-placeholder"
- is duplicated by
-
JRACLOUD-72132 Notifications from filter shares may be blocked due to SPF fail
- Closed
- is related to
-
JSDCLOUD-8592 Service Desk customer notifications are being marked as SPAM
- Closed
- relates to
-
JSDCLOUD-5614 JSD Notification were not sent out due to failed DMARC/Marked as SPAM. Add option to control the Reply-To: header in Jira Cloud
- Closed
- has action
-
MSGI-2599 Loading...
- mentioned in
-
Page Loading...