- Outlook for the near future:
- In the near future, for you as a (potential) reseller of our White Labeled Benno Cloud (WLBC) a Reseller Portal will be available online, which will enable you to:
- – Registration as a new WLBC Reseller (Self-service)
- – Dashboard with overview of your end customers and their archive statuses
- – Create, modify and delete your end customers and manage the contracts of your end customers
- – Overview of the invoices that we send to you for WLBC
- For the onboarding of your end customers we need to coordinate how you set up or implement the export of the emails to be archived so that the mails can be archived in Benno Cloud.
To this end we offer various interfaces, which we will present and explain below. - INTERFACES FOR IMPORTING MAILS INTO WLBC
- With WLBC you can archive the emails de facto all mail and groupware solutions (incl. Microsoft 365/Exchange Online) be archived.
The import of emails from IMAP mailboxes (IMAP import) is not available. - WLBC has the following Import interfaces for the import of emails of the respective clients or end customers:
1. REST API for import from Linux/Unix systems as well as self‑service upload of legacy mails
2. Journaling mailbox for M365/Exchange Online
3. SMTP import
- 1. REST API for import from Linux/Unix systems
- The e-mails are sent as individual EML files to the REST API of Benno Cloud (https upload). The EML files should be cached as a copy directly on the MTA if possible and then transferred via REST.
- 1.1 Linux / UNIX MTA
- Für Debian GNU/Linux systems we provide a MILTER Daemon as a ready-made Debian package. The MILTER Daemon can be attached to Postfix or Sendmail installations.
All incoming and outgoing e‑mails are locally cached by the MILTER. Zusätzlich the SMTP envelope information is stored with the e‑mails so that data of possible BCC Empfänger is not lost.
The cached e‑mails are anschließend transferred by an asynchronous running job to Benno Cloud übertragen (https-Upload). Auch hierfür we provide a ready-made Debian GNU/Linux package to Verfügung.
Für other platforms können we provide an example cURL call to Verfügung, which can serve as a template für implementing the integration.
- 2. Microsoft Exchange Server and Microsoft 365/Exchange Online (M365)
- Microsoft Exchange Server (MXS) provides the Möglichkeit to store all incoming, outgoing and internal e‑mails in the so‑called Journaling Mailbox to temporarily store. The e‑mails are stored as e‑mails with the metadata in the body and the actual e‑mail as an attachment.
The e‑mails can subsequently be exported via POP3 or sent via SMTP to an external mailbox.
M365 or Exchange Online also offers this configuration Möglichkeit. However, the e‑mails cannot be imported via POP3 here, but müssen to be forcibly sent directly via SMTP to a collection mailbox (which is directly linked to Benno Cloud).
Für the import from MS Exchange or M365 we provide you with a journal mailbox address for the respective end customer. In MS Exchange or M365 this address is then configured as the target address of the journaling mailbox.
A short explanation of the configuration of the journaling mailbox in Exchange Online can be found here: https://wiki.benno-mailarchiv.de/doku.php/microsoft_office_365
- 3. SMTP Import
- For SMTP import into Benno Cloud, emails to be archived are sent via SMTP to a specific (predetermined by us) email address of Benno Cloud. They are thus directly archived.
- A dynamically configurable alternative to MILTER is the Möglichkeit to send the e‑mails via envelope forwarding to an individual e‑mail address of Benno Cloud.
In Linux/Unix MTA Postfix, this is configured, for example, with the help of BCC maps (keyword sender_bcc_maps, recipient_bcc_maps).
This method has gegenüber the above described MILTER import the advantage of the simpler and more dynamic configuration. However, the information über recipients is lost here, which were addressed via BCC. The e‑mails are then archived, but can under circumstances only be found by the ADMIN in Benno Cloud.
- 4. IMAP Import
- ATTENTION:
- Due to the requirements of the GoBD, NO interface is available for IMAP import! Even if the IMAP retrieval were technically feasible, a GoBD-compliant mail archiving is not implementable via IMAP.
- Provider mailboxes (e.g., T-Online, web.de, GMX, etc.) or mailboxes from providers such as, for example, All Inkl, which do not offer their customers suitable interfaces für a GoBD-compliant mail archiving or make them available, can generally not be archived in a GoBD-compliant manner.
- Für such cases a migration to suitable mail providers is indispensable, which provide suitable interfaces for archiving. (LWsystems offers for the migration of mail hosting into the LWsystems Cloud (Server location: Germany) to. In the LWsystems Cloud we operate the Groupware Zimbra. There is the Möglichkeit, between Postfächern of any Größe to wählen – from simple IMAP mailboxes to full Groupware-Postfächern. These können natürlich also used with Microsoft Outlook and with synchronized with mobile Endgeräten are).
- 5. Note for larger infrastructures: Archiving of duplicates on multiple mail servers
- If emails are imported from multiple different source systems, there is the Möglichkeit that an email is imported multiple times or fälschlicherweise imported.
Für such cases there are appropriate configuration options that we can deploy case-by-case for your clients können. - In the following wiki article the issue is erläutert:
https://wiki.benno-mailarchiv.de/doku.php/multi-import - If you have such a situation, as explained in the wiki, please feel free to contact us for clarification!
- 6. White Label WebApp with custom domain
- The Benno Cloud WebApp can easily be Corporate Design accordingly branded be. Außerdem können we provide the WebApp under a Domain-Name of your choice (bspw. mailarchiv.resellername.de) and operate it.
- The following items need to be configured:
1. As a reseller, you set up a CNAME record for your domain
2. We prepare the VirtualHost configuration on the web server
3. We set up a Let’s Encrypt (Dehydrated) SSL certificate for the CNAME domain.
4. You design and brand the WebApp using HTML/CSS and provide us with the CSS file for upload.
5. If you wish to use your logo for the WebApp, please also provide it to us.
6. We install your CSS file and logo etc. on the web server.
- 7. Complete White Labeling – including email sending
- From December 1, 2025, you can extend the white labeling of your Benno Cloud to include email sending. Emails that your customers forward from the archive will then be sent with your own sender address and via your domain.
- Two alternative paths to the goal:
- Alternative 1 – Simple: We send über our mail servers – You only adjust your SPF-Record (
a:mailout.benno-cloud.de) and give us your sender address.
Alternative 2 – Flexible: You send über your own mail servers – You have full control über DKIM, DMARC and all other authentication mechanisms. - Adjust mail templates: Download our standard mail templates (TXT/HTML) here, adjust them to your wishes and submit them for integration with us. This is done easily über our support team: support@benno-mailarchiv.de
- Without your active request for white labeled mail sending, the emails über our mail servers with sender addresses such as
no-reply@benno-cloud.desent.
- AUTHENTICATION INTERFACES
- Benno Cloud includes a local user management for each individual tenant. It is accessible within the WebApp (admin rights of the user required).
Furthermore, the authentication of users can be against a local LDAP or Active Directory (AD) or via OAuth2 (e.g., Microsoft Login, Google Login, etc.) can be performed. - When authenticating against a local system at the end customer, there should be no direct access to the LDAP service. Instead, we provide a Debian GNU/Linux package for this purpose, with which Benno Cloud can perform the authentication against the internal LDAP directory via REST API.