Not receving email from GoDaddy

Dear Experts

Please can someone assist me. My domain is not receiving email from another domain that is hosted with GoDaddy. They also have their email hosted with GoDaddy. I can send email to them fine. We just cant receive from them. Their server attempts to connect to ours but then for some reason just drops.

Mail flow into my environment:
Internet -> company firewall -> Cisco Ironport -> Exchange 2010 server

On my ironport there are no entries logged for even a connection attempt from their server.
On my firewall however I can see their server attempts to connects but we only receive bytes worth of data, 777, 843, 777, 843. There seems to be a pattern.

Refer to attached image.
Firewall log
Any ideas?
TTAF4Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
TTAF4Connect With a Mentor Author Commented:
Hi Jason

Thank you for your reply.

196.34.160.78 is the public ip of my ironport.

I have eventually found out what's wrong. The sender (abgafrica.com) has a very poor reputation on their public ips.
0
 
Lisa Hendrickson "CallThatGirl"Connect With a Mentor MS Outlook ExpertCommented:
Not sure if this is helpful or not...Have you contacted them and ask for 2nd level support? They can put in a request with the engineers.

My last black list experience left me with about no hair left. Once I sent out a newsletter, I got on their own blacklist. I could not email anyone at GoDaddy (even the clients I moved to their hosted exchange!). I had to put in many requests and complain and finally it was lifted.
1
 
Jason CrawfordExchange EngineerCommented:
First you'll want to run some message tracking:

Get-ExchangeServer | Where-Object {$_.isHubTransportServer -eq $true -or $_.isMailboxServer -eq $true -or $_.IsClientAccessServer -eq $true -or $_.IsEdgeServer -eq $true} | Get-MessageTrackingLog -Sender xxx -Recipient xxx -Start xxx -End xxx | Sort-Object -Property Timestamp | Format-List | Out-File "$env:USERPROFILE\Desktop\track.txt"

Open in new window


Replace the 'xxx' in the script with the appropriate values.  Note the start and end dates should be a day before and a day after the email was actually sent.

I'm not confident you'll find anything here but just in case.  Next move on to the transport logs.  For this next section you'll want to enable verbose logging on the Receive Connector used to receive email from GoDaddy.  If you're not sure which RC this applies to just enable it on all of them, I do this anyway with every Exchange server I deploy:

Get-ReceiveConnector | Set-ReceiveConnector -ProtocolLoggingLevel verbose

Open in new window


Once logging is enabled, have the sender send another email so it can be captured in the logs.  Give it about an hour after the email is sent before moving on to the next step.

Open up the path to the transport logs:

C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive

The date should be in the file names so open the log for the date the email was sent and just search Notepad for the WAN IP or sender address.  Please report back your findings and we'll keep digging.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
TTAF4Author Commented:
Thank you both for your prompt replies. I am going to open up a support ticket with GoDaddy. Will let yall know the results.
0
 
TTAF4Author Commented:
ok I eventually managed to get hold of GoDaddy. The reason I am not receiving email from them is because my MTA has a poor reputation.
0
 
Lisa Hendrickson "CallThatGirl"MS Outlook ExpertCommented:
Did they offer help on how to resolve this?
0
 
Jason CrawfordConnect With a Mentor Exchange EngineerCommented:
Why would they care who they deliver email to?  Reputation is for sending email not receiving.  Did they provide any documentation to back this claim up or is this just what they told you?  Were you able to run the tracking commands I sent over?
0
 
TTAF4Author Commented:
20161103 02:19:40.047 core sid="2EAQc51nKEj0t" id="2EAQc51nKEj0t2EAQcZyxp" ip="46.252.205.172" action="PERMERR" dstmta="196.34.160.78" age="62" code="554" reason="554-is-ironport-01.ttaf.co.za\r\n554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.\r\n" account="mani.i@abgafrica.com" fwd="0" bounce="false" mailfrom="mani.i@abgafrica.com" fromdomain="abgafrica.com" recipient_list="navishkar.sadheo@ttaf.co.za" todomain="ttaf.co.za" subject="Test - please reply " subject_hash=12739b92f271f580b15764215c6dc880 script="none"

i am the recipient here.
0
 
Jason CrawfordConnect With a Mentor Exchange EngineerCommented:
Ok so the recipient Ironport device rejected the email due to a 554 error.  I looked up the 196.34.160.78 IP address, and while it is not on any blacklists, it originated from Mauritius.  International IPs are often blocked by devices like Ironport so you will have to work with the recipient to bypass the filter.
0
 
TTAF4Author Commented:
Found the  problem on my own.
0
All Courses

From novice to tech pro — start learning today.