Mailbox troubleshooting · Practical guide
Gmail alias sending identity: verify authorization and the received From
Separate a configured Gmail alias from the identity a third-party sending application actually uses.
Reviewed · Examples are illustrative
Who this helps: Mailbox owners and administrators validating sending and reply access.
Define the decision
An alias visible in Gmail webmail does not prove that Zintara’s connected mailbox sends through that alias. Inspect the resulting account identity and a received message rather than assuming every webmail Send as setting carries over.
Work through the procedure
- Identify whether the address is a Workspace alias, another Gmail account or a third-party address.
- Verify the provider-side alias setup and ownership.
- Check the connected identity available in Zintara.
- Send a controlled message and inspect From, Reply-To and authentication; reply to verify routing.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Webmail alias: [email protected]
Connected account: [email protected]
Received campaign From: [email protected]
Conclusion: the tested application path did not use the aliasRead the result
Google’s current help page announces a January 2027 change for third-party-address Send as support, while stating Workspace aliases and owned Gmail addresses are unaffected. Keep those categories separate when planning.
Check before moving on
- Check what the recipient actually sees.
- Confirm replies return to a mailbox the application reads.
Limits and next action
The reviewed Zintara connection is not a general Gmail alias-management interface. Do not promise an alternate sender until its end-to-end behavior is verified.
Source: Google: alternate sending addresses and announced changes
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features. Check current provider guidance before changing mailbox configuration.
Related guides
- Connect Google Workspace to Zintara and verify both directions →
- Gmail IMAP access troubleshooting: separate account policy from folder scope →
- Google OAuth app access blocked: identify the policy owner →