Search results

  • | <nowiki>Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co
    300 KB (41,181 words) - 07:10, 9 July 2015
  • ...bmail, desktop clients, or mobile apps, your users will receive your email communication on all devices. [[Category: Communication]]
    2 KB (329 words) - 07:50, 8 June 2022
  • For inter-OX-communication over the network, multiple Open-Xchange servers can form a cluster. This br It's required to define the network interface that is used for cluster communication via ''com.openexchange.hazelcast.network.interfaces''. By default, the inte
    58 KB (8,939 words) - 14:04, 30 January 2020
  • ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co ...the java function getHostName will be used. This name is used for internal communication. </nowiki>
    271 KB (37,062 words) - 13:43, 1 July 2015
  • |Communication error with Facebook service: %1$s |A communication error occured while processing the free/busy request ("%1$s").
    213 KB (27,569 words) - 14:38, 15 August 2013
  • ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co ...the java function getHostName will be used. This name is used for internal communication. </nowiki>
    231 KB (31,760 words) - 11:29, 16 April 2013
  • ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co ...the java function getHostName will be used. This name is used for internal communication. </nowiki>
    247 KB (33,845 words) - 11:37, 16 August 2013
  • ...nternal components, plugin capabilities, public interfaces (APIs) and data communication streams of the Open-Xchange server. =<span style="background:#dcdcdc">Frontend and client based communication flow </span>=
    7 KB (1,153 words) - 05:53, 20 June 2018
  • ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co ...the java function getHostName will be used. This name is used for internal communication. </nowiki>
    268 KB (37,155 words) - 12:16, 21 October 2015
  • * Enabled Hazelcast for inter-OX-communication, see [[AppSuite:Running_a_cluster]] for details
    22 KB (3,224 words) - 13:19, 18 December 2023
  • ...ng App Store. Availability will be confirmed by Open-Xchange via the usual communication channels.
    4 KB (596 words) - 09:04, 13 July 2022
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    351 KB (48,276 words) - 15:48, 31 January 2017
  • | <nowiki>Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co
    280 KB (38,131 words) - 21:26, 5 March 2014
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    347 KB (47,794 words) - 13:34, 31 January 2017
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    366 KB (50,420 words) - 07:11, 29 September 2017
  • | <nowiki>Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co
    293 KB (39,973 words) - 13:36, 1 July 2015
  • ...e ticket system (OTRS). The ticket system provides additional features for communication between you and Open-xchange, but it is not meant as a full substitution of ...requirement, customers and support agents have to keep the readable ticket communication, in form of email/article body, subject or attachment names, free from any
    5 KB (836 words) - 11:26, 2 September 2019
  • ...ge of our people, the power of their collaboration, and the success of our communication; we look at all potential acquisitions with this in mind.
    7 KB (1,105 words) - 08:38, 19 March 2015
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    321 KB (44,146 words) - 07:59, 2 December 2015
  • ...unning.<br/>But the client is not connected to the server directly.<br/>As communication channel between both nodes JMS is used. * 1x JMS Server for communication
    23 KB (2,471 words) - 10:59, 2 October 2015
  • ...unning.<br/>But the client is not connected to the server directly.<br/>As communication channel between both nodes JMS is used. * 1x JMS Server for communication
    32 KB (3,487 words) - 15:29, 12 January 2016
  • ...products/appsuite/stable|pc2n=debianname|pc2v=DebianSqueeze|backend|office-communication|calcengine}} ...ianSqueeze|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    858 bytes (109 words) - 14:08, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianWheezy|backend|office-communication|calcengine}} ...bianWheezy|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    856 bytes (109 words) - 14:10, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianJessie|backend|office-communication|calcengine}} ...bianJessie|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    856 bytes (109 words) - 14:11, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLES11|backend|office-communication|calcengine}} ...c2v=SLES11|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    851 bytes (110 words) - 14:12, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLE_12|backend|office-communication|calcengine}} ...c2v=SLE_12|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    851 bytes (110 words) - 14:14, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL6|backend|office-communication|calcengine}} ...pc2v=RHEL6|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    824 bytes (107 words) - 14:15, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL7|backend|office-communication|calcengine}} ...pc2v=RHEL7|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    816 bytes (107 words) - 14:17, 12 January 2016
  • ...products/appsuite/stable|pc2n=debianname|pc2v=DebianSqueeze|backend|office-communication|calcengine}} ...ianSqueeze|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    853 bytes (109 words) - 14:41, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianWheezy|backend|office-communication|calcengine}} ...bianWheezy|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    851 bytes (109 words) - 14:34, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianJessie|backend|office-communication|calcengine}} ...bianJessie|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    851 bytes (109 words) - 14:34, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLES11|backend|office-communication|calcengine}} ...c2v=SLES11|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    854 bytes (110 words) - 14:36, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLE_12|backend|office-communication|calcengine}} ...c2v=SLE_12|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    854 bytes (110 words) - 14:37, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL6|backend|office-communication|calcengine}} ...pc2v=RHEL6|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    819 bytes (107 words) - 14:39, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL7|backend|office-communication|calcengine}} ...pc2v=RHEL7|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    819 bytes (107 words) - 14:40, 12 January 2016
  • ...products/appsuite/stable|pc2n=debianname|pc2v=DebianSqueeze|backend|office-communication|calcengine}} ...ianSqueeze|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    861 bytes (109 words) - 14:42, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianWheezy|backend|office-communication|calcengine}} ...bianWheezy|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    859 bytes (109 words) - 14:43, 12 January 2016
  • ...=products/appsuite/stable|pc2n=debianname|pc2v=DebianJessie|backend|office-communication|calcengine}} ...bianJessie|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    851 bytes (109 words) - 14:43, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLES11|backend|office-communication|calcengine}} ...c2v=SLES11|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    846 bytes (110 words) - 14:44, 12 January 2016
  • ...ath|pc1v=products/appsuite/stable|pc2n=susename|pc2v=SLE_12|backend|office-communication|calcengine}} ...c2v=SLE_12|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    854 bytes (110 words) - 14:45, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL6|backend|office-communication|calcengine}} ...pc2v=RHEL6|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    819 bytes (107 words) - 14:46, 12 January 2016
  • ...path|pc1v=products/appsuite/stable|pc2n=rhelname|pc2v=RHEL7|backend|office-communication|calcengine}} ...pc2v=RHEL7|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}
    819 bytes (107 words) - 14:47, 12 January 2016
  • | <nowiki>Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co
    301 KB (41,323 words) - 19:56, 2 December 2015
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    333 KB (45,761 words) - 15:55, 17 May 2016
  • ...ween those two components by using SSL. To enforce Guard to use SSL in the communication between those two components enable the follwing configuration in Guard con
    38 KB (5,758 words) - 18:25, 13 April 2017
  • The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers emails to or from the REST API you can optionally encrypt the whole communication between
    14 KB (2,017 words) - 11:50, 13 April 2018
  • ...o the individual wforce instances, and we need to have some "intra-cluster communication" between the wforce instances to present a unified view of status.
    31 KB (4,248 words) - 12:18, 9 June 2022
  • The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers emails to or from the REST API you can optionally encrypt the whole communication between
    14 KB (2,091 words) - 13:27, 13 February 2023
  • ...of concept (POC) for an online service offering a privacy oriented email, communication and collaboration platform with integrated search. The purpose of this POC ...of concept (POC) for an online service offering a privacy oriented email, communication and collaboration platform with integrated search.
    3 KB (499 words) - 11:21, 19 December 2016
  • ...v7<br>Open-Xchange Documents Frontend 7.8.1-rev7<br>Open-Xchange Documents Communication 7.8.1-rev7<br>Open-Xchange Calcengine 7.8.1-rev7<br>Open-Xchange Readerengi
    28 KB (3,967 words) - 11:39, 9 January 2017

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)