iMIS Communication Suite and Office 365 emails are sent but not recieved by the recipient

NOTE: This article is intended for those using iMIS 2017 (20.2.65).

If iMIS communications are not being received by Office 365 recipients, then review the following information.

Review the web.config file

Ensure the web.config files for Net & AsiScheduler are set identically under the <mailsettings> section on both web.config files using the correct O365 Account info. Reference this other public knowledge base article for more details when configuring your smtp settings for iMIS  Communication Suite using O365. Click here.

If iMIS Communication Suite is displaying the message was sent and delivered, then that typically entails the email was relayed out through the smtp protocol (internet), and it should have gone out successfully.

There may be other subtle concerns with the emails once they are in transit in the internet to the recipients' mail server. Often times messages could have potentially be caught as false positive. See How do I report a suspicious email or file to Microsoft?

A "false positive" is a legitimate email message that was incorrectly identified as spam. Because of the high volume of submissions that we receive, we may not be able to answer all requests for analysis. Admins can send email, url, and attachments to Microsoft for review. See Admin submissions in Office 365 ATP 

Other example, it could be related to the actual messages being force to the junk folder in the recipient's mail client such as (outlook, gmail, etc). See Use mail flow rules to see what your users are reporting to Microsoft in Exchange Online.

Similarly, important is to ensure adding the iMIS App server's IP address to the allow list in your O365 (Admin - Exchange) portal. See Configure connection filtering.

See also How to set up a multifunction device or application to send email using Microsoft 365 or Office 365.

Compare the options

Here's a comparison of each configuration option and the features they support.

Features

SMTP client submission

Direct send

SMTP relay

Send to recipients in your domain(s)

Yes

Yes

Yes

Relay to internet via Microsoft 365 or Office 365

Yes

No. Direct delivery only.

Yes

Bypasses antispam

Yes, if the mail is destined for one of your Microsoft 365 or Office 365 mailboxes.

No. Suspicious emails might be filtered. We recommend a custom Sender Policy Framework (SPF) record.

No. Suspicious emails might be filtered. We recommend a custom SPF record.

Supports mail sent from applications hosted by a third party

Yes

Yes. We recommend updating your SPF record to allow the third party to send as your domain.

No

Saves to Sent Items folder

Yes

No

No

Requirements

 

 

 

Open network port

Port 587 or port 25

Port 25

Port 25

Device or application server must support TLS

Required

Optional

Optional

Requires authentication

Microsoft 365 or Office 365 username and password required

None

One or more static IP addresses. Your printer or the server running your LOB app must have a static IP address to use for authentication with Microsoft 365 or Office 365.

COMPARE THE OPTIONS

 

Limitations

SMTP client submission

Direct send

SMTP relay

Throttling limits

10,000 recipients per day. 30 messages per minute.

Standard throttling is in place to protect Microsoft 365 or Office 365.

Reasonable limits are imposed. The service can't be used to send spam or bulk mail. For more information about reasonable limits, see High-risk delivery pool for outbound messages.

0 Comments

Article is closed for comments.
Powered by Zendesk