Skip to content

Fixing a 403 error when pushing signatures to a Gmail alias

The Gmail Pusher alias 403 error occurs when a signature is pushed to an email alias instead of the primary email address. For example, to aliasusername@opensense.com instead of primaryusername@opensense.com.

The push fails for that user, with a 403 error that shows the primary email address the signature can be sent to (primaryusername@opensense.com).

Pusher result marked failed for one user, with a 403 Delegation denied message that names the user's primary email address, and No Signature Found

A second failed push, with a 403 Delegation denied message naming a different primary address

  1. Note the primary email address shown in the 403 error.
  2. Push the signature again, to that primary email address.

Once the admin confirms a successful push, impacted users should make sure that their primary email address is selected in their Gmail signature settings as well.

Gmail signature settings with the pushed signature, and the Signature defaults for new emails and for replies and forwards

If you have any concerns or questions, contact help@opensense.com to find the best resolution.

Screenshot preview

Screenshot