- Outlook for the near future:
- In the foreseeable future, a Reseller Portal will be available online for you as a (potential) reseller of our White Labeled Benno Cloud (WLBC), 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 agree on how to set up or implement the export of emails to be archived so that they can be archived in Benno Cloud.
For this, we offer various interfaces, which we present and explain below. - INTERFACES FOR IMPORTING MAILS INTO WLBC
- With WLBC, emails from virtually all mail and groupware solutions (including Microsoft 365/Exchange Online) can be archived.
The import of emails from IMAP mailboxes (IMAP import) is not available in WLBC for regulatory reasons (GoBD). - WLBC has the following import interfaces for importing emails from the respective tenants 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
- For Debian GNU/Linux systems, we provide a MILTER daemon as a ready-to-use Debian package. The MILTER daemon can be integrated with Postfix or Sendmail installations.
All incoming and outgoing emails are locally cached by the MILTER. Additionally, SMTP envelope information is stored with the emails, ensuring that data from potential BCC recipients is not lost.
The cached emails are then transferred to Benno Cloud by an asynchronously running job (https upload). We also provide a ready-to-use Debian GNU/Linux package for this purpose.
For other platforms, we can provide an exemplary cURL call that can serve as a template for implementing the connection.
- 2. Microsoft Exchange Server and Microsoft 365/Exchange Online (M365)
- Microsoft Exchange Server (MXS) provides the ability to temporarily store all incoming and outgoing as well as internal emails in the so-called Journaling Mailbox. The emails are stored as emails with metadata in the body and the actual email as an attachment.
The emails can then be exported via POP3 or sent to an external mailbox via SMTP.
M365 or Exchange Online also offers this configuration option. However, the emails cannot be imported via POP3 here, but must be sent directly via SMTP to a collection mailbox (which is directly linked to Benno Cloud).
For the import from MS Exchange or M365, we will 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.
You can find a brief explanation on configuring the Journaling Mailbox in Exchange Online 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.
- An alternative to MILTER that can be configured dynamically is the option to send emails to Benno Cloud via envelope forwarding to a specific email address.
In Linux/Unix MTA Postfix, this is configured using BCC Maps (keyword sender_bcc_maps, recipient_bcc_maps).
This method has the advantage of simpler and more dynamic configuration compared to the MILTER import described above. However, information about recipients addressed via BCC is lost. The emails are then archived but may only be found by the ADMIN in Benno Cloud under certain circumstances.
- 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 with providers like All Inkl, which do not offer their customers suitable interfaces for GoBD-compliant mail archiving or make them available, usually cannot be not archived in compliance with GoBD.
- For such cases, a move to suitable mail providers is unavoidable, which provide suitable interfaces for archiving. (LWsystems offers the relocation of mail hosting to the LWsystems Cloud (server location: Germany) for this purpose. In the LWsystems Cloud, we operate the Groupware Zimbra. There is the possibility to choose between mailboxes of any size – from simple IMAP mailboxes to entire groupware mailboxes. These can of course also be used with Microsoft Outlook and synchronized with mobile devices).
- 5. Note for larger infrastructures: Archiving of duplicates on multiple mail servers
- If emails are imported from multiple different source systems, there is a possibility that an email is imported multiple times or incorrectly.
For such cases, there are corresponding configuration options that we can use on a case-by-case basis for your clients. - In the following wiki article, the problem is explained:
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 be easily branded according to your corporate design. In addition, we can provide and operate the WebApp under a domain name of your choice (e.g. mailarchiv.resellername.de).
- 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 want to use your logo for the WebApp, please also provide it to us.
6. We set up 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 via our mail servers – you only adjust your SPF record (
a:mailout.benno-cloud.de) and provide us with your sender address.
Alternative 2 – Flexible: You send via your own mail servers – you have full control over DKIM, DMARC, and all other authentication mechanisms. - Customize Mail Templates: Download our standard mail templates (TXT/HTML) here, customize them according to your wishes, and submit them to us for integration. This is done uncomplicatedly via our support team: support@benno-mailarchiv.de
- Without your active request for white labeled mail sending, the emails are sent via our mail servers with sender addresses like
no-reply@benno-cloud.de.
- AUTHENTICATION INTERFACES
- Benno Cloud includes a local user management for each individual tenant. It is accessible within the WebApp (assuming admin rights of the user).
Furthermore, the authentication of users can be done against a local LDAP or Active Directory (AD) or via OAuth2 (e.g. Microsoft Login, Google Login etc.). - 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.