Solved

Issue in Exchange server 2013 send /receive

Posted on 2015-02-23
9
471 Views
Last Modified: 2015-03-03
HI,
I have setup an exchange server 2013 cu7 on Windows 2012 R2 Standard.
I have seperate AD server running on the same OS mentioned above.

My Exchange installation was fine but aster installation i couldn't send and receive email from outside. Internal is working fine.

When i send to couple of external email ids like gmail i am getting error like
mx.google.com rejected your message to the following email addresses:

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.

mx.google.com gave this error:
[86.98.5.254 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for more information. qu4si7170968pbb.17 - gsmtp


Couple of emails are qued up and not sending.

Also  when i send email to my exchange user i am not receiving.

I tried Microsoft remote connectivty analyser and i am getting the error.

      Testing TCP port 25 on host mail.atomoptions.ae to ensure it's listening and open.
       The specified port is either blocked, not listening, or not producing the expected response.


I am using a fortigate firewall and using fortigate dyndns.
The domain is from 1and1 and i created the mx recored and it is pointing to the firewall.

I also done the port forwarding also.

Please help me in resolving the issue.


Thanks
Raneesh.A
0
Comment
Question by:Raneesh A
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 19

Expert Comment

by:Kash
ID: 40625654
have you got port 25 open on the firewall and nating/pointing to the exchange ?

are you able to send emails at all i.e: apart from google, have you tried sending to any other recipient. are you getting the same error message
0
 

Author Comment

by:Raneesh A
ID: 40625717
yes i have allowed all port to the exchange ip including nat..
i tried to send to another domain and is stuck in mail queue.
0
 
LVL 10

Expert Comment

by:nashiooka
ID: 40625774
The NDR was generated by Google, there for the mail did get sent and was bounced from outside your organization.  Therefore it's not likely to be a firewall issue.  It looks like Google thinks it's SPAM.  You could try hot mail or yahoo etc...  This would tell you a lot.
0
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

 

Author Comment

by:Raneesh A
ID: 40627463
my server name is atomex.atomoptions.ae and i changed the mx record as mail.atomoptions.ae (owa,ecp...) and created A record in dns server for mail and autodiscover to point to exchange server .


I tried sending to other domains and received error
Generating server: atomex.atomoptions.ae
Receiving server: mx00.1and1.com (74.208.5.3)
raneesh.a@inichesoln.com
Remote Server at mx00.1and1.com (74.208.5.3) returned '400 4.4.7 Message delayed'
2/23/2015 3:04:32 PM - Remote Server at mx00.1and1.com (74.208.5.3) returned '451-4.4.0 Primary target IP address responded with: "554-perfora.net (mxeueus002) Nemesis ESMTP Service not available 451-4.4.0 554-No SMTP service 451 4.4.0 554 invalid DNS PTR resource record." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 74.208.5.3:25'


For Hotmail

Generating server: atomex.atomoptions.ae
raneeshkalam@hotmail.com
COL004-MC1F40.hotmail.com
Remote Server returned '550 OU-002 (COL004-MC1F40) Unfortunately, messages from 86.98.86.75 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.'
0
 

Author Comment

by:Raneesh A
ID: 40627471
Also this the error i got from google when i tried to send an email to our exchnage user

Delivery to the following recipient has been delayed:

     raneesh.a@atomoptions.com

Message will be retried for 1 more day(s)

Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at http://support.google.com/mail/bin/answer.py?answer=7720
[(10) mail.atomoptions.ae. [2.50.42.138]:25: socket error]
0
 
LVL 11

Accepted Solution

by:
hecgomrec earned 500 total points
ID: 40628294
From your errors above I can tell you it seems your IP is Blacklisted.  Your emails are going out but there is an error on the SMTP transport.

Check all these:

Your public IP should be mapped (NAT) on your firewall to your internal server's IP (with all or required ports)
You must have public DNS and MX records matching your server's certificates (mail.atomoptions.ae or owa.ato....,etc)
You must be passing your SMTP communication to the same ISP.  You can't send over SMTP using an IP range from another ISP ( 86.98.86.75   --  2.50.42.138) and when I ping your server I got 86.98.4.224.  So make sure you are using the right server IP to send your SMTP.

Check you internal DNS and MX records to match your server's internal IP so when you look for mail.atomoptions.ae within your network you'll get your internal IP.
0
 
LVL 19

Expert Comment

by:Kash
ID: 40628553
NDR is normally received when your emails hit another server. It is telling us that you are on RBLs.

Try using a smart host first to rule out any NDR issues. If after using smarthost you can't send then I would start looking at other issues.
0
 

Author Comment

by:Raneesh A
ID: 40630149
I think my isp is blocking port 25.
When i tried smart host in send connector the emails are going. but not receiving emails to exchange  .
0
 

Author Comment

by:Raneesh A
ID: 40641267
Issue resolved . it was because of our dyndns .
0

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
Read this checklist to learn more about the 15 things you should never include in an email signature.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question