On Monday morning messages sent via MailGun to our Office 365 account started to fail with the following message:
5.7.511 Access denied, banned sender[198.61.254.54]. To request removal from this list please forward this message to delist#messaging.microsoft.com. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653.
I checked on MX Toolbox and found their IP 198.61.254.54 listed in SORBS.
I cannot delist the IP from SORBS as the request has to come from the IP address which is listed.
I emailed the delist# address at Microsoft, who replied to say that the ISP/ESP is responsible for delistings.
I opened a ticket on Tuesday at 15:11pm with Mailgun support, asking them to delist the IP or change us to a different IP. It's now 15:42 on Wednesday and they have not acknowledged or replied to my ticket.
We send around 5,000 emails per month so are well under their recommended 50k+ threshold for a dedicated IP address.
Mailgun's control panel says:
For technical questions we recommend asking the community on Stack Overflow.
So here I am. What's my next move?
Mailgun support responded after 51 hours and said: "We have reviewed the error, and we have made adjustments on our side that will help solve this issue moving forward".
They had changed the shared IP address my domains were allocated to, and now mails are being delivered again correctly.
Another possible solution to this would have been for me to purchase a dedicated sending IP, although I was close to the lower recommended limit for this so I'm not sure if they would have improved deliverability in my case. I'm not sure if the purchase process for dedicated IPs is automated, or if I would have had to wait for a support agent to assign the new IP in any case.
Related
My company is using a FreePBX server for the inbound and outbound calls. The trunking service is using SIP station trunking. The sales and marketing team usually use the outbound call service. So the issue arise when they are making outbound calls, there is always the country code appearing at the receiving party.
At the extension configuration, the outbound caller id is set to <+65xxxxxxxx>. So the question is how can we remove this country code so the receiving party will only show XXXXXXXX as the caller id number.
Geolocation=SG.
*edits: *If i set outbound caller id to < XXXXXXXX>, the receiving party will receive call as +1XXXXXXXX as the sip station is US based.
Thank you.
There is no possible answer for this question. It depends of trunk provider you are using and their equipment.
But you should consider that if you are calling from abroad via international trunk - nation law will forbid what you are asking for.
You can get a local number and show that number on calling, will be local number. Sure you have call via trunk related to that local number for this country.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am using AWS SES to send out emails automatically through my application.
I have configured the Identity management as following:
DKIM is setup correctly. I have no issues sending emails from my domain except for GMX and WEB.de emails where I receive the following error:
Action: failed
Final-Recipient: rfc822; xyz#web.de
(mxweb111) Nemesis ESMTP Service not available
554-No SMTP service
554-Reject due to policy restrictions
Looking at further documentation, it seems that emails coming from my domain are classified as Spam by their servers.
I have done research and found that I might need to configure Reverse-DNS but as it looks like, AWS SES does not support this?
What else can I do to make my emails get through WEB.de and GMX servers?
Thank you.
I was in deep conversations with AWS SES support regarding this issue. This is the outcome:
I also would like to update you that SES internal team were able to confirm a deliverability issue with the recipient ISP and are actively working towards a resolution but we do not have an exact ETA at this time. Due to the nature of the shared IP pool, these types of blocks can happen periodically and we make every effort to resolve these issues as fast as possible. To prevent impact from these types of issues, it is always recommended to use dedicated ips for higher volume sending.
It means that the shared IP addresses used by AWS SES are blacklisted with GMX and WEB.de
AWS SES wants to resolve this.
In the meantime, they recommend to use dedicated IP addresses to solve this issue.
Please note that these IP addresses have to be "warmed up" in order to not cause trouble on the recipient end (e.g. spam folder issues).
Unfortunately, my sending volume is not that high (yet) so I have my fingers crossed I can get those emails send out easily. Otherwise I have to find another solution or need to wait for AWS so solve the blacklist issue.
I hope this helps anyone else.
Edit January 2021
I was able to send to GMX/WEB.de although my IP was only starting to warm up. Now after one month I am nearly at 100% with not many emails per day sendout volume.
Several e-mail services operated by United Internet (at least GMX, Web.de) seem to have blocked Amazon SES IPs. Validity of DKIM, SPF, DMARC does not seem to have any impact on the block. I'm seeing these rejections in my logfiles as far back as 2020-10-05.
The alternative of using a the dedicated IP address has its own challenges. Managing and warming up new IP addresses for delivery can be very painful (e.g., Outlook.com was known to accept and then silently discard e-mails after IP changes).
I would suggest to write to mailsecurity#info.gmx.net or use their contact form https://postmaster.gmx.net/en/contact. I've received a response from them, although they didn't seem to fully grasp the issue. Maybe more contacts will help them see the importance of addressing this. Until then I am informing my users per banner of the issue (and recommending alternative e-mail services).
Amazon support has not been helpful for me. I've received one first-level response which indicated the responder had not understood the issue at all, but promised to forward it to SES support. Since then I haven't heard anything for a week.
Edit: since 2021-03-24, there are no more 554-Reject due to policy restrictions failures in my logs. Seems that either GMX or Amazon have done something to address this problem.
We have a service responsible for sending emails using AWS SES. This is working pretty well since we deployed it. But one strange thing start to happen a day ago (April 22, 2020). We have change nothing from our side and start to receives a lot of emails from Amazon SES:
What we already know:
As it is happening with almost all emails we sent, not all users all
are clicking in the "unsubscribe" link
The users are receiving the emails, once we know they are clicking in
the links inside of the emails
The emails we sent two days ago are exactly the same emails we are sending today. Both content and configuration
If anyone have past for this kind of problem, any help would be great
I haven't encountered the report abuse but have encountered the related bounce email issue several times. Not much is useful from FAQ (https://aws.amazon.com/ses/faqs/) but it does mention the reputation dashboard which you should be following to see if you are on the road to recovery.
Your tasks include:
1) Investigating if you send an email that could be considered abuse/spam under local laws of the receiver
At a minimum, you need to make sure you are offering the capability to unsubscribe and actually unsubscribe users in timely fashion. But also review content with an eye on local laws.
2) Ensure that users who do not want to receive email from you are removed.
This should be part of above.
3) Build up your reputation by increasing the percentage of valid emails.
This has been an issue for us in systems that send a small amount of email...it takes time to build up from a dip.
Remember - AWS wants to ensure it's multi-tenant mail servers remain whitelisted and that other AWS customers aren't impacted by any one potential bad actor.
Anyone know how to get Mailgun's attention when they have a blacklisted IP? All my email is bouncing and there is no way to get support (for days) unless you get a very expensive plan with them.
I went to the "IPs" section of the Mailgun admin, but I am not allowed to remove the one (blacklisted) IP associated with my domain.
Sure wish I had gone with the competition at the moment.
From few months ago when i was using twitter, i was able to send twitter a SMS and when i go home and check my twitter page, i see the SMS i sent is on the website as a tweet. "That was great"
Now, i want to make the same in my website, so someone will send my website SMS as a command and my website will save this command in the db for future processing.
My problem that i don't know where to begin.
1- How users will send from around the world while there are different mobile companies in each country, or thats not a problem?
2- How my website will receive and read these SMS? there is a service for that?
3- Do you know any articles which simplify these tasks for me?
If someone worked on something like that before, please advice, any info will be helpful.
Contact your messaging provider, they will have solutions for each country they support.
In practice these things need to be agreed on a per-country bases (e.g. shortcodes etc), but the providers will do a lot to help.
Depending on what countries you want to cover, a single provider will probably do it - if you need absolutely every country with a mobile network, then you might need several, in which case integration is more complicated.
Typically they send either a HTTP POST, or a SMTP email to your server when they receive a message to your company's shortcode or shortcode prefix. But the integration options that exist are agreed per provider; there is no real standard or de-facto standard.
Well, first of all you need a sms-gateway. This is a service which you can buy a lot of places with varying prices. Your site can communicate with this gateway in different ways depending on the gateway-host.
Now, you can send messages to the number you bought on the sms-server and poll them (or push, again depending on your sms-provider) to your site. Just as with any other sms "IRL", you can use country codes to send a very costly SMS from around the globe. If you wish to keep this price lower, you need to rent a SMS-gateway which is internationalized or you need to rent one in each country...
.. In conclusion, doing this is not really a feasable option for your small "hobby-type" project :) Renting a SMS-gateway is rather cheap though, so the problem is really in your "multiple countries" request ..
I have created a web service for sending and receiving SMS messages. We are connecting through VPN to the SMS gateway of the local GSM operator: they have assigned us an public number as well as the option to send messages worldwide.
It doesn't matter if we send sms worldwide or receive from anyone - it just work :)
International sms might be a bit more expensive to send.
Edit:
theoretically there is a possibility to send sms thgrough an sip provider (like betamax /voipdiscount.com/) but this is not so fast and reliable comparing to traditional service.
I've had some success in the past with http://www.aspsms.com/
This is a paid service (per SMS) and be aware that you need to pay and FAX (yes, FAX...) your identity information to the before you get an API key.