![]() I have already submitted the form (2 weeks ago) associated with that help article. Host aspmx.l. : 550-5.7.1 Our system has detected an unusual rate ofĥ50 5.7.1 our Bulk Email Senders Guidelines. ![]() Unfortunately, Google has yet to follow suit and we're still receiving the error below: Fortunately, all of the above have now removed us and we're able to send email to those servers, which is great. We we're on several Blacklists including Yahoo, Hotmail, Lashback, and Barracuda. We have since rectified the issue with the Spam (2 weeks ago). One of our servers was compromised about 2 weeks ago and a considerable amount of spam sent out. We're a web development company and host around 75 client's websites and email. I understand the need to be patient however as the others had removed us within a couple of days I was hoping Google would follow suit. Unfortunately it seems a large portion of our clients need to regularly contact Gmail users (or people using Google Apps) and just cannot do so at the moment. I have already submitted the form associated with that help article. To protect ourĥ50-5.7.1 users from spam, mail sent from your IP address has been blocked.ĥ50-5.7.1 Please visit http:/ Opens a new window / mail/ help/ bulk_mail.html to reviewĥ50 5.7.1 our Bulk Email Senders Guidelines. Host gmail-smtp-in.l. :ĥ50-5.7.1 Our system has detected an unusual rate ofĥ50-5.7.1 unsolicited mail originating from your IP address. ![]() SMTP error from remote mail server after end of data: We we're on several Blacklists including Yahoo, Hotmail, Lashback, and Barracuda.įortunately, all of the above have now removed us and we're able to send email to those servers, which is great. Unfortunately, Google are yet to follow suit and we're still receiving: We have since rectified the issue with the Spam (3 days ago). One of our servers was compromised earlier this week and a considerable amount of spam sent out. We're a web development company and host around 50 client's websites and email. Unfortunately we're in the "me too" club! If you have any questions about this process, please PM me and I will be happy to assist in any way I can. This will provide some level of future protection in the event my client gets hit with another spambot, etc., in that the Exchange server public IP should not be affected by the issues with the browsing public IP. I have since successfully removed the original public IP from all RBLs. So, I contacted my clients ISP and obtained a second public side IP address, setup a one-to-one NAT from the new public IP to the internal IP of the Exchange server, updated the DNS / MX / SPF / PTR records with the ISP and hoster, and the problem was resolved. I recently took over a client network with the same issue as yours and was running into road blocks at getting them delisted with a few of the more questionable RBL list providers. I do have a question: Is your Exchange server and browsing public IP address the same? If so, you may want to look into putting your Exchange server on a different public IP than the one everyone uses to surf the internet. Like you, I brag about Spiceworks to all my tech associates I have convereted a few already :) I am glad to see that other Spiceworkers are jumping in and helping out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |