Due to a merge, we have domain A under one Google Apps acccount, domain B under another one. I can create accounts for all the users in domain B to domain A to start a migration afterward. Adding aliasses with domains under account A is no problem.
However, sending email as the account under domain B (which users can request manually with their account, the account in domain B will then be mailed with the question whether they want to allow it) doesn't seem possible with the Admin SDK:
Any email address which exists as a user or an alias on the hosted domain.
Is there any way to start the process users would enter into when manually requesting to be allowed to send mail as that other user / email address?
Migrating the domain to it first is out of the question as apparently, a domain has to be completely shut down before it is allowed to be added to another Google Apps account.
It is not possible to configure a "send as" via API if the original sender belongs to another domain. I cannot see a "click to complete" way for the users. A quick guide for them or some web scraping / Selenium could help you.
Maybe, if it were a domain alias or a subdomain instead of a different Google Apps account, you could.
Have you contacted Google Apps Support regarding this issue?
Related
We have an app whose domain is on Godaddy, the frontend (ReactJS) is hosted on Firebase and the backend (Django) is on AWS. We follow subdomain-naming just like Slack does i.e. xyz.ourdomain.com. However, for every customer we have to do these manual steps and wait for hours for records to propagate:
Add an A record to Godaddy where e.g. Name would be XYZ and Value would be the value provided to us by Firebase when we add a custom domain there which is Value: 151.101.1.195 (Firebase shows this message there: Your site will show a security certificate warning for a few hours, until the certificate has been provisioned.)
Then we need to authorize our domain URL xyz.ourdomain.com on Firebase and Google Cloud Console (however that is not a major worry for now)
The last step is some customisation from backend which is necessary and can be automated by me easily
I just want to know how to create wildcard entries so that when one enters *.ourdomain.com, it points to the Firebase hostings. Ideally, we want to remove the time it takes for records to propagate.
This level control is not built into firebase as it is designed to work as your primary domain app, as such you can redirect all subdomains in your DNS to point to your root domain with the following guide:
Log into your GoDaddy account.
Click “Domains.”
Click “Manage DNS.”
Click Add and select CNAME from the dropdown list.
Complete the fields listed:
Host: The host name should be set to the wildcard (" * ").
Points to: This is the URL you are setting as the destination for the host. ...
Click “Save.”
You additionally have the option for 301 permanent redirects.
Our company uses different Google services (one of them being GCP). We are going to move our e-mail accounts to another mail supplier and we are wondering what the impact will be on the existing GCP services that certain users use. To make it clear our #companyname.com mails are currently hosted by Google and they will be moved to another supplier.
Will the users (identified by their e-mail address) keep on working "seamlessly" with GCP even we do not use Google's mail anymore?
Thanks in advance.
Posting this community wiki answer for better usability.
John Hanley wrote:
If you are using Google Workplace for email and for Google Cloud IAM, you will NOT be able to move those identities to another email platform without keeping the Workplace account. The authentication must be handled by a Google account (Gmail, Workplace, Identity Platform).
You can move your email (send/receive) to another platform. It is the authentication/authorization part that must stay with Google. You can have email for your domain hosted by another provider and still keep Google Workplace. Otherwise, you will need to create new Gmail or Identity Platform identities for Google Cloud IAM.
I wanted to setup my cloud identity but its asking me to verify the domain that is already hosted on GCP. Can you help me with Cloud Identity setup with a proper organisation created (today its named "No Organisation"). I'm the admin for this account DOMAIN: we host our Corporate website on GCP with domain already registered with DNS services in google.
on the GCP Identity page its also giving me the following message.
Your current account, k*****.***a#DOMAIN.NL, is not associated with an organization on Google Cloud. This checklist is designed for administrators who are trusted with complete control over a company’s Google Cloud resources. If you already have an administrator account for your organization, sign in with the account now. Or, ask your company administrator to start the checklist.
I guess I'm stuck in a Chicken-n-Egg problem.
You need to create a Google Workspace account. Create it on your domain DOMAIN.NL, with you as 1st admin user and with subscription plan or not (in my case, I wasn't able to remove the 15 days of trial. Get it, you will be able to remove the trial subscription later (in the user list) on the admin.google.com Workspace console). You are able to create your org for free, but it's absolutely not clear!!
From the new user account that you have created on your Workspace domain (you#DOMAIN.NL), you will be able to reach the console (console.cloud.google.com) and you have your org.
Now you need to migrate the projects and to review the authorization. You also need to (re)create a Billing Account.
I didn't find another way to achieve this.
I'm working with a client right now that has a legacy application hosted by a 3rd party vendor on their amazon account. That legacy app was using Amazon SES for their mailing.
I created the clients own amazon account (as I don't have access to continue the build out on clients account), and am now seeing the issue where I need to transition the SES DNS validation over to their account.
I'm wondering what kind of downtime I would see, or problems I'd create by updating the DNS entry of _amazonses.mydomain.com from what it was on the past account to this new account.
My concern is by updating that entry, I would break the legacy system which I don't have the ability to update.
Thank you
You don't have any downtime, you can verify the domains in two different account, it just you need to add multiple TXT value to the record "_amazonses.mydomain.com".
e.g: _amazonses.mydomain.com
"txt-value-1"
"txt-value0-2"
As long as your clients are using their own credentials, emails flow just fine, once you confirm everything is good, you can remove your record from there.
If no,
You can still use SES sending authorization and allow them to use the domain verified in your account, doing this, they can only use your sending domain to send emails but emails will go from their account and they will be charged, their account should be in production.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-authorization.html
I'm building a service where the end users can create organizations. Other users may then be added to the organization, and each organization may have a number of administrators.
The service is built on AWS.
Now, when an organization is created, I'd like to automatically create an email address corresponding to the organization, and forward all messages sent to this address to the external e-mail addresses of the administrators of the organization.
So for example let's say the domain of my service is example.com, and Alice (alice#somewhere.com) creates an organization called Foobar. She also adds Bob (bob#somewhere.com) as a second administrator.
I'd then like to register admins-foobar#example.com as a valid mailbox, and whenever someone sends e-mail to this address, it should be forwarded to alice#somewhere.com and bob#somewhere.com, ideally also with the reply path set to the original sender, so that Alice and Bob can answer support questions.
The purpose of this is to have a single point of contact for support issues etc for all the users within an organization.
I've used AWS SES and AWS WorkMail in the past, mostly for transactional mail, notifications and for statically created incoming mailboxes for support etc, but I cannot seem to find if what I want is possible to do through the AWS SDK.
First of all, I'm not sure if what I want to do requires AWS WorkMail at all or if this is somehow possible to solve using AWS SES and trigger rules, but I first looked at WorkMail. The AWS WorkMail SDK enables creating users and enabling mailboxes for them through the SDK, and users are grouped into organizations. However, I cannot find a way to create organizations through the SDK, only through the AWS web console!
Second, I cannot find how I can programmatically set up e-mail rules for forwarding e-mail sent to the created users' mailboxes.
Is this possible at all using AWS services?