FAQs

Question

Why is the subject of a message so cryptic?

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.

Explanation

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 (https://tools.ietf.org/html/rfc1428) 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.

Source: https://tools.ietf.org/rfc/rfc1428.txt

/by

Which ports are used to send and receive messages via eGate?

Please note the following when sending messages via eGate.

server: egate.pranke.com

  • 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 egate.pranke.com 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 egate.pranke.com 110
    • Response: +OK eGate-POP Server (IV) at egate.pranke.com 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.
/by