The entirely private digital workspace, Zextras Carbonio, includes the following:
- Shareable across a domain include email, contacts, and calendaring essentials.
- a full-featured mail server with antivirus and anti-spam software
- Video and text conversations
- File-management programme with group editing and document sharing
Carbonio’s advantages include:
- concentrate on privacy and data sovereignty
- simplicity of installation due to Linux packages’ out-of-the-box usability
- comprehensive collection of collaboration and communication tools for businesses
- Scalability: put up a single server, then quickly add more nodes as the infrastructure and demands of the business change.
A browser is required to access any Carbonio feature:
The Web GUI is accessible in these languages, and English is Carbonio’s primary language.
Contribution to the Documentation The documentation for Carbonio is now open source and posted in a public repository on Github.
Any type of documentation that is developed in accordance with the standards and is submitted as a pull request is welcome. Send an email to firstname.lastname@example.org if you have any ideas for the documentation or if you need help using Python Sphinx, the framework we use to write the documentation.
Seeking Assistance for Carbonio
In addition to this documentation, Zextras offers the following web sources:
How to file a problem report
The first priority is usually to fix any issues that come up when utilising a software so that you may resume your regular daily activities as soon as feasible.
As a result, the best manner to report a Carbonio issue is the one that enables the Technical Support Team and the Reporter to work together to achieve their objectives most quickly and effectively.
To accomplish this, first create a precise and thorough report outlining the problem encountered. Next, open a ticket on the Zextras customer support site and attach the report to the complaint. This enables the Technical Support Team to investigate the problem right away without requesting further details.
It may be necessary to do one or more of the following tasks while creating a thorough report:
- to outline the procedures necessary to re-create the issue. This is the most crucial aspect since it would provide the Technical Support Team with a preliminary understanding of the potential source of the problem.
- to put CLI commands into action
- making screenshots
- to do additional activities based on the reported problem, the associated modules, etc.
Prior to Opening a Ticket
To provide the Technical Support Team with the necessary information, you need obtain certain data and configuration variables from Carbonio and its components before opening a support ticket.
- Commands must be run on the node where the component is installed in Multi-Server deployments.
- The directory /opt/zextras/log/ contains log files.
Common and general information
- Every situation requires the broad and common information since it enables one to comprehend the context in which the problem was encountered. The output of each of the ensuing instructions has to be saved to a text file.
- Enabling debug logging and attaching the produced log files to the ticket is another activity that helps the technical support team:
- Run to boost the log verbosity on the mailbox server
- duplicate the problem
- Run to return the log verbosity to normal.
- the mailbox server’s mailbox.log file
- The proxy node’s nginx.log and nginx.access.log files
Mobile Devices and Apps
Chats with Carbonio
Backup for Carbonio
- Open a fresh Firefox or Chrome window
- Wait for the webmail to fully load.
- duplicate the problem
- Attach the ticket’s files including both the console export and the network export.