- 최신
- 최다 투표
- 가장 많은 댓글
Hi,
The error means you've hit the limit of mails per user or organization. I took a look at your account and I did not see any enforcement placed on it. WorkMail is a managed business mail and calendaring solution not meant for mass/automated mailing. So it seems your use case is not one for WorkMail but should be done via SES.
You can use both SES and WorkMail in conjunction, WorkMail for receiving mail and normal business mail communication and SES for mass and or automated mailing.
Kind regard, Robin
Hello,
Thanks for taking a look. I have been using WorkMail for years via Microsoft Outlook. What you said does not explain why I suddenly can no longer send emails. I have not hit any quotas as far as I know. My account is in good standing, I barely send any emails, and my storage is fine, etc. If WorkMail is "managed" I should be able to send emails via both the web client (https://webmail.mail.us-west-2.awsapps.com/workmail/?organization=myoranization), and Outlook. I should not have to mess with SES at all... Any ideas?
I'm getting this same issue. It doesn't seem to be unique as there are a number of threads about it. What is the fix? I am on us-west-2 for both Workmail and SES. Simulation emails work. But I am unable to send emails from workmail. SES support said it is not an SES issue and closed my case as well.
Any suggestions of how to fix this? it was working fine for a couple years and just stopped recently.
관련 콘텐츠
- 질문됨 7달 전
Hi,
That is good to hear you're able to send mail again. Some extra feedback, in the WorkMail console you can find metrics on how much mail you're sending. Another thing I forgot to mention. Any issues with you account might also lead to a restriction on the number of mails you can send.
Kind regards, Robin
Did you do anything specific that you did to fix it?
The credit card on the account had expired. It was not obvious because AWS did not notify me that it had or that they would block sending messages. It also did not reflect anywhere in the console that there was a block/restriction in place. After updating the CC it started working again.