Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Thursday, 9 April 2020 09:53:07 BST Caveman Al Toraboran wrote: > On Thursday, April 9, 2020 10:49 AM, Michael wrote: > > I have not configured nullmailer to know its internals, but assuming you > > have not removed '127.0.0.1 localhost' from your /etc/hosts it should > > work. > interesting. i had (no work): > > `127.0.0.1 localhost myhostname` > > but it only worked when i swapped order of `myhostname`: > > `127.0.0.1 myhostname localhost` > > so now it's working, but me surprise! me cannot sense. do u sense? Hmm ... odd. It may be specific to nullmailer code, which I am not familiar with. The sequence in /etc/hosts file is: # IP_ADDRESScanonical_hostname [aliases...] 127.0.0.1 localhostmy_PC Userspace applications ought to resolve 'localhost' to 127.0.0.1, which is a special hostname, rather than an alias. You can read more about localhost in RFC 1912, starting at the bottom of page 13: https://tools.ietf.org/html/rfc1912 Given the above I would expect an application to resolve "localhost" to 127.0.0.1 and potentially fall over on some alias, depending how it parsed / etc/hosts file. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Thursday, April 9, 2020 10:49 AM, Michael wrote: > I have not configured nullmailer to know its internals, but assuming you have > not removed '127.0.0.1 localhost' from your /etc/hosts it should work. interesting. i had (no work): `127.0.0.1localhost myhostname` but it only worked when i swapped order of `myhostname`: `127.0.0.1myhostname localhost` so now it's working, but me surprise! me cannot sense. do u sense?
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Tuesday, 7 April 2020 11:01:45 BST Caveman Al Toraboran wrote: > On Friday, April 3, 2020 10:42 AM, Caveman Al Toraboran wrote: > > nullmailer is now configured, and test with`echo "Subject: ..." | sendmail > > -v m...@dom.com` works. but, smartd's test mail is not working, with this > > error:> > > Apr 03 10:15:09 blah smartd[219171]: Test of to m...@dom.com > > produced unexpected output (65 bytes) to STDOUT/STDERR: > > Apr 03 10:15:09 blah smartd[219171]: mail: cannot send message: > > Process exited with a non-zero status Apr 03 10:15:09 blah > > smartd[219171]: Test of to m...@dom.com: failed (32-bit/8-bit > > exit status: 9216/36)> > > tried to test`mail` in isolation: > > > > echo "test body" | mail -s "test subj" m...@dom.com --debug-level=3 > > mail: sendmail binary: /usr/sbin/sendmail > > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > > mail: mu_mailer_send_message(): using From: me@localhost > > mail: Sending headers... > > mail: Sending body... > > mail: /usr/sbin/sendmail exited with: 1 > > mail: progmailer error: Process exited with a non-zero status > > mail: cannot send message: Process exited with a non-zero status > > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > > > > i've also monitored `watch -n .1 tree /var/spool/nullmailer/` and verified > > that the queue never gets filled with any message when i use the `mail` > > command (which, i think, is what `smartd` uses). but, the queues get > > filled when i used `sendmail` by the command in my 1st paragraph. > > extra info: i've just found that it only fails > when sender address is `@locahost`. if i manually > execute `mail` with `-aFrom:lol@safsdfsd` it will > work, even tho the `From:...` is total garbage. > > but somehow just can't work when > `From:lol@localhost`. something personal going on > with `mail` and `localhost`. > > any idea what's going on? and what did i do > wrong? hence what's the most elegant way to fix > this? I have not configured nullmailer to know its internals, but assuming you have not removed '127.0.0.1 localhost' from your /etc/hosts it should work. Otherwise, I found these pages which may be of use in troubleshooting it: http://troubleshooters.com/linux/nullmailer/ http://troubleshooters.com/linux/nullmailer/landmines.htm signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Friday, April 3, 2020 10:42 AM, Caveman Al Toraboran wrote: > nullmailer is now configured, and test with`echo "Subject: ..." | sendmail -v > m...@dom.com` works. but, smartd's test mail is not working, with this error: > > Apr 03 10:15:09 blah smartd[219171]: Test of to m...@dom.com produced > unexpected output (65 bytes) to STDOUT/STDERR: > > Apr 03 10:15:09 blah smartd[219171]: mail: cannot send message: Process > exited with a non-zero status > Apr 03 10:15:09 blah smartd[219171]: Test of to m...@dom.com: > failed (32-bit/8-bit exit status: 9216/36) > > > tried to test`mail` in isolation: > > echo "test body" | mail -s "test subj" m...@dom.com --debug-level=3 > mail: sendmail binary: /usr/sbin/sendmail > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > mail: mu_mailer_send_message(): using From: me@localhost > mail: Sending headers... > mail: Sending body... > mail: /usr/sbin/sendmail exited with: 1 > mail: progmailer error: Process exited with a non-zero status > mail: cannot send message: Process exited with a non-zero status > mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, > dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 > > i've also monitored `watch -n .1 tree /var/spool/nullmailer/` and verified > that > the queue never gets filled with any message when i use the `mail` command > (which, i think, is what `smartd` uses). but, the queues get filled when i > used `sendmail` by the command in my 1st paragraph. extra info: i've just found that it only fails when sender address is `@locahost`. if i manually execute `mail` with `-aFrom:lol@safsdfsd` it will work, even tho the `From:...` is total garbage. but somehow just can't work when `From:lol@localhost`. something personal going on with `mail` and `localhost`. any idea what's going on? and what did i do wrong? hence what's the most elegant way to fix this?
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Friday, 3 April 2020 20:48:12 BST Grant Taylor wrote: > On 4/2/20 10:47 PM, Caveman Al Toraboran wrote: > > wow, didn't know sendmail's syntax was so hard it needed a compiler > > > > :D thank you very much for your help. highly appreciated. > > I think that's an inaccurate statement. > > First, m4 is a macro package, not a compiler. > > Second, the macros are used to reduce the size of the macro config (mc) > file to something manageable instead of hundreds of lines that are easy > to cause a syntax mistake. > > Third, the macros made the mc file more semantics in nature instead of > Sendmail config file (cf) specific. Meaning that one line allows > changing values in multiple places that use the common information, like > the domain name(s). > > My home system has a 33 line mc file (including comments) that expands > to 1915 lines of cf file (including comments). > > Both the input and output is ASCII text. Humans can read both of them. > Humans that understand cf syntax can read both files. > > This is far from turning something into byte code. I have used sendmail in the past and found it a pain to get my head around some of its more esoteric set ups, for reasons Grant has already explained. I can't recall the details, but it involved convoluted relaying through some american ISP, tiered fall-backs in case of delivery failure, self-signed TLS certs and a number of local/external email accounts and multiple aliases. Once the pain of understanding its sytanx, setting it up and testing was done with, the system worked *exactly* as I wished, day in day out, without errors and without missing messages. For years. It was so reliable, I had to re- familiarise myself with its syntax whenever I wanted to change something in its behaviour. A nice problem to have, compared with so many poorly written applications today. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On 4/3/20 4:01 PM, Grant Edwards wrote: If you want to become an ultra-professional, that's fine. If you just want to be able to send mail interactively from mutt... OK, that's a bad example now that mutt has built-in SMTP client capabilities. How about ... if you only want to get email off your local box to a remote server and don't care how it's done, then Sendmail probably isn't your best / easiest / first choice. ;-) -- Grant. . . . unix || die
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On 4/2/20 10:47 PM, Caveman Al Toraboran wrote: wow, didn't know sendmail's syntax was so hard it needed a compiler :D thank you very much for your help. highly appreciated. I think that's an inaccurate statement. First, m4 is a macro package, not a compiler. Second, the macros are used to reduce the size of the macro config (mc) file to something manageable instead of hundreds of lines that are easy to cause a syntax mistake. Third, the macros made the mc file more semantics in nature instead of Sendmail config file (cf) specific. Meaning that one line allows changing values in multiple places that use the common information, like the domain name(s). My home system has a 33 line mc file (including comments) that expands to 1915 lines of cf file (including comments). Both the input and output is ASCII text. Humans can read both of them. Humans that understand cf syntax can read both files. This is far from turning something into byte code. -- Grant. . . . unix || die
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On 4/2/20 8:23 PM, Grant Edwards wrote: It's very powerful but the configuration file format is almost impossible to understand, so people developed an m4 application that accepted a _slightly_ less cryptic language and generated the sendmail configuration file. The configuration file is far from impossible to understand. Calling it a configuration file is sort of a misnomer in that it's more of a programing language than a configuration file. Some have even said that it's Turning complete. It does have some things going against it though. 1) It is highly dependent on the tab character (one or more) being used to separate two parts of specific lines. This is easily visually lost as well as frequently lost with bad copy & paste. But it's trivial to know about and correct. (Compare that to Python that has lost all of it's leading white space.) 2) The "config" file is really multiple sub-routine that are called in specific instances and do very specific things. You must know which one you need to use when. 3) Sendmail's logic is different than what most people are used to. It's not quite RPN. But it's different enough that many people have problems with it. I think it's more like relay logic. Each line in a rule-set has an opportunity to apply to the current working space. Each line can modify the working space, possibly directly or indirectly by calling other things. If you aren't careful, the working set can be inadvertently matched by multiple lines (rules). As such, the working set is specifically modified so that other lines don't match if they should not. There is a lot of pattern manipulation to keep track of and it takes practice. I'm sure that there are others. But those are the big ones that come to mind at the moment. At it's peak back in the early 90's there were approximately five people in the world who actually understood sendmail, and none of them ever worked where you did. I don't know about the '90s, but I do know that in the '00s and '10s, your statement is exaggeration to the point of being hyperbole. I have witnessed an active Sendmail support community for about 15 of the last 20 years. Most of that support was via the comp.mail.sendmail newsgroup. The rest of us stumbled in the dark using the finely honed cargo-cult practices cutting and pasting random snippets out of example configurations to see what happened. Your lack of use of resources doesn't mean that said resources wasn't available. Usually what happed is that mail was lost or flew around in a loop multiplying to the point where a disk parition filled up. Yep. That said, sendmail has features that no other MTA has. For example, it can transfer mail using all sorts of different protocols that nobody uses these days. It's not just (on the wire) protocols that sendmail supports. Many of which are effectively obsolete save for specific microcosms. Sendmail also supports interfacing with other programs in a very flexible manner. It is fairly easy to have Sendmail support Mailman (et al.) in such a way as that you don't need to change anything on the email server when adding or removing mailing lists. No, I'm not talking about automated alias generation. There is no need for alias generation when Sendmail and Mailman are connected properly. Sendmail quite happily supports LMTP into local mail stores / programs. This is quite handy when you want something like a recipient's sive filter to be able to reject a message. Back in the 90's a number of replacement MTAs were developed such as qmail, postfix, exim, etc. When you installed one of these, (instead of the classic sendmail), they would usually provide an executable file named "sendmail" that accepted the same command line arguments and input format that the original did. That allowed applications who wanted to send email to remain ignorant about exactly what MTA was installed. Yep. The "sendmail" command has become a de facto industry standard that most MTAs emulate. -- Grant. . . . unix || die
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On 4/2/20 6:26 PM, Caveman Al Toraboran wrote: though i'm a bit curious about sendmail (if your time allows). Feel free to ask questions about sendmail. I'll do my best to answer. do you mean the ebuild "sendmail"? or the command "sendmail"? In this context, ebuild as a reference to the MTA known as Sendmail. i used to think it's a swiss-army kind of tool (used to call "sendmail" in my cgi scripts decades ago without any infrastructure; by just directly zapping recipient's smtp gateway). Yes, Sendmail can e a Swiss Army knife. That's one of it's advantages. That's also one of it's disadvantages. Your historic use of Sendmail is an example of using a local queuing MTA. Your CGI scripts passed the message off to the queuing MTA and didn't need to worry about what to do if the remote mail server couldn't be reached. You didn't have to bother with detecting the error and reporting it to the end user via the web form. You didn't have to bother with storing information for later retry. The local queuing MTA did all of that for you. -- Grant. . . . unix || die
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On 4/2/20 8:18 AM, Grant Edwards wrote: Then DO NOT use sendmail. Sendmail is only for the ultra-professional who already knows how to configure it (not joking). I take exception to that for multiple reasons: 1) Bootstrapping - you can't learn something without actually using it. 2) I've been quite happily using Sendmail on multiple platforms for 20 years. 3) Sendmail is capable of working in every single email scenario that I've seen in said 20 years. The same can't be said for other MTAs. If all your mail gets sent via a single SMTP server at your ISP (or wherever), then Sendmail is definitely not what you want. That depends. If you have a fleet of Sendmail servers, chances are good that you will prefer to re-use the same solution, even in small / simple role. Read: The Devil that you know. If you don't need local queueing (so you can send email while offline), then I'd pick ssmtp. (20)ProTip: You really do want local outbound queueing /somewhere/ on box. You don't want your web application to error out when it can't reach it's SMTP server. You don't want t loose that receipt for the transaction that the customer just made. Can you regenerate the receipt? ;-) You can have each application do it's own queuing / re-sending, r you can rely on the local MTA to do it for you. Where do you want the queuing complexity? A local queuing MTA is simple and solves a LOT of problems. If you want something even more sophisticated (e.g. something that can deliver mail locally and receive inbound mail using SMTP), then postfix or exim would probably the be the next step up: I would add Sendmail to the front of that list. But I might be biased. I've read claims that there are things you can do with sendmail that Exim or Postfix can't handle, but I'm not sure I believe it. I am sure I'll never need to do any of those things. I don't know Exim or Posfix well enough to comment with any authority. I do know that I Sendmail, Postifx, and Exim all handle (E)SMTP without any problem. I think that Postfix can be made to handle UUCP. Sendmail has four different ways that it can use UUCP, built in. I have no idea about Exim. Sendmail can easily work with other protocols, Mail11, fax, pager, news gateway (send and / or receive). It's also easy to add additional protocols without needing to recompile anything, only configuration changes are needed. I don't know where in the list I lost Postfix and / or Exim, but I expect that they didn't make it through the last paragraph. For a long time, Sendmail did have one claim to fame that no other MTA had. Specifically Sendmail had the ability to use milters (mail filters) and filter email during the SMTP transaction. It's trivial to hook ClamAV, SpamAssassin, and just about anything you want into checking mail during the SMTP transaction such that you have the ability to reject, not bounce, the message. Thus making the sending host be responsible for it. I'm sure there are many more and far more esoteric things that Sendmail can do. Though I doubt that many of them are as germane today as they were in the mid '90s. I was recently playing with the ability to have a domain spread across multiple servers and configuring Sendmail to route messages to the proper back end server, a feature known as LDAP routing. Yes, Sendmail has a lot of power, much like unix. It will happily hand you a loaded gun, encourage you to point it at your feet and empty the magazine as fast as possible. When you're done, it will help you reload and do it again. If you know how to wield this power Sendmail can be a wonderful tool that can be used in all of the scenarios described in this thread. It's also relatively trivial to have Sendmail be a basic queuing outbound only MTA that uses ISP smart hosts to provide SMTP services to local applications. But I really object to the "ultra-professional" comment, because everybody has to start somewhere. -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Thursday, April 2, 2020 6:18 PM, Grant Edwards wrote: > Nullmailer is also a good option with the added bonus of queueing > outbound mail while you're offline.: nullmailer is now configured, and test with `echo "Subject: ..." | sendmail -v m...@dom.com` works. but, smartd's test mail is not working, with this error: Apr 03 10:15:09 blah smartd[219171]: Test of to m...@dom.com produced unexpected output (65 bytes) to STDOUT/STDERR: Apr 03 10:15:09 blah smartd[219171]: mail: cannot send message: Process exited with a non-zero status Apr 03 10:15:09 blah smartd[219171]: Test of to m...@dom.com: failed (32-bit/8-bit exit status: 9216/36) tried to test `mail` in isolation: echo "test body" | mail -s "test subj" m...@dom.com --debug-level=3 mail: sendmail binary: /usr/sbin/sendmail mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 mail: mu_mailer_send_message(): using From: me@localhost mail: Sending headers... mail: Sending body... mail: /usr/sbin/sendmail exited with: 1 mail: progmailer error: Process exited with a non-zero status mail: cannot send message: Process exited with a non-zero status mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 i've also monitored `watch -n .1 tree /var/spool/nullmailer/` and verified that the queue never gets filled with any message when i use the `mail` command (which, i think, is what `smartd` uses). but, the queues get filled when i used `sendmail` by the command in my 1st paragraph. i like the queue functionality, so it is definitely more suitable for me than ssmtp. but i'm disappointed that it requires the service nullmailer to be running all the time. it should -imo- run in a triggered way upon calling sendmail, and should run once at bootup just to check if queue is not empty. and, if it runs, and is unable to empty the queue (e.g. due to no network availability) then it shall remain running until the network is back and the queue is empty. but, currently, it seems that the null mailer is just always running. disappoint!
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Friday, April 3, 2020 6:23 AM, Grant Edwards wrote: > On 2020-04-03, Caveman Al Toraboran toraboracave...@protonmail.com wrote: > > > though i'm a bit curious about sendmail (if your > > time allows). do you mean the ebuild "sendmail"? > > Yes. I meant the program provided by the "sendmail" ebuild. That is > the MTA named "sendmail" that's been around since the universe cooled > enough to form atoms: > > https://en.wikipedia.org/wiki/Sendmail > > For many years it was the de-facto standard MTA for Unix systems. > > It's very powerful but the configuration file format is almost > impossible to understand, so people developed an m4 application that > accepted a slightly less cryptic language and generated the sendmail > configuration file. At it's peak back in the early 90's there were > approximately five people in the world who actually understood > sendmail, and none of them ever worked where you did. The rest of us > stumbled in the dark using the finely honed cargo-cult practices > cutting and pasting random snippets out of example configurations to > see what happened. Usually what happed is that mail was lost or flew > around in a loop multiplying to the point where a disk parition filled > up. > > That said, sendmail has features that no other MTA has. For example, > it can transfer mail using all sorts of different protocols that > nobody uses these days. > > Back in the 90's a number of replacement MTAs were developed such as > qmail, postfix, exim, etc. When you installed one of these, (instead > of the classic sendmail), they would usually provide an executable > file named "sendmail" that accepted the same command line arguments > and input format that the original did. That allowed applications who > wanted to send email to remain ignorant about exactly what MTA was > installed. > > Exim, postfix, qmail and the others were all still full-function MTAs > intended for a multi-users system. They could route mail to different > destinations (including delivering it locally to a variety of mailbox > types) and accept inbound email from other MTAs. While they were far > easier to set up and maintain than the original sendmail, they were > still massive overkill for a computer that was used only by a single > person where reading mail was done via POP/IMAP and all outbound mail > was handed over to a single outside mail relay. They often didn't > deal well with the fact that they were running on a host that didn't > have a "real" hostname that meant anything to the outside world, and > that the local hostname had nothing to do with the email addresses of > the user(s). > > For that use case, simple MTAs like msmtp, ssmtp, and nullmailer were > written that don't handle incoming mail at all, and where all outbound > mail is sent to a single mail relay host. The first two don't even do > any queuing: if you try to send mail when your relay host is > unreachable, then the send simply fails. > > These too, when installed, provide an executable named "sendmail" that > accepts the same command line options and input format as the original. wow, didn't know sendmail's syntax was so hard it needed a compiler :D thank you very much for your help. highly appreciated. rgrds, cm
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Thursday, April 2, 2020 6:18 PM, Grant Edwards wrote: > Then DO NOT use sendmail. Sendmail is only for the ultra-professional > who already knows how to configure it (not joking). > > If all your mail gets sent via a single SMTP server at your ISP (or > wherever), then Sendmail is definitely not what you want. > > If you don't need local queueing (so you can send email while > offline), then I'd pick ssmtp. NB: ssmtp is a bit old and in need of > a ebuild maintainer, so might not be my first choice if I wasn't > already familiar it. > > https://wiki.archlinux.org/index.php/SSMTP > > Nullmailer is also a good option with the added bonus of queueing > outbound mail while you're offline.: > > https://github.com/bruceg/nullmailer > https://wiki.archlinux.org/index.php/Nullmailer > > If you want something even more sophisticated (e.g. something that can > deliver mail locally and receive inbound mail using SMTP), then postfix > or exim would probably the be the next step up: > > https://wiki.gentoo.org/wiki/Postfix > https://wiki.archlinux.org/index.php/Postfix > > https://wiki.gentoo.org/wiki/Exim > https://wiki.archlinux.org/index.php/Exim > > I've read claims that there are things you can do with sendmail that > Exim or Postfix can't handle, but I'm not sure I believe it. I am > sure I'll never need to do any of those things. thanks a lot for this info. highly appreciated. i'll go with nullmailer (imo suits me best). though i'm a bit curious about sendmail (if your time allows). do you mean the ebuild "sendmail"? or the command "sendmail"? i used to think it's a swiss-army kind of tool (used to call "sendmail" in my cgi scripts decades ago without any infrastructure; by just directly zapping recipient's smtp gateway).
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Thu, 02 Apr 2020 07:03:01 -0400, Caveman Al Toraboran wrote: > > On Wednesday, April 1, 2020 10:20 AM, Ian Zimmerman > wrote: > > > On 2020-04-01 03:51, Caveman Al Toraboran wrote: > > > > > why can't `mail` send emails? below is some info. > > > > Normally the mail program works by execing /usr/sbin/sendmail to to the > > hard part :-P Do you have it? It doesn't have to be the "real" > > sendmail - any MTA program you install usually makes a symlink from > > /usr/sbin/sendmail to itself. > > i got sendmail around. but didn't do any configurations. > > what's the minimum configuration to do? i'm really not > planning anything ultra-professional. i hope it to send > an email the shameless style (just send an smtp message > to the smtp server where my email is hosted) > > Try ssmtp package, I think it will do what you want. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] Re: mail cannot send emails (trying to use it with smartd)
On Wednesday, April 1, 2020 10:20 AM, Ian Zimmerman wrote: > On 2020-04-01 03:51, Caveman Al Toraboran wrote: > > > why can't `mail` send emails? below is some info. > > Normally the mail program works by execing /usr/sbin/sendmail to to the > hard part :-P Do you have it? It doesn't have to be the "real" > sendmail - any MTA program you install usually makes a symlink from > /usr/sbin/sendmail to itself. i got sendmail around. but didn't do any configurations. what's the minimum configuration to do? i'm really not planning anything ultra-professional. i hope it to send an email the shameless style (just send an smtp message to the smtp server where my email is hosted)
