Changes for page IMAP-Plugin

From version < 4.1 >

edited by MKO
on 30.03.2020, 17:35

To version < 9.1 >

edited by MKO
on 30.03.2020, 17:47

< >

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -6,8
          +6,8 @@
  == Functionalities ==
--; mmediate notification
--: Via the {{smallcaps}}}Imap{{/smallcaps}} interface the user is immediately informed about new or changed form entries.
++; Immediate notification
++: Via the {{smallcaps}}Imap{{/smallcaps}} interface the user is immediately informed about new or changed form entries.
  ; Configurable content
  : The content of the notifications as well as their subject, sender and recipient fields can be freely configured using corresponding templates. Since [[placeholders>>doc:Formcycle.UserInterface.Variables||target="_blank"]] can be used here, links for re-display directly within the mailbox can be created in addition to individual values or metadata of the form input.
  ; Provision of files
@@ -17,7
          +17,7 @@
  ; Manage form entries
  : In addition to the actual display, there are also options for managing form entries. For example, a form entry is moved to the corresponding {{formcycle/}} mailbox when it is moved to another folder. Furthermore, the read status is also synchronized. The deletion of form entries is also possible by deleting the corresponding message or by moving it to the trash, if the user has the appropriate authorization. If this authorization is missing, the message reappears in the e-mail program after a few seconds.
