SMTP settings test fine, no mail delivery

I have a program on an MFP that uses SMTP to send emails through MS Exchange 2010 R3 server. My SMTP settings test fine and the emails go through my program without any failure. However, the emails are not being delivered. There are no indications of a failure throughout the entire delivery process (from MFP program to Exchange Server) and delivery reports from my program indicate messages as being sent. They seem to simply disappear somewhere. MS Exchange Troubleshooting Assistant also indicates emails as being delivered but they most definitely are not being delivered.

I've run out of ideas and fixes to test. Is there perhaps another application on my server that could be blocking the emails? If so, wouldn't I get an "email failure" notification from somewhere? Is there specific applications I should be looking for?

Thank you in advance for any help given.

August 11th, 2015 10:01am

Hello

check smtp receive connector log
if not set auth on MFP need new receive connector with anonymous access and add mfp ip to scope and test again.

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2015 1:37pm

1. check your queues first

2. if you know the sender address configured on the application, try to track the emails. so that you can easily come to know where the email got struck. use the below script to track the emails. it will create a CSV file with the tracking result.

Get-Exchangeserver | where {$_.isHubTransportServer -eq $true -or $_.isMailboxServer -eq $true} | Get-Messagetrackinglog -Recipients "rece@domain.com" -sender "sender@domain.com" -Start "7/2/2012 08:00 PM" -End "7/2/2012 09:30 PM" | Select-Object Timestamp,Clienthostname,eventid,source,sender,@{Name="Recipients";Expression={$_.recipients}},Recipientcount,serverhostname,SourceContext,messagesubject | Export-Csv c:\temp\Messageinfo.csv

August 11th, 2015 2:00pm

Hi Meethius,

Appears to be corrupted mail.que database issue.

    • Stop the Microsoft Exchange Transport service by running the following command:
    • net stop MSExchangeTransport
    • Move the existing database files Mail.que and Trn.chk from the original location to the temp location.
    • Move the existing transaction log files Trn.log, Trntmp.log, Trnnnnnn.log, Trnres00001.jrs, Trnres00002.jrs, and Temp.edb from the old location to the temp location.

    • Start the Microsoft Exchange Transport service by running the following command:

    net start MSExchangeTransport

    New DB is created and mail flow resumes.

Follow this article for more detailed process:

http://msexchangeguru.com/2011/06/02/mail-que/

Change the location of the queue database:

https://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).as

August 12th, 2015 1:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics