Incident report not being delivered to Gmail account.

Ollie
Brass Contributor
Jan 04, 2019
Not ideal as there about 10 of these reports.

they were set up because a forwarder was not set up on their corporate to private emails before they were given access and set their own passwords.
We cannot set up forwarders with logging into their accounts.

These people are external board members and need their hand held.
- ChrisHoardMVP
  MVP
  Jan 04, 2019
  Thanks Oliver
  
  It's a bit of a tricky one and I know it's not ideal. It's also awkward from a compliance perspective because ideally, you don't want corporate information going to personal accounts like GMail or Hotmail. There would be a business case to state that such reports should only go to a corporate mailbox and then both mailboxes configured, say, on the Outlook app which has app protection policies on them.
  
  You can always set up forwarders on their corporate account in the Exchange Online admin console by selecting recipients > user > and I think its delivery options. So you don't need to touch the mailbox/have login details to apply forwarding.
  
  I would still see if the shared mailbox (hidden from GAL) - forwarder actually works and delivers to the external user. It's not ideal by it may get around the 5322 compliance error. If the emails generated in the incident report have no From address then its going to be difficult to square that without delivering it somewhere else first.
  
  Best, Chris
  
  Best, Chris
  - Ollie
    Brass Contributor
    Jan 04, 2019
    Is it in any way possible to force emails generated in the incident report to have a From address? postmaster@investni.com
    Regards,
    Ollie

Forum Discussion

Incident report not being delivered to Gmail account.