If your e-mails disappearing somewhere else externally or internally while doing and verifying all stuff try these
1- Server Network connectivity
2- Server DNS settings from server NICs and pinging exchange servers from another server/system with their host names. Try disabling IPv6 if entirely you're using IPv4 addresses for network connectivity
3-Smart Host Blacklist. Check your domain here: http://mxtoolbox.com/
4- If only externally you're not receiving mails then this must be an issue with Smart host, try send connectors directly through mx records.
5- send connectors values
6- Cross check receive connector values for frontend exchange server.
7- Check your firewall ports forwarding. Is it mapping exernal IP to exactly frontend exchange server local IP?
8- If above All steps resulted status OK , try testing now with telnet because that could be the issue with connectors
telnet mail.port25.com 25
helo
ehelo
mail from: nabil@techie.com
///if here it says 530 5.7 1 client was not authenticated then definately this could be the issue with connector enable anonymouse access and cross check send and recive connectors all parameters value
rcpt to:helpdesk@domain.com
OUTPUT:
220 Exchange.Domain.com Microsoft ESMTP MAIL Service ready at Mon, 18 Apr 2016
10:32:14 +0300
helo
250 Exchange.domain.com Hello [37.X.X.X]
ehlo
250-Exchange.domain.com Hello [37.X.X.X]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
mail from:nabil@techie.com
250 2.1.0 Sender OK
rcpt to:nabil@techie.com
550 5.7.1 Unable to relay //this is because rcpt domain is different
rcpt to:helpdesk@domain.com
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
♥
Also verify exchange server services and running status
9-Exchange server console commands
Open Exchange server and type these to verify status and also check exchange server logs
[PS] C:\>Test-ServicesHealth
[PS] C:\>Test-ServicesHealth | FT Role,Required,RequiredServicesRunning -AutoSize
//then verify output
[PS] C:\> Test-Mailflow -TargetEmailAddress helpdesk@domain.com
//then verify output
[PS] C:\>Test-SMPTConnectivity -Identify exchange-domain.com
References: (Don't mind if I mentioned below some material, references, Solutions based on different scenerio for my personal use and can help you guys too. )
http://exchangeserverpro.com/exchange-server-2013/
send/receive connectors
https://www.youtube.com/watch?v=---_nBPFJIU
Solution 2
http://www.petenetlive.com/KB/Article/0000723
Installation
https://www.youtube.com/watch?v=3Nre0kDoV-w
Migration
https://www.youtube.com/watch?v=NW64KdTHTFA
Once connector is configured ask you exchange admin to run this command
Get-ReceiveConnector "Your Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
SOLUTION---
http://exchangeserverpro.com/exchange-server-2013-upgrade-fails-due-to-receive-connector-conflicts/
SOLUTION--------
https://community.spiceworks.com/topic/314850-exchange-server-2013-default-receive-connectors
LAST-HOPE(If you deleted accidentally receive connectors )
http://mike-graham.co.uk/blog/2013/08/16/exchange-2013-on-premises-receive-connector-settings/
https://social.technet.microsoft.com/Forums/exchange/en-US/32e13998-a84e-4f10-8557-3f7ce6fdb824/2013-default-receive-connectors?forum=exchangesvrsecuremessaging
Solution: Restart the transport service with a few hours interval, nahh don’t think so. Exchange 2013 is brand new and should work, and before the migration you had the exact configuration with Exchange 2010 server.
IMP solution: I very simple. remove the old receive connector and create a new one, but connect it against the frontend transport instead of the default Hub transport (backend).
Transport system has been running fine as it should for a couple of weeks now. I believe this is a bug in the transport service and the symptom is selecting the wrong receive connector when there is an incoming connection to Exchange.
It makes sense to connect receive connectors and possibly send connectors against frontend (CAS server) but I think it should work equally fine if you select the backend (mailbox server) especially when the backend is the default option when using Exchange Admin Center.
Connector details-concept
http://markgossa.blogspot.com/2016/01/receive-connector-selection-exchange-2013-2016.html
http://www.servolutions.com/support/config_exchange_2013.htm
Important: You also need to make sure to not install the Windows "Simple Mail Transfer Protocol" service. This service could block the Exchange SMTP transport from actually answering the SMTP IP port (25) and could cause Emails to loop back to the internet if installed. Check Administrative tools, Services and disable this service in case it is installed
SMTP SOLUTIONS
https://exchangemaster.wordpress.com/tag/smtp/
http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-server-2013-sp1-transport-service-stops-and-does-not-restart.html
Common errors:
530 5.7.1 Client was not authenticated
No comments:
Post a Comment