Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:timer:signalbymailreply
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:software:tim:timer:signalbymailreply [2018/03/05 08:42] Julian Le created |
en:software:tim:timer:signalbymailreply [2021/07/01 09:52] (current) |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| ==== Parameter ==== | ==== Parameter ==== | ||
| - | email, password, port, host, limit, moveFolder, piIdRegExp, pDName, NodeNameRegExp, firstline, box, decisionRegExp, signalSuccessMail, processVariable, transitions | + | email, password, port, host, limit, moveFolder, piIdRegExp, pDName, NodeNameRegExp, firstline, box, decisionRegExp, signalSuccessMail, processVariable, transitions new version: username, password, port, host, moveFolder, pDName, NodeNameRegExp, signalSuccessMail, processVariable, transitions, decisionRegExp |
| - | new version: | + | |
| - | username, password, port, host, moveFolder, pDName, NodeNameRegExp, signalSuccessMail, processVariable, transitions, decisionRegExp | + | |
| == 1. e-mail == | == 1. e-mail == | ||
| Line 49: | Line 47: | ||
| == 3. Port == | == 3. Port == | ||
| - | This provides information on the port corresponding to the e-mail address and the host. | + | This provides information on the port corresponding to the e-mail address and the host. Frequently used ports are: 110 //Pop// 995 //Pop including encryption// 143 //IMAP// 993 //IMAP with encryption// |
| - | Frequently used ports are: | + | |
| - | 110 //Pop// | + | |
| - | 995 //Pop including encryption// | + | |
| - | 143 //IMAP// | + | |
| - | 993 //IMAP with encryption// | + | |
| == 4. Host == | == 4. Host == | ||
| - | Host, e.g., pop3.gmail.com or imap.gmail.com (very often this will entail either pop or pop3 or IMAP. SMTP is far less common!). An IMAP mail box will be necessary if moving all e-mails to other folders. The kind of protocol to use is dependent on the mail box being employed. If both common protocols are supported by the web service, then IMAP should be selected as preferred protocol.</note> | + | Host, e.g., pop3.gmail.com or imap.gmail.com (very often this will entail either pop or pop3 or IMAP. SMTP is far less common!). An IMAP mail box will be necessary if moving all e-mails to other folders. The kind of protocol to use is dependent on the mail box being employed. If both common protocols are supported by the web service, then IMAP should be selected as preferred protocol. |
| + | |||
| + | <note important>Important: If you want to move mails to other folders, an IMAP mailbox is required. Basically, the use of the protocol depends on the mailbox. If both protocols are supported, then IMAP is to be preferred.</note> | ||
| <note important> It is highly recommended to use a separate mail box for each timer and process definition.</note> | <note important> It is highly recommended to use a separate mail box for each timer and process definition.</note> | ||
| Line 71: | Line 66: | ||
| == 7. nodeNameRegExp == | == 7. nodeNameRegExp == | ||
| - | NodeNameRegExp is a regular expression which provides clues on how to find the name of a node. The textual content of e-mails as well as corresponding subject headings will be scanned for this expression. | + | NodeNameRegExp is a regular expression which provides clues on how to find the name of a node. The textual content of e-mails as well as corresponding subject headings will be scanned for this expression. e.g., ++(.+)++ The element which has to be searched would be the nodeName included in brackets. For example: |
| - | e.g., ++(.+)++ The element which has to be searched would be the nodeName included in brackets. For example: | + | |
| <code> | <code> | ||
| Line 108: | Line 102: | ||
| found-no-node-for-signal-by-mail-reply\\ | found-no-node-for-signal-by-mail-reply\\ | ||
| signal-done-for-signal-by-mail-reply\\ | signal-done-for-signal-by-mail-reply\\ | ||
| - | found-no-process-instance-for-signal-by-mail-reply//Only the configuration using loom.properties would be possible in this case.\\ | + | found-no-process-instance-for-signal-by-mail-////reply//Only the configuration using loom.properties would be possible in this case.\\ |
| The correct answer has to be configured in the following way:\\ | The correct answer has to be configured in the following way:\\ | ||
| //signal-successful-signal-by-mail-reply// \\ | //signal-successful-signal-by-mail-reply// \\ | ||
| Line 127: | Line 121: | ||
| ---- | ---- | ||
| + | |||
| ==== Procedure ==== | ==== Procedure ==== | ||
en/software/tim/timer/signalbymailreply.1520235735.txt.gz · Last modified: 2021/07/01 09:55 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
