Troubleshooting problems related to in-bound emails

The following steps assume:

A user John (john@BusinessPartner.com) wants to send an email to Mary (mary@YourCompany.com)
John is a user on the Internet who may or may not use Xeams
Mary is a user on your network and her emails goes through Xeams

	Step 1 - John send an email to Mary. John's SMTP server receives the messages. Step 2 - Johns SMTP server does an MX lookup to find the IP address of Mary's SMTP server. If John's SMTP server is unable to find an MX record, it will generate an NDR (non-delivery report) back to John notifying the server is not found. Click here to see what could go wrong at this step
	Step 3 - Message passes through Mary's firewall. Click here for details Step 4 - Message is accepted by Xeams. Click here for details. Step 5 - Message passes through several filters. Each filter assigns a score. Click here for details. Step 6 - Message is saved in the local repository. Click here for details.
	Step 7 - Message is forwarded to the corporate email server. (Applies in Spam Filter or in Hybrid mode). Refer to the SMTPOuboundConversation.log file to see if a message was successfully accepted by the receiving server. You could also refer to any logging available in your corporate email server. Step 8 - Message is fetched by the user. (Applies in Stand Alone or in Hybrid mode). Messages are either fetched by using IMAP or POP3 protocol.