Receiving mail issue in Exchange 2016
Hi Guys,
We having issues receiving mail in Exchange 2016.
We use a smart host to deliver mail to our Exchange 2016 server via port 25.
By means of the "Default Frontend" receive connector in Exchange.
Basic authentication is enabled, as well as Anonymous Users permissions group.
Scoping is the local IP of the smart host.
Mail is piling up in the smart host queue.
Receiving mail was working fine up to a recent power failure.
During troubleshooting, I found no authentication username & password configured in the smarthost.
Can a receive connector in Exchange receive mail from a smarthost via SMTP without authentication?
The smart host logs does not show any specific error related to Exchange not receiving the mails.
Using an Exchange mailbox to authenticate, should I use the format user@domain.local as the username to authenticate?
We having issues receiving mail in Exchange 2016.
We use a smart host to deliver mail to our Exchange 2016 server via port 25.
By means of the "Default Frontend" receive connector in Exchange.
Basic authentication is enabled, as well as Anonymous Users permissions group.
Scoping is the local IP of the smart host.
Mail is piling up in the smart host queue.
Receiving mail was working fine up to a recent power failure.
During troubleshooting, I found no authentication username & password configured in the smarthost.
Can a receive connector in Exchange receive mail from a smarthost via SMTP without authentication?
The smart host logs does not show any specific error related to Exchange not receiving the mails.
Using an Exchange mailbox to authenticate, should I use the format user@domain.local as the username to authenticate?
Did you make any changes to the default receive connectors created by exchange. if so, undo those changes. no changes are needed on the default receive connectors that exchange creates. Also if you are 3rd email gateway that receives your emails and then forwards them on to your company, you should only have to make sure that your perimeter firewall, gateway, load balancer, or whatever you are using knows that any port 25 traffic needs to be sent to the exchange server IP. smart hosts are used by the send connectors when sending email outbound, and not the receive connectors so smart host shouldn't have anything to do with the issue you experiencing.
ASKER
Thanks Guys,
I discovered that receiving mail in Exchange stopped due to back pressure. (disk space)
Smart host authentication was fine.
Upon investigation I found the log files to be extremely big, taking up lots and lots of disk space.
It seems that the Exchange backups did not flush the logs.
I moved the log files in the database folder to a different location (manually) in a desperate attempt to get the mail receiving up and running.
I will be investigating the backup (flush logs) option.
The logs seems to be growing at 150Gb's per day (40 users),
This seems very excessive, is this possible, or could there be something else wrong?
I discovered that receiving mail in Exchange stopped due to back pressure. (disk space)
Smart host authentication was fine.
Upon investigation I found the log files to be extremely big, taking up lots and lots of disk space.
It seems that the Exchange backups did not flush the logs.
I moved the log files in the database folder to a different location (manually) in a desperate attempt to get the mail receiving up and running.
I will be investigating the backup (flush logs) option.
The logs seems to be growing at 150Gb's per day (40 users),
This seems very excessive, is this possible, or could there be something else wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Authentication of smart host is based on its configuration. if you are using third party smart host services, then please ask them if we need to put authentication