System-wide performance maintenance will impact support ticket submissions starting at 6pm CST on January 28th (11am AEDT on 29 January / 12am GMT on 29th January) and is projected to end at 10am CST on January 30th (3am AEDT on 31 January / 4pm GMT on 30th January). During this time, email support@advsol.com for help with urgent iMIS issues or email hosting@advsol.com for urgent assistance with hosting issues. We thank you for your patience.

Using Office 365 and iMIS for communication suite emails

 

iMIS 2017

How to configure O365 in the web.config to be used with iMIS communication Suite.

The smtp settings can be configured in both web.config files (Net & AsiScheduler) that are located in these sample folders' paths shown below. It is best practice to make back up copies of your web.config files prior making any changes.

Web.config for AsiScheduler:

C:\AsiPlatform\Asi.Scheduler_imis

Web.config for Net Folder:

C:\Program Files (x86)\ASI\iMIS\net

The default settings in the web.config files are typically as follows:

<mailsettings>
<smtp deliveryMethod="Network" from="xxx@xxxx.com">
<network host="127.0.0.1" port="25" defaultCredentials="true" />
</smtp>
</mailSettings>

The above <mailsettings> properties could be changed to any other email provider of your choice, or smart host. The great majority of providers such as O365 configuration will required you to authenticate with a real mailbox credentials to establish that connection.

Sample:

<mailSettings> 
<smtp from="user@xxxx.com"> 
<network host="smtp.office365.com" port="587" enableSsl="true" userName="user@xxxx.com" password="abc123" /> 
</smtp> 
</mailSettings> 

Note: Replace the above (user@xxxx.com) with the appropriate authenticated Office 365 email address

In regards to any limitations associated with Microsoft Office 365, please review this important article from Microsoft Office 365:

https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3

 

 

 

0 Comments

Article is closed for comments.
Powered by Zendesk