The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We recently started testing a appended disclaimer for all inbound emails from external addresses.
There is an email alias that is used for creating tickets and a forwarding rule exists to forward the emails to the inbound Halp email address.
When Halp auto-replies to the user from that internal address, the disclaimer is appended because Halp's SendGrid email is responding on behalf of the internal address (and is authorized to do so).
What is the correct method for excluding this sender from getting the disclaimer appended to the emails without increasing up the risk for possible spoofing? Are there any identifying values in the Halp email headers that can be used to do this?
The current flow is:
Side note: DKIM and DMARC are being utilized as well to ensure that Halp is authorized to send on behalf of the "support@foo.com" account - if that helps give any more defining characteristics.
Hi Dan!
Halp does not have custom email headers, but you should be able to look at the DKIM Signature Headers and filter based on this value:
inbound.halp-mail.com
Let us know if that doesn't work!
Greetings, friends, Chances are if you’ve been spending some time in the online Community, you’ve noticed some members with the lozenge “Community Leader” next to their names. These folks are not m...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.