IIS SMTP server will not relay

We have migrated to Office 365 and I am using this document to setup an SMTP relay for our copiers...
http://support.microsoft.com/kb/2600912

I have everything setup exactly as this suggests, but an email never arrives.  I have logging enabled on the IIS SMTP server and in the log file located at C:\Windows\System32\LogFiles\SMTPSVC1, I see this...

19:09:32 172.16.81.246 HELO - 250
19:09:32 172.16.81.246 MAIL - 250
19:09:32 172.16.81.246 RCPT - 250
19:09:32 172.16.81.246 DATA - 250
19:09:33 172.16.81.246 QUIT - 240

It looks like it is accepting the email, but I'm not sure what is happening after this.  How can I track this down further?
LVL 5
bpl5000Asked:
Who is Participating?
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
Is the to address one of the exchange mailboxes?
You can track messages with delivery reports
http://technet.microsoft.com/en-US/library/jj150554.aspx
0
 
bpl5000Author Commented:
Thanks for the response!  The IP address that the IIS SMTP server is accepting is the IP address of the copier.

I tried running a delivery report on the user I created as per step 2 of Microsoft's document.  I also ran a message trace on that account, but both the delivery report and the message trace show no messages by that user.  It looks to me like the SMTP server is accepting it from the copier, but when it tries to relay it thru the user account (which was setup in step 2), something goes wrong.  I'm not sure where else I can look in the EAC or on the IIS SMTP server side (maybe a log showing the SMTP server trying to pass the message onto Office 365?).

I thought about adding our public IP to Connection Filter/Allowed IP Addresses in EAC.  I wish there was some way to see if the connection from the IIS SMTP server is being refused by Office 365.
0
 
David Johnson, CD, MVPOwnerCommented:
you are getting an OK from exchange.. is the email address you are sending TO within your organization ?

250 Requested mail action okay, completed.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Mohd_ShaikhConnect With a Mentor Commented:
Suggestion:-

Enable the verbose logging on the Receive connector and check it out that what exactly is going on their.


Thanks!
0
 
Vasil Michev (MVP)Connect With a Mentor Commented:
Just run a message trace in the EAC:

http://technet.microsoft.com/en-us/library/jj200712(v=exchg.150).aspx

Also, the setup you did requires a valid Exchange license to be applied to the user you configured in the IIS SMTP relay settings. Not a big deal, but if you only want to send messages to internal recipients only, you can follow this article instead:

http://support.microsoft.com/kb/2799338
0
 
bpl5000Author Commented:
ve3ofa, we are NOT getting an OK from Exchange, that OK is from our IIS SMTP server.  The TO address is within our organization as far as being part of OurDomain.org, but it is with Office 365, NOT an on premise Exchange server, but I think that should be obvious from what I stated above.

vasilcho, as stated before I did run a message trace in the EAC.  The message doesn't show at all... I'm assuming the message is rejected when the IIS SMTP server tries to transfer it to Office 365.  I could try your suggestion for not setting up a user for the relay, but it's not really internal because it's going from our on premise IIS SMTP server to our Office 365 tenant out in Microsoft's cloud.

Mohd_Shaikh, it's Office 365, not our own Exchange server.  I know how to setup verbose logging on the receive connector in EMC of our old Exchange server, but I do NOT see how to setup such logging on the EAC of our Office 365 tenant.  If you know how to do so, please advise.
0
 
bpl5000Author Commented:
Ok, so I changed the logging from the default IIS log file format to NCSA Common log file format and now I can see what happens when the SMTP server tries to hand off the email to our Office 365 tenant.  Right away I noticed the sending email address was not a valid address.  It did not matter before because we were using Exchange and would allow anything from that IP address.

As soon as I saw that email address in the log I said, "D'oh!"  I put in a valid email address and now it's working!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.