SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I queried the S-nailx mailing list about curious behavior (I got the message ' Snorkeling on empty pipe') The current lead Steffen (Daode) Nurpmeso replied:
Quote:
Oh really! Please let me assume it is only because of OpenSSL, rather than because of the software as such, right? :-) The .SlackBuild script of Johannes Schöpfer is the most complicated think i have ever seen! I really had to think about it, but luckily and successfully avoided that, then.
We are at Slackware, too! Thank you, this is really nice!! I did not even know that Slackware is still truly alive, but i think: good that it is.
I don't use it, but does he really think that SlackBuild script is complicated? It seems pretty straightforward to me. I hope he doesn't take a look at some of Eric Hemeleers' scripts.
Hmmm... a welter of 'obsolete syntax' error messages when I send a test message using gmail and previously successful syntax in ~/.mailrc. Referred to the man pages by these errors so a little more research required here...
For the record the 'obsolete syntax' errors are here:
Code:
andrew@ilium~$ echo "Testing, Testing, Testing" | nail -v -s "My test..." andrew.xxxxxxxxxxxxxxxxx@gmail.com
mailx: Loading /etc/nail.rc
mailx: Loading /home/andrew/.mailrc
mailx: Obsoletion warning: variable superseded or obsoleted: smtp
mailx: Obsoletion warning: variable superseded or obsoleted: smtp-auth-user
mailx: Obsoletion warning: variable superseded or obsoleted: smtp-auth-password
mailx: Obsoletion warning: variable superseded or obsoleted: ssl-verify
mailx: P(seudo)R(andomNumber)G(enerator): getrandom(2/3) + builtin ARC4
mailx: Obsoletion warning: Use of old-style credentials, which will vanish in v15!
Please read the manual section "On URL syntax and credential lookup"
mailx: Obsoletion warning: please don't use *smtp*: assign a smtp:// URL to *mta*!
mailx: Resolving host smtp.gmail.com:587 ... done
mailx: Connecting to 74.125.68.108:587 ... connected.
andrew@ilium~$
The message goes through but the rc syntax obviously needs adjusting for this newer version...
Hmmm... a welter of 'obsolete syntax' error messages when I send a test message using gmail and previously successful syntax in ~/.mailrc. Referred to the man pages by these errors so a little more research required here...
For the record the 'obsolete syntax' errors are here:
Code:
andrew@ilium~$ echo "Testing, Testing, Testing" | nail -v -s "My test..." andrew.xxxxxxxxxxxxxxxxx@gmail.com
mailx: Loading /etc/nail.rc
mailx: Loading /home/andrew/.mailrc
mailx: Obsoletion warning: variable superseded or obsoleted: smtp
mailx: Obsoletion warning: variable superseded or obsoleted: smtp-auth-user
mailx: Obsoletion warning: variable superseded or obsoleted: smtp-auth-password
mailx: Obsoletion warning: variable superseded or obsoleted: ssl-verify
mailx: P(seudo)R(andomNumber)G(enerator): getrandom(2/3) + builtin ARC4
mailx: Obsoletion warning: Use of old-style credentials, which will vanish in v15!
Please read the manual section "On URL syntax and credential lookup"
mailx: Obsoletion warning: please don't use *smtp*: assign a smtp:// URL to *mta*!
mailx: Resolving host smtp.gmail.com:587 ... done
mailx: Connecting to 74.125.68.108:587 ... connected.
andrew@ilium~$
The message goes through but the rc syntax obviously needs adjusting for this newer version...
Yes, it appears from v15 we will have to use the 'set mta=submissions://[gmail-addr]:[password]@smtp.gmail.com:587' instead for gmail, although I haven't tried it.
smtp-auth and smtp-use-starttls remain valid in v15. I can't see why the new 'submissions' form is thought to be an improvement for the remainder.
Yes, it appears from v15 we will have to use the 'set mta=submissions://[gmail-addr]:[password]@smtp.gmail.com:587' instead for gmail, although I haven't tried it.
smtp-auth and smtp-use-starttls remain valid in v15. I can't see why the new 'submissions' form is thought to be an improvement for the remainder.
Well, I have nutted out a successful version with nail / mail v14.9.11 which works well enough. Still many, many options that could be tweaked but for my purposes the following ~/.mailrc works with gmail:
Code:
#--------------------------------------------#
# Setting mailx version v14.9.11 for gmail #
#--------------------------------------------#
# Use v15.0 compatibility mode
set v15-compat
# See the whole process, especially for troubleshooting:
# set verbose
# Essential setting: select allowed character sets
set sendcharsets=utf-8,iso-8859-1
# Default directory where we act in (relative to $HOME)
set folder=mail
# My actual address obfuscated here:
set from="xxx.xxx.xxx@gmail.com"
# Request strict TLL transport layer security checks
set tls-verify=strict
set tls-ca-file=/etc/ssl/certs/ca-certificates.crt
set tls-ca-no-defaults
set smtp-use-starttls
set smtp-auth=login
# When sending messages, wait until the Mail-Transfer-Agent finishs.
# Only like this you will be able to see errors reported through the
# exit status of the MTA (including the built-in SMTP one)!
set sendwait
# And of course put your own gmail username and
# password here in the obvious places:
set mta=smtps://USER:PASSWORD@smtp.gmail.com:465
#--------------------------------------------#
Setting 'verbose' in this config reveals many of the better options that can be used to fine tune this. So I guess I am now quite happy with the new version in -current
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.