erichflynn Absent Member.
Absent Member.

Auto-forward vs invite/delegate cross-post

I believe I found why this is happening. The individual wrote the rule so that ANY item received, would invite their 3rd party personal email.

This didn't happen with delegate (GW2012). It appears to have been replaced with invite (GW2014) that has a different behavior.

Does anybody know what the change from delegate to invite was? There must be a different RFC for it and Why was this renamed?

Also if you disable auto-forward rules at the GWIA will it also disable auto-delegates and/or auto-invites?

>>> Erich D. Flynn<> 4/1/2016 4:09 PM >>>

We are having an issue with people that have an auto-forward rule on their account.

When it forwards the message everyone sees the external email address on the To: line, even though the original sender didn't have the address in their email. The same thing occurs with appointments, it adds the individuals external address to the appointment.

We have our GWIA configured with Flat-Forward

Is this expected behavior?
Labels (1)
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: Auto-forward vs invite/delegate cross-post


Here's an explanation of Delegate vs Invite:

I'll do some further digging for you.

Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.