Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 683204 - <mail-mta/nullmailer-2.2 with >=net-libs/gnutls-3.6 - smtp: Failed: Sending failed: Protocol error
Summary: <mail-mta/nullmailer-2.2 with >=net-libs/gnutls-3.6 - smtp: Failed: Send...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Robin Johnson
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-12 22:44 UTC by redneb
Modified: 2019-09-16 18:38 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description redneb 2019-04-12 22:44:02 UTC
I noticed that nullmailer had problems sending emails from 3 different gentoo systems of mine. In most cases, I found the following error in nullmailer's log:

    Starting delivery: host: smtp.gmail.com protocol: smtp file: 1553319967.12736
    From: <REDACTED> to: <REDACTED>
    Message-Id: <1553319967.532067.12735.nullmailer@REDACTED>
    smtp: Failed: 
    Sending failed: Protocol error

In some very few cases, nullmailer was able to send the email after many attempts.

After some investigation and experimentation, it appears that these problems are due to an incompatibility issue between all versions of nullmailer earlier than 2.2 and version 3.6 and newer of gnutls. This is supported by the following item in nullmailer's changelog for 2.2:

    - Fixed compatibility issue with gnutls 3.6 (and possibly others).

which corresponds to this upstream commit [1].

Therefore, I propose that all ebuilds for <mail-mta/nullmailer-2.2 are updated so that they depend on <net-libs/gnutls-3.6. Note that this also means that mail-mta/nullmailer-2.2 has to be stabilized, since gnutls 3.6 is already stable.

[1] https://github.com/bruceg/nullmailer/commit/a51499eb296f437712ff72d7425953559274890d
Comment 1 redneb 2019-04-12 22:49:20 UTC
This might be related to #651238.
Comment 2 poncho 2019-08-04 10:32:44 UTC
Had this issue today as well. Updating to mail-mta/nullmailer-2.2 fixed it