Please contact your support team if you have a question or need assistance for any Rackspace products, services, or articles.
We're using rackspace hosted emails for multiple domains.
We're having email rejected due to secure.emailsrvr.com being listed on spam block lists
The IP address being listed is 188.8.131.52
Listing confirmed at http://www.uceprotect.net/en/rblcheck.php
emails bounced back contain msgs like:-
host mail.hone.net[184.108.40.206] said: 550 5.7.0 550 Server
IP 220.127.116.11 listed as abusive. See
http://www.linuxmagic.com/power_of_ip_reputation.html for more information.
Protection provided by MagicSpam 1.0.8-1.1 http://www.magicspam.com (in
reply to RCPT TO command)
said: 554 5.7.1 The message from (<removed>)
with the subject of (RE: removed.) matches a
profile the Internet community may consider spam. Please revise your
message before resending. (in reply to end of DATA command)
Does anyone know how to avoid this, eg using alternactive smtp addresses?
That IP is tied to a relay, or outbound mail server, in our system. Many IPs can tie back to secure.emailsrvr.com, and this is dictated by our load balancer. We are aware of the blacklist and are awaiting it's removal.
In the meantime as a work around you can ask if the recipient can safelist the sender, sender's domain, or that IP. What would also be helpful is if you create tickets with the bouncebacks so that we can add the ticket as an affected user on our internal tracking system.
Regards,Alison OsterTechnical Community Manager
I saw this and wanted to add the following information that you might be unaware of:
Rackspace also employs numerous spam filtering and internal controls to help prevent our IP’s from ending up on any blacklists. However, no prevention method is fool-proof and from time-to-time this can happen. We do apologize.
About the process and time frame:
Please note that all blacklists are managed by different owners. There is no central entity that you can contact and ask for removal from all blacklists, so we have to approach the individual blacklist owner via the method that they have set up to request de-listing.
Note that some lists operate fully automatically and do not accept removal requests. In case of these blacklists, the listed IP address will be removed automatically, once a certain period of time elapses. Obviously, this requires that the IP address no longer expresses the behavior because of which it became listed in the first place.
Some blacklists are well-run, and generally considered “legitimate”; meaning that the data they store regarding an IP or domain’s reputation is accurate and accepted as a valid source of reputation. In addition, they also provide an avenue to request de-listing and these requests are handled in a timely and professional manner. These blacklists are the “good guys” and most major email providers subscribe to these services because of this.
Other blacklists are run poorly and are considered “borderline legitimate”. These can be riddled with mistakes, poor practices, security holes and operational problems. De-listing from these can be a difficult and time-consuming process, if there is even a path to request de-listing. Sometimes, even getting a response from some of these is precarious.
Then there are blacklists that are run from a purely monetary motive. These blacklists are completely illegitimate and will arbitrarily list in order to obtain a ransom, which must be paid before de-listing can occur.
Rackspace is familiar with working with most of these blacklist providers and while we can’t guarantee fast de-listing with any blacklist, we do our best to work with legitimate (and when necessary borderline-legitimate) blacklists and their requirements in order to de-list as quickly as possible. We really don’t want you to negatively affected by a blacklisting any longer than necessary.
In the meantime, we recommend reaching out to any of your recipients through another channel (if available) and make them aware of the situation. It would speed things along if the recipients do want to receive your email and can report the messages as “false positives” to their mail providers or email administrators. The fastest way for them to begin receiving your email again would be to see if they can “safelist” (also known as “whitelist”) your domain name.
Hope this adds a bit of insight into the problem. Thanks for your understanding and patience.
Hi CarlTwo months ago we created a ticket related to IP ranges and IP addresses blacklisted by UCEPROTECT, Level 2 and level 1, and the issues has not been solved yet.Unfortunately in many cases requesting to be whitelisted is not an option. For some customers, seriously affected by this problem, we have contracted external SMTP services for them to process outgoing mail, but it is not reasonable to have to maintain an external smtp service. Also it is not good that we had to request those customers to change outgoing configuration for all their email clients.In some cases using an external SMTP service is not enough, because when they access trough webmail mails sent to server that uses uceprotect lists are bounced.We have also installed roundcube webmail for some customers that depends on webmail.Really this is not reasonable at all.We understand Uceprotect policies are rude but all mail providers have to deal with them and most of them find the way to avoid hiting uceprotect spamtraps.This is not the first time we experience issues related to ip´s blacklisted by uceprotect. It has been a recurrring issue for the last 18 monthsHope you can find a definitive solution soon.Thanks