Since version 3 of eBiss 3.0.134, data can be retrieved from or sent to a WebDAV server.

The license-managed eBiss module contains both a WebDAV receive channel and a WebDAV transmit channel. You can use these channels to connect a directory using the WebDAV protocol.

eBiss.WebDAV uses PROPFIND and GET requests to retrieve files from the directory that was previously entered as a URL in the WebDAV receiver channel and then put them into the stored message basket.

In the opposite direction, eBiss.WebDAV transmits messages from a message basket via the WebDAV send channel to a directory in a stored URL.

Would you like more information about our WebDAV module? We are happy to advise you.



Relevant for customers who have booked one or more DataStream(s) or have several own eGate accounts.

General: Forwarding rules can be set to active/inactive.

The rule action “None” (formerly “inactive”) can now be used to exclude individual users from rules.


Account A with:

Action: None when messages are sent from/to Account B
Action: Copy, for all outgoing and incoming messages
The first rule specifically ensures that the second rule is not applied to messages with reference to account B.

Note: A prerequisite for using forwarding rules is the granting of a forwarding permission. For the above example, this means that a forwarding permission for Account A must first be granted on Account B. (With DataStreams this permission is granted by us.)

Please note the following when sending messages via eGate.


  • Encrypted transmission:
    • Send via TLS (SMTP): Port 25 or Port 8025
    • Receive via TLS (POP3): Port 995
  • Unencrypted transmission:
    • Send (SMTP): Port 25 or Port 8025
    • Receive (POP3): Port 110 or Port 8110

If you want to make sure that the communication with eGate works over the selected ports, please proceed as follows:

  • By establishing a Telnet connection (via a terminal cmd.exe) you can determine whether the eGate service is accessible from the internal network.
  • telnet request via port 25 (SMTP)
    • Request: telnet 25
    • Response: 220 egate4 ESMTP-Server
    • The connection could be successfully established via the above port (25) if the server returns the response listed above.
  • Alternative telnet request via port 110 (POP)
    • Request: telnet 110
    • Response: +OK eGate-POP Server (IV) at READY
    • The connection could be successfully established via the above port (110) if the server returns the response listed above.
  • If you receive a negative response, please check the rules in your firewall.

Sorry, this entry is only available in Deutsch.

Situation: Eine gesuchte Nachricht habe ich zwar auf eGate in den “fetched messages” gesehen, diese Nachricht ist aber nicht in meinem WWS.

Vorgehen / Abhilfe

Bitte sehen Sie in den Messageboxes des Konverters nach, ob auf der Eingangsseite (Messagebox “from Partner” o.ä.) Nachrichten von unbekannten Partnern zu sehen sind (gelb gefärbt).

Besonders bei neuen Handelspartnern können am Anfang Nachrichten hängen bleiben wegen unterschiedlichster Fehlerquellen.

Eine wichtige Hilfe bei der Fehlereingrenzung ist die Untersuchung eines Tasks bei der hängenden Nachricht. Der Task kann auch den Support unterstützen bei der Fehlerbehebung.

Doppelklicken Sie auf den Anfangsbereich der Zeile mit der gelben Nachricht und öffnen Sie das Register “Tasks”. Die Info -Zeile kann man markieren und mit Copy und Paste in einen beliebigen Text einfügen und versenden





Situation: I am Pranke customer. My new EDI partner is not an eGate customer and told me his GLN. This does not correspond however with the GLN of its enterprise appearing in the participant search

Solution / Description:

If the GLN in the participant search is different from the GLN named by the contact person of the new EDI partner, this may be because the partner has several GLNs, but only one eGate account with an EDI communication address.

Usually, even large organizations have only one EDI communication address, where the EDI data is exchanged and then distributed within the organization. Only if several such communication addresses exist to external parties, several participant numbers must also be created. Usually it is not necessary to create further participants for the same company. It is therefore necessary to clarify with the person responsible for EDI at the new EDI partner whether an additional participant (with an additional communication address to be monitored) is necessary. The GLN appearing in the participant search is the participant’s UNB dispatch address, which is also linked to the communication address known to us.

In exceptional cases, several GLNs can also be stored with a partner, please consult our support for this.


I am a Pranke eGate customer, my new trading partner uses X400 as a communication channel.

Can I however exchange data with him?

Solution / Description:

Pranke is offering an extension to the eGate contract to enable data to the X400 users to be transferred. Please feel free to contact us at


I am a Pranke eGate customer, my new trading partner uses AS2 as a transmission path. Can I still exchange data with him?

Solution / Description:

Pranke offers an extension of the eGate contract, which makes it possible to exchange data with AS2 users. Please contact us for further information


It is possible for the owner of an eGate customer account to determine the access of the message to the recipient (if necessary, please ask which customer status you have), even if the recipient is not a Pranke customer (so-called gateway).

Please log in to eGate to search the sent messages for the message. Please refer to the FAQ “eGate User Information“.

If the message has the sent status ( please consider the article „eGate-Icons“),

then the message has reached your partner or his service provider.

The recipient location can be checked in the open message in the Raw Header register and this can be communicated to the recipient.


This can be checked by the responsible person of the converter (possibly a service provider) or the mail server of the recipient (often a service provider is connected between Pranke eGate and the end customer who may have error messages). The service provider customer (final recipient) would have to inquire about this.


The addressing of all accounts on eGate is always done via the Pranke Participant Number. This is a ten-digit unique number, which can be searched by name or GLN under the participant search at First, please enter the 10-digit eGate participant number, which is the local part of the e-mail address, i.e. the part before the @ sign, for example:2123456789.Then the domain part follows, it always reads:egate.pranke.comThe correct addressing then looks like this (example, please replace the local part with the respective TNR of the partner).

Pranke eGate customers with a so-called full account can send data via SMTP and retrieve data via POP3.

Here the server configuration:



For gateway accounts applies:

I send from the address stored in eGate for example to for example:
Messages sent from an address other than the one registered with Pranke will be rejected, the sender must be known to us, he is on a so-called whitelist.

For example, an attempt to send fails because we don’t know this address.

A special problem is the BATV feature of some sender mail servers, since it always generates different sender addresses,

see: BATV Feature



If you have a gateway account and use x400 as the transmission path, you must send the messages to the x400 eGate address. This address is in principle always the same, you only have to enter the respective participant number of the trading partner on eGate in the surname (S). You can find this on our participant search at or you can ask your trading partner for it.

The following is the structure of the currently valid X.400 address of an eGate participant when sending from the X.400 network of Deutsche Telekom:

X400 Bezeichnung X400 Key Value
Country C= de
Adminstrative Domain A= viat-smtp
Private Domain P= com
Organisation O= pranke
Organisation Unit 1 OU1= egate
Surname S= <TNr>

For ‘Surname’, the TNr (= participant number) must be entered here. So for the eGate user 2800999999 the gateway address is therefore: C=de; A=viat-smtp; P=com; O=pranke; OU1=egate; S=2800999999

When sending outside the X.400 network of Deutsche Telekom:

X400 Bezeichnung X400 Key Value
Country C= DE
Adminstrative Domain A= VIAT
Organisation O= PRANKE
Surname S= EGATE

Sorry, this entry is only available in Deutsch.

Der Kommunikationsweg FTP / SFTP ist aus technischen Gründen leider nicht möglich. Sollten Sie den Pranke Konverter eBiss nutzen ist die Einrichtung eines FTP Kanals möglich. Wenn Sie hierfür Hilfe benötigen wenden Sie sich bitte an .