Emails bounce backs.

We have a vps hosting a website for a client.

They are hosting mail onsite using exchange.

We have the mx records etc pointing to their server and this has been working for about 4 years without an issue.

Recently the client has been unable to send emails to any email address ending in @hotmail.com

Please find the error messages received below when trying to email.

Questions
1. The ip address (masked in this sample as XX.XXX.XXX.XXX) is the ip address of the vps.
So why this ip address would appear when someone is sending mail through their own ip address?

2. What do we need to do so our client can email @hotmail.com email addresses.

We can confirm the masked IP address is not blacklisted anywhere.

Thanks for your help.

The following organization rejected your message: mx4.hotmail.com.

Diagnostic information for administrators:

Generating server: sydneywebhosting.com.au

rejectedemail@hotmail.com
mx4.hotmail.com #<mx4.hotmail.com #5.0.0 smtp; 550 SC-001 (BAY004-MC5F18) Unfortunately, messages from XX.XXX.XXX.XXX weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors.>; #SMTP#
Cheryl LanderAsked:
Who is Participating?
 
DrAtomicCommented:
Another reason might be that the ISP your client is using has it's smtp server blacklisted.
I just had a look and yes, they sorbs had blacklisted their ip.

Delisting aside, it is important to find out why sorbs listed the ip. Check against their definition of spam http://www.sorbs.net/information/definition.shtml (and to as a help to explain this to your client; the internet and especially the email part of it is a self regulatory anarchy, you have no choice in the matter other then to adopt the policies that are being used by your intended delivery addresses and change your sending policies accordingly).

http://mxtoolbox.com/blacklists.aspx is a nice tool to check a lot of blacklists in one go, be sure to use the ip address that is being used to send mail though.

Or is the mail being send through a website on the vps (thus using the local smtp component)?
Yes this is the case. The email is being generated via a website. ( a simple registration form )

Ok, that explains why the vps IP is in the mailheader. The mailheader is stamped with each processing step, as the smtp component on the server send the mail that IP is regarded as the sender.

Workaround; use a different SMTP whilst the SORB issue is sorted. Either have a local relay server on your network that can be used in emergencies like this or add an ip to the server and have sendmail (or the smtp equivalent you are using) run on that for now.

The permanent (well for as long permanent is permanent on the internet) solution is to have the client comply with the sorbs standard.
0
 
DrAtomicCommented:
The mail is being bounced with code 550 SC-001

Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation. If you are not an email/network admin please contact your Email/Internet Service Provider for help.


This can have many reasons a common one however is using a SPF record which does not have the SMTP server defined that is being used to send the mail. Also you are saying that you are seeing your server IP as the sending IP, can it be that the client is using webmail (IMAP) to send his mail (thus use your local server to send it)? Or is the mail being send through a website on the vps (thus using the local smtp component)?

Another reason might be that the ISP your client is using has it's smtp server blacklisted.

As for the second question; if there is no SPF in place then have the client use a different SMTP server; that should resolve it.
0
 
Cheryl LanderAuthor Commented:
Hi DrAtomic,

Thanks so much for the quick response.

Also you are saying that you are seeing your server IP as the sending IP, can it be that the client is using webmail (IMAP) to send his mail (thus use your local server to send it)? Or is the mail being send through a website on the vps (thus using the local smtp component)?

They are using outlook on their own network. They are not using webmail. They do not have access to it as we have disabled mail in plesk.

They do not appear to have a spf record at all.

Another reason might be that the ISP your client is using has it's smtp server blacklisted.
I just had a look and yes, they sorbs had blacklisted their ip.

Or is the mail being send through a website on the vps (thus using the local smtp component)?
Yes this is the case. The email is being generated via a website. ( a simple registration form )
0
 
HariomExchange ExpertsCommented:
Check out the 4th reply here (reply with the most pluses)
http://answers.microsoft.com/en-us/outlook_com/forum/oemail-osend/please-contact-your-internet-service-provider/38318705-fb86-4f8d-9ebe-089c13bae099
Filling out the form you stated just help get our butt offs the problem this time, but not forever. PAIN huh!
0
 
Cheryl LanderAuthor Commented:
sorry Viralr.

what does this mean?
Filling out the form you stated just help get our butt offs the problem this time, but not forever. PAIN huh!

So in short we cant do much?

Thanx.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.