The problem can be reduced to this simple test case. First, create a mailx configuration file called /home/chris/mailtest.rc with this in it:

Then executing the following test email in a terminal works fine up to an including s-nail-14.9.21-x86_64-1.

However from s-nail-14.9.21-x86_64-2 onwards, the correct exchange appears to take place with the gmail mail server but the message delivered to the recipient has no body and no subject given for it. Its headers look fine though so the transport seems to be OK.

Reverting to s-nail-14.9.21-x86_64-1 solves the problem. Unfortunately I do not have a copy of the s-nail.SlackBuild so I do not know what changed between the SlackBuild for s-nail-14.9.21-x86_64-1 and the SlackBuild for s-nail-14.9.21-x86_64-2.

I have not tested this with any smtp relay other than gmail. It would be interesting to hear the results from anyone who is able to do this.

While i can't help on the subject, at least here you can see what changed(thanks to Alien, and thanks to Ponce pointing to it in another thread):
https://git.slackware.nl/current/log...ail.SlackBuild

Thanks for the heads-up. On comparing versions, there was no difference in the SlackBuild between s-nail-14.9.21-x86_64-1 and s-nail-14.9.21-x86_64-2. This implies that the defect is something to do with the latest version of glibc. More particularly it suggests that s-nail-14.9.21 is not compatible with the glibc-2.33 headers.

Confirmed here...

I'm having the same problem. I posted about it to the 'requests for current' thread on the 18th.

Here

Fortunately, I have a current vm that hasn't been updated since 2/11 so I downloaded the s-nail source on it and rebuilt it against glibc 2.22 then transferred it over to my physical machine and installed it. Now everything is working as expected. My messages contain a body and a subject.

@andrew.46 and @Mechanikx: Are you using a relay and if so is it the gmail smtp relay? I was wondering whether it is a problem with sending any email in any way, with sending an email via a relay, or with sending via a SSL/TLS enabled relay such as gmail.

Edit: I have just tried mailx with a different (non-gmail) relay which uses the rather unusual combination of SASL authentication but not TLS encryption. This also works with s-nail-14.9.21-x86_64-1 but not with s-nail-14.9.21-x86_64-2 onwards. However, in the case of this relay, instead of the recipient receiving an email without subject or body, following SASL authentication completing successfully there is a failure to send the email itself correctly because mailx gives an incorrect response. It looks as if there is some timing problem in s-nail triggered by glibc-2.33. Perhaps s-nail is making some incorrect synchronization assumptions.

Edit2: s-nail-14.9.21-x86_64-4 does appear to work correctly for (but only for) local emails via postfix and procmail (that is, not involving a relay).

@chrisVV

I do have it set up with gmail smtp. I'm not very knowledgeable in this area so I can't really explore any further. Like I said in my previous post I rebuilt s-nail-14.9.21-x86_64-4 against glibc 2.22, but if there are any tests you would like me to run on my end to help you diagnose the problem just let me know.

That's fine, I was just wondering whether the defect affects relays other than gmail, and I have established that it does.

By the way, you can get the original s-nail-14.9.21-x86_64-1.txz from http://slackware.uk/cumulative/slack...t/slackware64/ . That site has saved me a number of times when updated packages have had defects.

This is great! Thank you

Here is a new s-nail release, which addresses ssl-problems.
https://lists.sdaoden.eu/pipermail/s...ry/001401.html
https://ftp.sdaoden.eu/s-nail-14.9.22.tar.xz

3 members found this post helpful.

This has resolved the issue completely on my system .

3 members found this post helpful.

Yes, s-nail-14.9.22 fixes the problem for me.

2 members found this post helpful.

It seems that fixes the lock problem too.

2 members found this post helpful.