Emailing

There are 3 email plugins that may be ranked in this order, from best to worst:

1. "Email - Configuration Microsoft Graph REST API"

2. "Email - Configuration SMTP"

3. "Email - Configuration Outlook"

No 1. replaces "Email - Configuration Office365 REST". To use this clients would need to have an Office365 subscription. It's good because it is using modern tooling, and emails sent will appear in that users sent items in their usual email client. The downside is that an Office365 subscription costs money.

No. 2. requires the following details to be set on the plugin, regarding your email server:

• SMTPServerAddress

• SMTPServerPortNumber

• SMTPRequiresSSL

These details could be obtained from your current email client. This is a fair plugin, but SMTP can sometimes be tricky to get working because of firewalls, and confusion over what ports are supposed to be used. Emails sent will not appear in that user's Sent folder in their usual email client, however it will still be logged and available in Jiwa.

No 3. requires users to have Outlook installed as it uses the Outlook COM objects. It can sometimes not work properly in multi-user environments. Outlook must be the 32-bit version. Windows services cannot use this emailing mechanism. Emails sent will appear in that user's sent items in their usual email client.  It is not appropriate for remote desktop / terminal server environments as problems arise if Outlook is running for a different user to the one trying to send an email.

It's also possible to use a combination of all methods in the one database.  For example, you might want services, which generate automatic emails, to use SMTP, because you don't have an Office 365 account for those.  But your users would use their Office 365 account.

We call it, 'multiple email providers' and this is native in version 8

Emailing with multiple email providers in version 7 - Jiwa 7 - Documentation (atlassian.net)