» Published on Sun, 08 Sep 2019 19:00:00 +0000

• Resolved

  Update is complete.

  » Updated Sun, 08 Sep 2019 19:36:00 +0000

• Scheduled

  Additional technical information for Transactional SMTP users

  Starting from this release, Maxemail will no longer advertise AUTH methods in response to a client-issued EHLO command until a secure connection is established (ie. after successful STARTTLS on port 587 (recommended) or port 25 (compatibility)).

  There is no impact to connections using port 465 (legacy) which uses implicit encryption to establish the secure session before the client issues any commands.

  Clients using port 587 or 25 should be aware of the change, but are not expected to have to make any changes to their implementation, as:

  1. Maxemail has never accepted AUTH until a secure session is established.
  2. Existing client implementations should follow RFC3207 §4.2 which requires that they MUST disregard features advertised before the encryption, and therefore SHOULD issue another EHLO after the secure session is started.

  Any queries should be directed to the support team at support@xtremepush.com

  » Updated Sun, 08 Sep 2019 19:00:00 +0000

• Scheduled

  Maxemail will be updated to v125. Release notes

  No service impact is expected as updates are rolled out progressively across our infrastructure, although there may be a slight delay to sending as services are restarted.

  » Updated Sun, 08 Sep 2019 19:00:00 +0000