Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I would like to set up my workmail to get an incoming email but, I cannot see how and I have this message:
Your domain's incoming mail is not enabled
I think the original asker has abandoned this thread. But it is an issue that many people are struggling with and nobody has a really good answer. So I am going to show the screenshot as Flux was asking in the comment.
I am known to answer my own questions here, so by me getting on the case I will hopefully be able to catalyze a definitive answer.
I am managing my domain with AWS Rout 56 also, and surprised that there is nothing in workMail to just automatically set this up. You see that there are 3 DKIM related CNAME records that are said to be "Pending". This is odd, because I had many other records that needed setup, and I set them up manually and hit the retry button and every time it was discovering the DNS change immediately. Only with these 3 records it keeps with this weird "Pending" status.
Definitely in my case that 72 hours issue should not be an issue, it's not about DNS propagation. There is something else about this DKIM which is causing the "Pending" status.
UPDATE: This "Pending" status has now (~4 hours later) gone to "Verified". So there is nothing wrong with the DNS settings any more. Still the message remains "Your domain's incoming mail is not enabled."
Another thing that has been said elsewhere was to check the SES rules. I had a little clash trying to set up SES rules before I discovered WorkMail, then I went to set up WorkMail but deleted my bad SES rules. So now I added one simple rule back:
Under SES "Configure Email Receiving" there is one rule set called INBOUND_MAIL. In that under "View Active Rule Set" I created one rule:
Recipients: c...t.org
Actions:
1. WorkMail Action
Deliver mail to WorkMail organization m-26...71
Which is the ARN of my WorkMail organization. So that's there.
Still, with all that it keeps saying inbound email is not configured. In Thuderbird I have set up outbound email with IMAP and SMTP just fine, but replying to the emails sent from the new organization will always bounce with:
550 5.1.1 Requested action not taken: mailbox unavailable
UPDATE: I haven't forgotten about this issue yet, still not figured it out, but I will and will report here.
Related
I´m trying to deploy a AWS EC2 Mac instance.
During the process of setting the instance up, I get asked to allocate a dedicated host for it.
When I try to do it, I keep getting the following message:
Your request for accessing resources in this region is being validated, and you will not be able to launch additional resources in this region until the validation is complete. We will notify you by email once your request has been validated. While normally resolved within minutes, please allow up to 4 hours for this process to complete. If the issue still persists, please let us know by writing to aws-verification#amazon.com for further assistance.
It´s been more than a day since I started trying, so the problem isn´t the 4 hours mentioned in the message.
Anyone has any ideas how to solve this?
Thank you!
Is the AWS account in which you are trying to provision those resources brand new?
Messages like the one you are seeing are usually seen in case the account in question hasn't been fully activated or lacks billing information.
If my assumption is correct check the root account email inbox for confirmation/verification email requests from AWS. And make sure that your credit card information is up to date.
When a review reply is updated, I'm able to receive push notification. But where as for new question, update question and answer to a question is not notified via push notification. I subscribed to all changes.
URL: https://mybusiness.googleapis.com/v4/accounts/{accountno}/notifications
Output:
I have given required permissions as well in pubsub settings
This is a bug.
I have reported this to the GMB API support multiple times - the new Notifications API has the same bug.
The four Q&A NotificationTypes (NEW_QUESTION, UPDATED_QUESTION, NEW_ANSWER, UPDATED_ANSWER) can be set, however GMB never sends Pub/Sub messages for them.
You can let them know here:
https://support.google.com/business/contact/api_default?hl=en
And hope that they create an issue here at some point:
https://issuetracker.google.com/issues?q=componentid:585921%20status:open
I don't have a ton of experience with Amazon SES. For a client of mine, I maintain a small subscription list (about 1300 people) and I use Amazon SES to send messages through from the WordPress blog that this group is subscribed to, whenever there is a new post. Every so often I get complaint notifications from Amazon, but there is no identifying info to tell me who the complaint is from so that I can remove them from my list. How can I use those emails (or some other part of SES) to effectively remove these recipients? I have no intention of sending to anyone who doesn't want to receive these emails (even if they have not unsubscribed on the blog directly), but I can find no way of addressing these complaints.
The messages contain (in addition to the content of the email), information like the following:
User-Agent: ReturnPathFBL/1.0
Abuse-Type: complaint
Arrival-Date: Thu, 17 Aug 2017 10:22:08 +0000
Feedback-Type: abuse
Version: 1
Source-IP: 54.240.27.23
Original-Rcpt-To: 8516be265e1454635b9a5885efb329a4#comcast.net
Original-Mail-From: 0101015defb6e57b-8068a1db-1011-407e-af0c-1bf96aa38c5f-000000#us-west-2.amazonses.com
Reported-Domain: comcast.net
UPDATE
This is maddening. I have now setup an endpoint on my server, and when subscribed to SNS topic I correctly receive logs that I have been subscribed. But then...NOTHING. I still get the useless emails, but I get zero SNS notifications, despite being verified. Still investigating.
UPDATE II
Success!! It turns out that setting up SNS (or email notifications) on the DOMAIN was meaningless. I had to set it up specifically on the EMAIL SENDING ADDRESS. This was CRUCIAL but not at all obvious (at least to me)
Your question been addressed in amazon blog.
https://aws.amazon.com/blogs/ses/tag/abuse-complaint/
Make sure you are following the procedure to handle bounces and complaints from amazon aws.
Setting up Meteor to use "out of the box" AWS SES is simple, and one can use native Meteor "Email" methods without modification.
Steps to implement this can be found here. Thanks to Brian
Shamblen for putting together a detailed answer.
But one caveat with the "out of the box" SES is you need to both verify the sender and receiver email address.
To remedy this, you can put in a request with AWS SES for what they call, Production Access.
And further, according to Brian Shamblen,
The process to get production access is rather complicated. One will
need to handle bounce and complaint notifications from SES and prevent
messages from being sent to those addresses in the future.
Question
What is the Meteor code involved in handling bounce and complaint notifications from SES and prevent messages from being sent to those addresses in the future?
EDIT: Made modifications to question for clarity.
Requesting production access is fairly straightforward. You just need to contact them and they usually give it to you in a couple of hours.
Information about the process is here: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html
Load up the URL : http://aws.amazon.com/ses/fullaccessrequest/ and let them know what you will be sending via Emails, for example if you will be sending transaction based email (verification of a transaction, etc)
With production access you can either send email from:
A specific verified email address, where you will be asked to click a link to an email sent to that address to verify you own it
Any email under an entire domain. Under this process you prove you own the domain by editing its DNS records to contain a 'key'.
Most use cases are covered under production access, they typically give you 2000 emails a day and rate limit emails to 5/sec (they queue them so the maximum send rate is 5/sec). If you need more than this you can contact them to raise this additionally.
The process of verification is to stop people quickly creating AWS accounts to mass-spam users. If they allowed this straight-off then AWS IPs would be looked at as spam by other email providers.
For bounce notifications, SES tracks these, and you have to make sure that you don't get an above average bounce rate. Typically these would come from sending unsolicited email, which I wouldn't advise sending via SES.
Production access is only approved by the AWS team. Wait a bit and they should easily give you 2.000 emails/day for free.
As per bounces-unsubscribes... You'll need to have the SES API notify you of each email address which has been 'marked' with such status.
You should store all those email addresses somewhere and tell your app not to send them ANYTHING else in the future.
I facing some issue related to Amazon SES Statistic ordering, actually my recent sending mail static are in middle of data record it should be at top or lower of the record so what is the reason behind it?
My Question is How i do a simple report status with how much emails returned, invalid emails and emails sent if the "GetSendStatistics" returns a unordered list?
You will need to sort the data yourself, by using the Timestamp field of SendDataPoint. Unfortunately, the list returning from GetSendStatistics is not sorted.
This happens because due to the characteristics and nature of sending e-mail over the Internet, it might take a different amount of time for a server to determine whether a message (or a set of messages) is confirmed to have bounced, or to be delivered for sure. Please refer to this thread at AWS forums for a similar question and some insight into the issue you are facing.