group.of.nepali.translators team mailing list archive

[Bryce Harrington <1971489@xxxxxxxxxxxxxxxxxx>]

I reviewed the upstream mailing list discussion, and tried some of the
example commands they discussed but was not able to reproduce the issue.

I'm guessing this could be constructed by setting up a bionic LXC
container with exim4 installed, then attempt to send email to a gmail
host?

    $ sudo apt-get install exim4
    $ sudo exim4 -d-all+tls <...something...> <gmail host>

And then observe log output such as in the original bug description.

Advice on how to set up a reproducer would be appreciated.

** Changed in: exim4 (Ubuntu Bionic)
       Status: Triaged => Incomplete

** Bug watch added: bugs.exim.org/ #2359
   http://bugs.exim.org/show_bug.cgi?id=2359

** Also affects: exim via
   http://bugs.exim.org/show_bug.cgi?id=2359
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1971489

Title:
  exim4 GnuTLS breakage with outgoing TLS 1.3 "Resource temporarily
  unavailable"

Status in exim:
  Unknown
Status in exim4 package in Ubuntu:
  Fix Released
Status in exim4 source package in Trusty:
  Won't Fix
Status in exim4 source package in Xenial:
  Won't Fix
Status in exim4 source package in Bionic:
  Incomplete

Bug description:
  Very recently, my (unchanged for years) bionic exim4 flow ( outgoing
  SMTP -> smtp.canonical.com ) abruptly stopped working, with exim4 log
  as follows:

    SMTP<< 220 smtp-relay-canonical-1.canonical.com ESMTP Postfix (Ubuntu)
    SMTP>> EHLO myhostname
    SMTP<< 250-smtp-relay-canonical-1.canonical.com
           250-PIPELINING
           250-SIZE 61440000
           250-VRFY
           250-ETRN
           250-STARTTLS
           250-ENHANCEDSTATUSCODES
           250-8BITMIME
           250-DSN
           250-SMTPUTF8
           250 CHUNKING
    SMTP>> STARTTLS
    SMTP<< 220 2.0.0 Ready to start TLS
    SMTP>> EHLO myhostname
    H=smtp.canonical.com [185.125.188.121] TLS error on connection (recv): Resource temporarily unavailable, try again.
    SMTP(close)>>
    H=smtp.canonical.com [185.125.188.121]: Remote host closed connection in response to EHLO myhostname

  This appears to be a manifestation of this exim4 bug which was fixed in exim4 (4.92): https://bugs.exim.org/show_bug.cgi?id=2359
  See also: https://www.mail-archive.com/exim-users@xxxxxxxx/msg53121.html

  I found and installed a PPA version of exim4 (4.94) for bionic, which
  did fix the problem for me.

  I believe that all Ubuntu versions which supply exim4 < 4.92 {Bionic,
  Xenial, Trusty} are affected by this bug, which leaves exim4
  mysteriously broken when the server side happens to move to TLS 1.3.

  I suggest updating exim4 on the affected Ubuntu versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1971489/+subscriptions