...
Expand |
---|
title | Create Message Source configuration assistance |
---|
|
Setting | Description |
---|
Name | Name of the message source | Type | Message source type | Preset | Presets which can be used to simplify the remaining configuration i.e. Host/Post | Host | Message Server's hostname or IP Address | Port | Message Server's port | Timeout | Connection to be timed out based on the configured time (seconds). Leaving this configuration blank would result the timeout to be 30 second | Username | Username to access the account | Password | Password to access the account | SSL | Does the connection use SSL? | SSL Certificate Validation | SSL Certification Validation | Check Server Identity | RFC 2595 specifies additional checks that must be performed on the server's certificate to ensure that the server you connected to is the server you intended to connect to. This reduces the risk of 'man in the middle' attacks. | Read Strategy | Read Unread and Mark As Read - Only the unread emails in the mailbox are to be processed and once read, they will be flagged as read (Default). Read All and Delete - All the emails in the mailbox will be read and deleted after they are successfully processed. NOTE: For example: UserA has been using Read Unread and Mark As Read read strategy for past 5+ months and currently has over 2000 emails residing in the inbox. However, the user has now decided to switch the read strategy over to Read All and Delete and the consequence of this turned out that all the mails residing in the inbox folder were processed by JEMHC which resulted to exceeding the allowance. For example: read strategy (in JEMHC) has been set to Read Unread and Mark As Read and the Mail Server (POP) has been configured to Delete Gmail's copy once it has been processed. The end result of this would be the processed mail will be deleted from the inbox as per configuration. |
|
...
Submit the connection settings once they have been successfully validated. Lastly, JEMH will ask you to enter the Inbound email address. Typically this would be the username used in the inbound mail server connection.
...
JEMHC is designed for maximum interoperability using the same mail protocols that Jira supports, namely POP/s and IMAP/s (as well as FTP). Native communication with Exchange using MAPI is not currently possible - Exchange does support POP/s and IMAP/s, so those services need to be enabled and surfaced through firewalls for JEMHC to access (see https://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx )
...
Info |
---|
Google Gmail troubleshooter1668960Gmail: Use email clients with IMAP or POP - topic3398031&ref_topic=3396281 Setting up IMAP folders in Gmail is pretty easy. The default Inbox works as expected, Gmail special folders can be accessed as follows: No Format |
[Gmail]/Important: No Format | TopLevel
Deeper |
Info |
---|
Microsoft Exchange - technetlibrary/jj657728(v=exchg.150).aspx |
Setup outbound mail sending
Info |
---|
smtp server overviewtechnet/magazine/2005.11.howitworkssmtp.aspxtechnet/library.aspx |
Now we will configure JEMHC to be able to send email notifications out to Jira users and also users without a Jira user account (we call them non-Jira users). The first thing to do is configure the outbound mail server connection.
...