--The provided {{smallcaps}}Smtp{{{/smallcaps}} server is currently without functionality, so sent messages are completely discarded by it.
++The provided {{smallcaps}}Smtp{{/smallcaps}} server is currently without functionality, so sent messages are completely discarded by it.
  == Installation ==
@@ -40,67
          +40,47 @@
  {{id name="server_config"/}}
  ; smtp.binding.address
--: Default value: //0.0.0.//. Specifies the {{smallcaps}}ip{{/smallcaps}} address of the {{{smallcaps}}Smtp{{{/smallcaps}} server to use. The default value is //0.0.0.0//, which uses an automatically generated {{smallcaps}}ip{{/smallcaps}}. Changing this value is only necessary if multiple network adapters are in use or the automatic detection fails.
++: Default value: //0.0.0.//. Specifies the {{smallcaps}}ip{{/smallcaps}} address of the {{smallcaps}}Smtp{{/smallcaps}} server to use. The default value is //0.0.0.0//, which uses an automatically generated {{smallcaps}}ip{{/smallcaps}}. Changing this value is only necessary if multiple network adapters are in use or the automatic detection fails.
  ; smtp.binding.port
  : Default value: //25//. Specifies the port of the {{smallcaps}}Smtp{{/smallcaps}} server to use. The default value should only be changed if this port is not available.
  ; imap.binding.address
  : Default value: //0.0.0.0//. Specifies the IP address to use for the {{smallcaps}}Imap{{/smallcaps}} server. The default value is //0.0.0.0//, which also uses an automatically generated {{smallcaps}}ip{{/smallcaps}}. Changing this value is only necessary if multiple network adapters are in use or the automatic detection fails.
--: Default value: //143//. Specifies the port of the {{smallcaps}}Imap{{{/smallcaps}} server to use. The default value should only be changed if this port is not available.
++: Default value: //143//. Specifies the port of the {{smallcaps}}Imap~{{/smallcaps}} server to use. The default value should only be changed if this port is not available.
--=== Configuration of the e-mail message ===
++=== Configuration of the e-mail message ===
  {{id name="message_files_config"/}}
  ; mail.to.template
--: Default value: //mail_to.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail recipient.
++: Default: //mail_to.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail recipient.
  ; mail.from.template
--: Default value: //mail_from.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail sender.
++: Default: //mail_from.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail sender.
  ; mail.subject.template
--: Default value: //mail_subject.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail subject.
++: Default: //mail_subject.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail subject.
  ; mail.body.template
--: Default value: //mail_body.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail content.
++: Default: //mail_body.txt//. Specifies the name of the file to be searched for in the client and form files and to be used as a template for the e-mail content.
--== Configuration of e-mail contents and fields ==
++== Configuration of e-mail contents and fields ==
--The configuration of the contents and fields of the actual message uses a template mechanism. This is based on the four files set in [[e-mail message configuration>>||anchor="message_files_config"]]. These are imported as a client file when the plugin is installed and are used when synchronizing the messages.To ensure a form-specific display, it is possible to create identically named files manually as form files and thus overlay the client files.  In all files it is possible to use [[placeholders>>doc:Formcycle.UserInterface.Variables||target="_blank"]] so that form data sent here can be displayed. It is also possible to create a link to display the filled out form.
++The configuration of the contents and fields of the actual message uses a template mechanism. This is based on the four files set in [[e-mail message configuration>>||anchor="message_files_config"]]. These are imported as a client file when the plugin is installed and are used when synchronizing the messages.To ensure a form-specific display, it is possible to create identically named files manually as form files and thus overlay the client files. In all files it is possible to use [[placeholders>>doc:Formcycle.UserInterface.Variables||target="_blank"]] so that form data sent here can be displayed. It is also possible to create a link to display the filled out form.
  ; Content
--: Default value: //mail_body.txt//. Specifies the content of the e-mail message. Only here you have the possibility to use {{smallcaps}}Html{{/smallcaps}}. Example:
--
--{{code language="html"}}
--  <html>
--  <head></head>
--  <body>
--    <p><a href="[%$FORM_INBOX_LINK%]">Link</a> to form entry ([%$PROCESS_ID%]).</p>
--  </body>
--</html>
--{{/code}}
--
++: Default value: //mail_body.txt//. Specifies the content of the e-mail message. Only here you have the possibility to use {{smallcaps}}Html{{/smallcaps}}.
++Example: {{code language="html"}} <html> <head></head> <body> <p><a href="[%$FORM_INBOX_LINK%]">Link</a> to form entry ([%$PROCESS_ID%]).</p> </body> </html> {{/code}}
  ; Subject
--: Default value: //mail_subject.txt//. Specifies the subject of the message.  Example:
--
--{{code language="none"}}
--  ID: [%$RECORD_ID%] - [%$STATUS_NAME%]
--{{/code}}
--
++: Default value: //mail_subject.txt//. Specifies the subject of the message.
++Example: {{code language="none"}} ID: [%$RECORD_ID%] - [%$STATUS_NAME%] {{/code}}
  ; Recipient
--: Default value: //mail_to.txt//. Specifies the recipient of the message. This is to be entered according to the pattern //name <user@example.com>// and has no effect on the actual receipt of the message. Example:
--
--{{code language="none"}}
--  XIMA FORMCYCLE <no-reply@example.com>
--{{/code}}
--
++: Default value: //mail_to.txt//. Specifies the recipient of the message. This is to be entered according to the pattern //name <user@example.com>// and has no effect on the actual receipt of the message.
++Example: {{code language="none"}} XIMA FORMCYCLE <no-reply@example.com> {{/code}}
  ; Sender
--: Default value: //mail_from.txt//. Specifies the sender of the message. This must be entered using the pattern //Name <user@example.com>// and has no effect on the sending of the message.  Example:
++: Default value: //mail_from.txt//. Specifies the sender of the message. This must be entered using the pattern //Name <user@example.com>// and has no effect on the sending of the message.
++Example: {{code language="none"}} [%$PROJECT_NAME%] <[%$PROJECT_NAME%]@example.com> {{/code}}
--{{code language="none"}}
--  [%$PROJECT_NAME%] <[%$PROJECT_NAME%]@example.com>
--{{/code}}
++== Configuration of the e-mail program ==
--== Configuration of the e-mail program ==
++Für die Konfiguration des E-Mail-Programms sind neben der Adresse des E-Mail-Servers die unter [[Konfiguration des E-Mail-Server-Services>>||anchor="server_config"]] hinerlegten Ports zu verwenden. Die kompletten zu verwendenden Anmeldedaten setzen sich demnach wie folgt zusammen:
--Für die Konfiguration des E-Mail-Programms sind neben der Adresse des E-Mail-Servers die unter [[Konfiguration des E-Mail-Server-Services>>||anchor="server_config"]] hinerlegten Ports zu verwenden. Die kompletten zu verwendenden Anmeldedaten setzen sich demnach wie folgt zusammen:
--
  ; {{smallcaps}}Smtp{{/smallcaps}} server
  : //<server address>//
  ; {{smallcaps}}Smtp{{/smallcaps}} port
@@ -116,12
          +116,12 @@
  ; Authentication
  : Password, normal
  ; SSL encryption and connection security
--: none
++: none
--== Example configuration for Thunderbird ==
++== Example configuration for Thunderbird ==
--1. Open the e-mail account management via //Extras// > //Account settings//.{{lightbox image="thunderbird_1.png" group="g0" width="300"/}}
--1. Via //account actions// > //add email account...// open the dialog for configuring a new account.{{lightbox image="thunderbird_2.png" group="g0" width="500"/}}
--1. Initially, Thunderbird tries to determine a server automatically based on the entered email address (here //user@imap.com//). Since this is not possible here, you can cancel this by clicking the //Edit Manually// button.{{lightbox image="thunderbird_3.png" group="g0" width="500"/}}
--1. The corresponding data can now be entered in the following interface of the server configuration. In the example, the client name is //imap.com// and the user name //user// and the standard ports are used.{{lightbox image="thunderbird_4.png" group="g0" width="500"/}}
++1. Open the e-mail account management via //Extras// > //Account settings//.{{lightbox image="thunderbird_1.png" group="g0" width="300"/}}
++1. Via //account actions// > //add email account...// open the dialog for configuring a new account.{{lightbox image="thunderbird_2.png" group="g0" width="500"/}}
++1. Initially, Thunderbird tries to determine a server automatically based on the entered email address (here //user@imap.com//). Since this is not possible here, you can cancel this by clicking the //Edit Manually// button.{{lightbox image="thunderbird_3.png" group="g0" width="500"/}}
++1. The corresponding data can now be entered in the following interface of the server configuration. In the example, the client name is //imap.com// and the user name //user// and the standard ports are used.{{lightbox image="thunderbird_4.png" group="g0" width="500"/}}
 . After completing the configuration, the user's mailboxes now appear as folders (here //central mailbox// and //demo mailbox//) and contain the messages of the existing form entries.{{lightbox image="thunderbird_5.png" group="g0" width="700"/}}

Changes for page IMAP-Plugin

Summary

Details

Navigation