I keep getting this error message from Clickfunnels when trying to send emails through Mailgun '421 Mailgun temporarily unavailable'
Is this me or Mailgun - i have used this route of many occasions previously and this is the first time I have seen this
Related
A day ago I was able to use oauthplayground to successfully receive push notifications to my specified URL. Now when I send another watch request, I get a 200 ok as a response in the oauthplayground response box, but checking logs at the address (AWS API Gateway + Lambda Proxy) there is no POST message from google. No sync message or anything.
I tried to use google python client to send a watch request and same thing occurs.
body={'type':'web_hook','id':"id123",'address':'https://myaddress.com/notifications'}
response = service.activities().watch(userKey='all',applicationName='drive',body=body).execute()
I get similar response as in oauthplayground
{'kind': 'api#channel', 'id': 'some_id', 'resourceId': 'resource123', 'resourceUri': 'https://www.googleapis.com/admin/reports/v1/activity/users/all/applications/drive?alt=json', 'expiration': '1594846986000'}
I am able to send a POST message through Postman to my url and I see a log of that in CloudWatch. I have tried multiple times to send watch requests but although they are 200 status ok, I am still not receiving anything at my endpoint.
Could there possibly be a limitation on how many watch requests I am able to receive? Is there a reason Google accepts the request, but is not sending it to my URL?
I am trying to send email message to a specific email address via the aws pinpoint. My from email address is verified. However, whenever I try to send the email it gives me an error "Failed to submit email message to ". I don't understand where am I going wrong with this.
#Krishna gave the right clue, however to be precise, all of the following must be true:
Your From email address is verified in Amazon Pinpoint/SES.
Either your To email address(es) is verified, OR you have requested Sending Limit Increase specifically for Amazon Pinpoint, not just SES.
In my case it was problem no. 2, I have increased my sending limit for SES but not Pinpoint yet. Amazon treats them somewhat differently, however the error message it gave me was totally undecipherable:
Message not sent: We weren't able to send your email message to someemail#gmail.com. Request Id 982 : Failed to send message.
Specifically, check the Pinpoint project's right sidebar here:
By default Pinpoint provides an sandbox environment.
In order to send emails you need to white-list your from email address as well. ( i.e. got to SES and verify the from email id as well)
You should them be able to send emails via Pinpoint.
The receiver should acknowledge to terms and condition that AWS can send automated emails.
Actually we are using GMAIL POP3 and found so many times mails do not fetch from POP into the OTRS so we checked Gmail and found mails are there and still that mails are not received into OTRS and after that mail if sender sends the mail again then we receive the mail into OTRS but still previous mail is missing in OTRS, so I have checked the logs into OTRS and no logs at that particular point of time or from that user then I checked header in gmail of that mail which is received in OTRS and which is not received in OTRS and no difference found in header of mail.
Any idea what else need to check or why it is happening?
Thanks in Advance.
Is there some dependence from attachment?
I have experience when email do not fetch from pop if attachment has large weight (more than 10-20 MB ).
I'm trying to use a Mailgun Campaign to help track emails sent through Mailgun. The links in the email get modified, as expected, so that Mailgun can collect stats on which links are getting clicked. However, the links are timing out.
Some of the clicks are definitely getting through (they are collected by Mailgun's Campaign tracking), but I'm also getting a lot of user reports of timeouts. Every time I try the links they timeout.
The Mailgun Domain and DNS Verification is all green, including the optional entries.
'Is it down' type services all says it's up: http://currentlydown.com/email.mg.dr2dr.ca
DNS resolution works, when I ping email.mg.dr2dr.ca, it resolves, but the requests all timeout.
I have started a ticket with Mailgun Support, but it's email support so I figured I would ask here to see if anyone has any ideas.
I am having issues with sending email from a verified email.
(asking it here, as for some reason I can't ask in AWS forum)
Setup:
The email XXX.mydomain.com is verified.
domain mydomain.com is verified (in domain list).
I am testing through 'Send email Test' in AWS.
The sender (from) is the verified email.
When I send to +DDVVF#mydomain.com+, it's fine (email is sent).
When I send to a different email (my-client#other-domain.com), I get an error message, containing:
Email address is not verified. (Request ID:
73ee3c33-ef6b-11e5-a37e-e5f5988f938c)
Should I also verify the TO emails I want to send?
It doesn't seem scalable, as I don't want to verify each TO separately.
Any ideas?
Thanks,
It seems you are still in the sandbox , you need to log in request with AWS to move you to Production.
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html