Skip to content

fix(gmail): allow Workspace native aliases with empty verification status#407

Merged
steipete merged 2 commits intoopenclaw:mainfrom
salmonumbrella:fix/issue-406-workspace-alias
Mar 7, 2026
Merged

fix(gmail): allow Workspace native aliases with empty verification status#407
steipete merged 2 commits intoopenclaw:mainfrom
salmonumbrella:fix/issue-406-workspace-alias

Conversation

@salmonumbrella
Copy link
Copy Markdown
Contributor

@salmonumbrella salmonumbrella commented Mar 4, 2026

Summary

  • allow --from when a configured send-as alias has empty verificationStatus but is Gmail-managed (no custom SMTP relay), matching Google Workspace native alias behavior
  • keep rejecting explicit unverified statuses such as pending
  • apply the same validation logic to both gmail send and gmail drafts create
  • add regression tests for send, drafts, and the shared send-as validation helper

Fixes #406

Testing

  • make fmt
  • make lint
  • make test

@steipete steipete force-pushed the fix/issue-406-workspace-alias branch from 81ffb6a to 9bac0cc Compare March 7, 2026 14:56
@steipete steipete merged commit 4abcd03 into openclaw:main Mar 7, 2026
2 of 6 checks passed
@steipete
Copy link
Copy Markdown
Collaborator

steipete commented Mar 7, 2026

Landed via temp rebase onto main.

  • Gate: make ci
  • Land commit: 9bac0ccec3fdd940b9844f7aa272d7935d1077e2
  • Merge commit: 4abcd03

Thanks @salmonumbrella!

klodr pushed a commit to klodr/gogcli that referenced this pull request Apr 22, 2026
…atus (openclaw#407)

* fix(gmail): allow workspace native aliases for --from

* fix: land Workspace alias send fix and changelog (openclaw#407) (thanks @salmonumbrella)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--from blocked for Google Workspace native aliases (shows as unverified in API despite being valid)

2 participants