I am working on the initial set up of workmail in my account.
The mydomain.awsapp.com/mail login keeps redirecting me back to the login page.
I get the error message: 550 5.1.1 Requested action not taken: mailbox unavailable when trying to send to any of the configured workmail organization users from outside.
I do not see any permissions, or quota tab on the user edit screen.
Whatsmydns.net shows that my MX record has propagated.
I initially tried creating a "test domain" account. I created users. But still wasn't able to login to web interface. So, I thought maybe it was a test domain limitation. Then I added in the real domain. Now, I'm wiping it all away and will create the workmail environment specifying the domain right off the bat.
Went recreated everything. Removed workmail organization, recreated hosted zone, set domain to use DNS servers of hosted zone, re-setup amplify hosting, recreated workmail organization. Set default domain to mine. Created user. This go around I held off on creating the mail from domain. Still same problem. Login page redirects back to login page with good login credentials. If you give it bad credentials it does error.
Making progress. Documentation makes one think to check "remote user" when that is really an indicator of to create the mailbox or not. Removed remote user and am now able to login. Can send email out. Took quite a while, but did get my first inbound email.
AWS 官方已更新 2 年前
I initially tried creating a "test domain" account. I created users. But still wasn't able to login to web interface. So, I thought maybe it was a test domain limitation. Then I added in the real domain. Now, I'm wiping it all away and will create the workmail environment specifying the domain right off the bat.
Went recreated everything. Removed workmail organization, recreated hosted zone, set domain to use DNS servers of hosted zone, re-setup amplify hosting, recreated workmail organization. Set default domain to mine. Created user. This go around I held off on creating the mail from domain. Still same problem. Login page redirects back to login page with good login credentials. If you give it bad credentials it does error.
Making progress. Documentation makes one think to check "remote user" when that is really an indicator of to create the mailbox or not. Removed remote user and am now able to login. Can send email out. Took quite a while, but did get my first inbound email.
Added back in the from mail domain. Things seem to be working okay. Doing user migration with audriga now.