On Jun 20, 2018, at 4:25 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 6/20/18, Warren Young <war...@etr-usa.com> wrote: >> Two options: >> >> a. Just say that mailx isn’t allowed, because it doesn’t have the correct >> interface. >> >> b. Add a printf-like syntax for building the command with a sensible set of >> substitutions: ‘mailx -s "%s"' > > c. Write a Tcl/Python/Perl/Awk script that transforms the input into a > format suitable for your preferred MUA.
Fine with me. My rule is not to call an interface general-purpose until it’s been used in at least three different contexts. Here, that means at least three different command-line MTAs. It looks like sendmail is the default, and that msmtp looks like it should drop in. What’s the third? I don’t think Sendmail’s sendmail counts as separate from Postfix’s. Rather than call script-wrapped mailx the third test case, I propose mutt. It has a big virtue when the local system doesn’t really have an MTA service, as is common on single-purpose VMs, so you want the CLI MUA to talk to an external SMTP server. Mutt knows how to talk to lots of things, and it has a reasonable TUI for configuring all of that. _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
