[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 675
  • Last Modified:

can't send out email addressing to internal email address

Hi Experts,

We use our Exchange 2003 sever as our scan job forwarding server.   scan job email was sent to our company email address.  Now it wouldn't work.  But we found that we can receive the scan email in Yahoo mail or any other addresses except of our company's email address.  

Please advice.

Thank you very much in advance.

Enjoyroot
0
EnjoyNet
Asked:
EnjoyNet
  • 3
  • 2
2 Solutions
 
Justin YeungCommented:
what do you mean scan job? it is from a multifunction printer?

usually there is an account in the printer which to access the smtp server. check if the account is locked out. or password expired, etc.
0
 
EnjoyNetAuthor Commented:
Yes, it is a MFP.  Since I can receive scan job email in my Yahoo.  So the account is not locked and pass is not expired I believe.  

Thanks
0
 
herbusCommented:
Can you take a look at the SMTP logs for Exchange and see if there is an error code associated with any attempt to send to internal addresses?

The SMTP logs will typically be in your Exchange install location, under a folder called "server-name.log".

Did this used to work but suddenly stopped?  If so, any changes around that time?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
EnjoyNetAuthor Commented:
Herbus,

The log contains no error or may be I don't know how to read it. I tried to search for Error in the log and found nothing.   Yes, it just stopped working 10 days ago.  We didn't change anything.  

Thanks

Enjoyroot

0
 
herbusCommented:
I guess that all other internal mail is OK - just mail from the MFP is not delivering..?

Maybe I've jumped ahead of myself - check out this article and see if you can check the IIS SMTP logs rather than the Exchange specific entries I mentioned.  The IIS SMTP logs are a little less convoluted and will still let you establish whether mail connections from the MFP are making it to Exchange for your internal staff, or show a status code (sc-status column) that we can look into...
http://www.msexchange.org/tutorials/Logging_the_SMTP_Service.html

The Exchange logs I pointed you to are explained well enough here:
http://www.msexchange.org/tutorials/Exchange-2003-Message-Tracking-Logging.html
...with a link at the bottom of the article to another page showing some error codes:
http://www.msexchange.org/tutorials/Exchange_Server_2003_Message_Flow.html

There's a bit of troubleshooting you'll need to undertake, but I hope this gets you somewhere.  You need to search IIS or Exchange logs for the IP address of the MFP, then look for entries that contain one of your internal addresses that didn't get the mail.  From there, the status code or message tracking should be able to tell us where it went (or didn't)...
0
 
EnjoyNetAuthor Commented:
I chose another mail server for forwarding.  Thank you for your help.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now