eGate is generally to be considered as a closed community network. Therefore, when picking up messages with a SMTP Channel in eBiss, we want to use the Sender identification mandatory. This means that all possible sender eGate email addresses of my trading partners must be known in my eBiss system. This also applies to (third party) poviders who forward EDI messages on behalf of their customers. So if an eGate participant is offered in the participant search not only with a CUSTOMER.INI file but also with a SENDER .INI FILE I have to make sure that the eGate participant of the provider (or SENDER) exists as trading partner in my eBiss. If not, then I need to import the SENDER .INI file.

Example of an eGate participant with provider affiliation:

Name Tnr GLN/UNB-ID Customer .ini File Sender .ini File
Muster GmbH, München (DE) 1234567890 1234567890123 Download Provider

If messages remain unprocessed in your INBOX and with an unknown partner, the reason may be that the validation in the receive channel was not successful.

Pranke eGate Access if You’re Not a Pranke eGate Customer

To enable you to exchange messages with a Pranke eGate customer, a communication channel must be set up for you. This communication channel might be through email forwarding, x.400 with A=viaT and C=DE, or AS2.

eGate receives your message for another subscriber via this communication channel and makes it available to the recipient via their communication channel – and vice versa.

Read more


The MDN (Message Disposition Notification) is an electronic acknowledgement of receipt that is returned to the sender when transmitted via AS2. It is unique for each message.

If the recipient of your message requests such an MDN, you will find it in eGate under the “DeliveryReport” tab.


This is initially only a hint that the message could not yet be transmitted successfully.
The SMTP status code 450 4.3.2 indicates that the Exchange Server of the other side has frozen the reception of messages, e.g. because a problem is being solved there.

“This notification can be ignored if you don’t receive another tracker that reports an error for the message in question.

This means that this is only a warning; if the message cannot be delivered repeatedly, you will receive an error message.
e.g: companies do not need to do anything at this point, eGate simply informs you that the message is not yet available on the other side.

IT terms
Cross Docking Procedure in which goods pre-picked for a final destination in a distribution warehouse are only redistributed at package level.
CRP program The Cyclic Replenishment Program is a procedure for the regular replenishment of articles.
EAN The international (formerly European) article number is an internationally unique article identification.
EANCOM A subset of EDIFACT, carried by EAN.UCC, specifically for retail and consumer goods.
EAN International The umbrella organisation for the allocation of article and company identifications looks after various standards, including EANCOM.
EAN.UCC The umbrella organization of EAN International and UCC.
EDI Electronic Data Interchange is a generic term for the structured exchange of data between applications.
EDIFACT Electronic Data Interchange For Administration, Commerce and Transport is an internationally standardized basic standard of EDI, supported by UN and ISO.
GLN The Global Location Number is an internationally unique identification of a company and is assigned by the EAN.UCC.
GTIN The Global Trade Item Number is the successor of the EAN and UPC.
Material EDI The profile of the DTB for data exchange between producer and supplier.
NCTS The New Computerized Transit System is a computerized transit system in Europe in connection with customs.
PLV The passive contract processing.
SSCC The Serial Shipping Container Code is an EAN package identifier.
Subset A subrange of a standard, e.g. EANCOM from EDIFACT.
UPC The Universal Product Code is an equivalent of the EAN in the USA.
VAN The Value added network is a value-added service, i.e. networks with additional services to the pure connection.
WWS profile EANCOM application profile for lifestyle retail
XML/EDI Electronic Data Interchange using eXtensible Markup Language describes electronic data interchange using XML or approaches such as ebXML, Bizztalk, but not yet a standard.

Set up the TLS/SSL communication channels to eGate.

  1. Open the communication channels in the eBiss menu on the left under the Communication group
  2. Create a POP3 receiving channel with the settings:
    • Host: (
    • Port: 995
    • Authentifizierung: Basic
    • Set username/password
    • In the advanced settings set the SSL handling to Implicit
  3. Create an SMTP send channel with the settings:
    • Host: (
    • Port: 25
    • Authentifizierung: Basic
    • Set username/password
    • In the advanced settings set the SSL handling to Explicit

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.)


Unreadable characters appear in the subject lines of messages on eGate as shown in the figure:

enkodierter Betreff

Then the following situation exists: The message contains special characters or umlauts and must be encoded in order to be transported via SMTP.


SMTP is defined as 7bit transport, in content the MIME extension avoids the problem by bringing the content via Base64 or Quoted Printable into a 7bit compatible format. The same procedure is used for the header, see the excerpt from RFC 1428 ( and the other references:

If a message body has been upgraded to MIME, the RFC 822 headers   containing non US-ASCII characters must be upgraded to conform with   the header encoding rules of RFC1342. A gateway should recode all   unstructered header fields as well as RFC 822 “comment”s and   “phrase”s according to the rules of RFC 1342. There is no equivalent   in RFC 1342 to the “8bit” Content-Transfer-Encoding value for message   bodies so all 8bit header text must be transformed according to   either the “B” or the “Q” encoding method.  For ISO 8859 character   sets, the “Q” encoding will generally result in somewhat readable   headers.


ediCERT® eXpertise

When you wish to contract us for an  eXtended EDI service, we will assess your needs in a workshop, to define and optimize your EDI processes. Based on the assessment we will define a tailor-made service, which covers exactly what is necessary in the daily business and ensures continuous development. This can go so far as to referring your customers directly to our hotline and us becoming your EDI department. Necessary processes, changes, new data entry of EDI customers, etc. are completely controlled by Pranke, even all the way into your ERP, shall you so desire. For all questions that are beyond the standard procedures we will also define customized interfaces, so that you can decide how to proceed.

Your gain: A failsafe EDI department with know-how first hand at a fair price. The construction of an internal department with personnel and training costs is eliminated, and you have the flexibility to add or subtract services as needed!


The description of the functions in eGate can be found in eGate in the menu Information/User Information or can be opened here as PDF:

eGate Anwenderinformationen