EGVP Service

In EGVP, a SAFE-ID is the unique identifier (address) of a mailbox in the SAFE directory service, used to address and deliver EGVP messages.

Every participant (e.g., court, authority, lawyer, or notary) automatically receives such a SAFE-ID when creating an EGVP mailbox, under which they are reachable in the directory service.

This ID usually looks something like this: safe-sp1-1400589659747-015539967 and is unique throughout Germany.

The SAFE-ID is also required to activate, for example, a special electronic authority mailbox (beBPo) – without this ID, no application can be submitted to the beBPo verification office.

No.

Because EGVP and De-Mail are based on separate, legally and security-technically independent platforms using different protocols (OSCI vs. SMTP/IMAP with S/MIME) as well as trust ecosystems, and neither a gateway nor an intermediary service is technically or legally prescribed, messages can only be sent and received within their own respective systems.

Yes.

The eBO ("electronic citizen and organization mailbox") is a secure transmission method within the framework of electronic legal communication. Since June 1, 2022, the eBO has been integrated into the EGVP infrastructure and is therefore also addressable in the beA system (special electronic lawyer mailbox).

The messages are encrypted from the moment of sending, and the files on the Safe system are protected by the EGVP security concept.

Access rights are defined based on a role concept so that data cannot be read, copied, changed, or deleted without authorization after storage. All security and data protection-relevant accesses are logged, and access protection is increased through the use of a firewall.

Detailed basics and current news from the judiciary can be viewed in the  ⇒ Justice Portal . Current guidelines can also be downloaded there.

No, account sharing for the ERV Portal is not supported.

Due to Two-Factor Authentication (2FA) and other security measures, every access is personal and not intended for shared use. If the ERV Portal is to be used by multiple users, a separate access must be ordered for each individual.

In this case, it is not due to a missing registration, but due to missing permissions in the ERV Portal. An administrator must manually assign the appropriate permissions.

How admins can assign permissions:

• Settings → User Rights
• Select the row of the affected user
• Mailbox access → Edit
• Activate the desired access permission via checkbox in the list of SafeIDs
• Click on "Close" to save

Yes, the Two-Factor Authentication method can be adjusted via the settings under User 2FA in the online portal.

Here, a method can be set as primary, deleted, or backup tokens for login can be retrieved.

Prerequisites

• Access to the Mentana Gateway web interface with administrator rights.
• A prepared list of users to be created in CSV format.

Instructions

1. Login: Log in to the Gateway web interface.
2. Navigate: Navigate to the user management menu item.
3. Find function: Search for a function like "Import users" or "CSV Import".
4. Prepare template: If offered, download the template and enter the user data (First name, Last name, Email etc.).
5. Upload file: Upload the prepared CSV file via the upload function.
6. Check result: Check the system log for errors after the upload.

Where do I find my SAFE-ID?

• Directly in beA / beN / beBPo / eBO: Log in to the mailbox and go to Settings → Overview. Your own SAFE-ID is shown there.

Where do I find the SAFE-ID of a contact?

• EGVP-/SAFE Directory Service (Address Book): Open the address book in your EGVP mail client. Search for the participant and click on Info/Details – the SAFE-ID is displayed there.

Where do I find the SAFE-ID of a lawyer?

•  ⇒ Federal Official Lawyer Directory:  Search for the name, select the data record, and click on Info. The SAFE-ID is displayed in the lower area.

The manual is always installed along with the software. It can be accessed at any time in the Outlook Add-in tab under "Info" or "Configuration".

To see the version number, go to the Mentana Add-In tab in Outlook and click on "Info". The information about the software will be displayed.

If you click on "Info" in the program and navigate to "Version Info", you can see the update history and the changes contained therein.

1. Select the Mentana Add-in in Outlook.
2. Open Support Tools and click Logging enable.
3. Restart Outlook.
4. Reproduce the error step by step.
5. Retrieve the log file (AddinLog) via the path displayed in the Support Tools and send it to support.
6. Then deactivate logging again.

Detailed instructions are available  ⇒ here for download .

Cause: This happens when the sender's mail gateway signs or modifies the message content before sending it to the Mentana Gateway. This prevents the attachments from being correctly assigned.

Solution: The sender's IT must ensure that the message is forwarded unmodified on their mail gateway to the Mentana Gateway. This cannot be fixed by our IT or service.

If settings that were correctly configured in the Gateway are overwritten during sending, the message is needed as a file to trace the process.

Please send the message as a .eml file or the message header, once in the form as it was sent, and once as it was received. If the Add-in is installed, an Add-in log is also very helpful.

Delivery attempts & Escalation: The Gateway tries up to five times to deliver a message. If this fails, the message is forwarded to the stored Postmaster address and ultimately lands in the folder C:\Program Files\Mentana\Gateway\data\Failed-Messages as a .eml file.

Check steps:

• Check connection between Gateway and mail server.
• Ask Postmaster if a forwarded message was received.
• Check the sending period in the Gateway log.

Support: If the message is still missing, please send us the EGVP Message-ID of the message.

Cause: Sending is aborted if a file attachment bears an invalid name.

Checklist for valid filenames:

• Only letters and numbers (umlauts allowed).
• No special characters.
• Use only - (hyphen) or _ (underscore) as separators.
• Maximum length: 90 characters.
• Only one dot . before the file extension.

Solution: Rename the file accordingly and try sending again.

Cause: Error 9999 indicates a temporary disruption in the sending process where a required resource (e.g., the SAFE system of the judiciary) was briefly unreachable.

Solution: Current Gateway versions include an automatic retry function. Please wait and try sending the message again after some time. If the error persists, check the reachability of the recipient.

Cause: Error 150067 means that the attached xJustiz file could not be read because it is faulty or non-compliant.

Solution: Check the file with the official  ⇒ XML-Checker  of the judiciary and adjust it if necessary.

Cause: Outlook deactivates Add-ins that it considers too slow. This can happen if the Add-In checks emails in the background over a slow connection to the mail server.

Solution: Outlook can be configured in the Windows Registry so that the Mentana Add-In remains permanently active. This should only be performed by the IT department. Detailed instructions can be found at Microsoft under:

 ⇒ Support for keeping add-ins enabled 

In the Electronic Court and Administrative Mailbox (EGVP), an electronic acknowledgement of receipt (eEB) can only be requested by the judiciary. For other user groups, such as citizens or organizations, requesting an eEB is not intended.

1. Create new certificate: Create a new SSL certificate in .pfx or .p12 format in your Certification Authority (CA).
2. Start Gateway Configuration: Open the Gateway Configuration application.
3. Upload Keystore: In the Web Console tab, click on Upload new Keystore. (Note: .pfx files must be renamed to .p12).
4. Store password & test: Enter the Keystore password and test the function.
5. Save configuration: Save the configuration.
6. Restart service: Restart the Mentana Gateway Web Console service.
7. Function test: Call up the Web Console via the new hostname and perform a test dispatch.