[SOLVED] mailx error on slackware-current

ardya · 02-17-2021, 09:04 AM

Hi, getting the following running 'mail' on the command line. I don't know if this started after the big update this week. As root I saw there was new mail after the update, ran 'mail', get error from root and user:

Code:

ardy@slackware-current:~$ mail
mailx: Creating file (dot) lock for /var/spool/mail/ardy . failed
mailx:   Fishy!  Is someone trying to "steal" foreign files?
mailx:   Please check the mailbox file etc. manually, then retry
mailx: Unable to (dot) lock mailbox, aborting operation: Resource temporarily unavailable
mailx: Creating file (dot) lock for /var/spool/mail/ardy . failed
mailx:   Fishy!  Is someone trying to "steal" foreign files?
mailx:   Please check the mailbox file etc. manually, then retry
mailx: Unable to (dot) lock mailbox: Resource temporarily unavailable
mailx: There are new messages in the error message ring (denoted by ERROR),
mailx:   which can be managed with the `errors' command
ERROR# Continue, possibly losing changes [yes]/no?

root@slackware-current:~# ll /var/spool/mail/
total 92
-rw-rw---- 1 ardy    mail     0 Mar 22  2020 ardy
-rw-rw---- 1 ircuser mail     0 Dec 10 17:57 ircuser
-rw-rw---- 1 root    root 91920 Feb 16 23:29 root

root@slackware-current:~# ls -ld /var/spool/mail
drwxrwxrwt 2 root mail 4096 Feb 16 23:29 /var/spool/mail/

3rensho · 02-17-2021, 09:36 AM

Just checked mine and see the same thing.

ardya · 02-17-2021, 12:28 PM

Piping to mail also fails...

Code:

echo test|mail -s test ardy@str002.ldev
postdrop: warning: unable to look up public/pickup: No such file or directory

Not related. Disregard this reply.

Mechanikx · 02-17-2021, 02:52 PM

I'm having the same problem. I'm pretty sure this started after 2/15 update because I have a script that backs up my system and then sends an email to me confirming the backup. The email still goes through but it no longer has a subject or message. For example

Quote:

echo "Backup created on $(date)" | mail -s 'backup up success' me@email.com

results in an empty email with no subject. Whereas before the 2/15 update it worked.

nobodino · 02-18-2021, 12:53 AM

same result here.

franzen · 02-18-2021, 01:34 AM

Someone already did report this to the s-nail mailinglist, no answer yet.
https://lists.sdaoden.eu/pipermail/s...ry/001397.html

bathory · 02-19-2021, 03:09 AM

FYI mailx is fixed with the latest s-nail update

ardya · 02-19-2021, 05:46 AM

Except now instead of returning to prompt when there's no mail, you have to manually quit. This is changed behaviour.

Code:

ardy@slackware-current:~$ mail
mailx version v14.9.21.  Type `?' for help
/var/spool/mail/ardy: 0 messages
No more mail.
? q

3rensho · 02-19-2021, 05:55 AM

I've always had to type "q" to quit as long as I have been using it. Even when there was no mail.

ardya · 02-19-2021, 02:43 PM

Marking as solved since the original reported problem is now resolved from upstream.