Posted on by admin

Download EMG 8.0.4

Changes

These are the changes in EMG 8.0.4 as compared to EMG 8.0.3.

  • Changes merged from version 7.2.35:
    • The handling of encrypted passwords was previously not fully reentrant, leading to incorrectly rejected logins in some rare occasions.
    • Earlier detection of sockets closed from the remote side.
  • The new global option FAIL_DESTADDR_MAX_PAUSE=n can be used to set the maximum time a destination address is rejected by the FAIL_DESTADDR_MAX option before being allowed again. By default this value is 24 hours. The value n can be either the number of seconds, the number of minutes followed by “M”, the number of hours followed by “H”, the number of days followed by “D”, or the number of weeks followed by “W”.
  • The hardcoded handling of HLR information in delivery reports over SMPP from Infobip has now been removed. If you have such a connector, you can use our infobip-hlr plugin.
  • If SSL is set, or TLS is set to ALLOW or FORCE on an outgoing SMTP connector, we now use the default value LOGIN for the XAUTH option.
  • EMG now supports internationalized email addresses over SMTP as defined in RFC 6531.
    • For incoming connectors, the EHLO response now includes 8BITMIME and SMTPUF8. The domain names are punycode decoded (which does nothing for the parts that do not start with “xn--“), and the result is stored UTF-8 encoded. If the client is SMTPUTF8 compliant, the full addresses can be sent UTF-8 encoded in the SMTP dialog, in which case EMG will just store them as is.
    • For outgoing connectors there are three cases.
      1. If neither the username nor the domain part contains any non-ascii characters (above 0x7F), they are sent as before.
      2. If the server responds with SMTPUTF8, the address is sent as is, UTF-8 encoded. EMG then also adds SMTPUTF8 at the end of the “MAIL FROM” command.
      3. If the server does not respond with SMTPUTF8, the domain part is punycode encoded. If the username contains any non-ascii characters when talking to such a server, the message is terminated as it cannot be delivered.
  • EMG now handles the =?charset?encoding?encoded-text?= syntax from RFC 1522 for the Subject header, both for incoming and outgoing emails. The charset can be “ISO-8859-1” or “UTF-8” on the way in. On the way out, there are three cases. Except for in the last case, the encoding is always “Q”, signifying quoted-printable.
    1. If the text contains characters above 0xFF, “UTF-8” is used.
    2. If the text contains characters above 0x7F but below 0x100, “ISO-8859-1” is used.
    3. Otherwise, the text is sent as is, without the “=?...?=” construction.

Files

The downloads are password-protected. To obtain the username and password required, please use our license request form. If you already have an existing installation, you should download just the new binaries. However, if you’re upgrading from EMG 7 or earlier, please also take a look at the full installation guide, as you may also need a new Perl installation.

Binaries and scriptsEMG 8.0.4-binaries
Full distributionEMG 8.0.4-full