On Mon, Dec 3, 2012 at 7:13 PM, John Broome <[email protected]> wrote:
> I ran that command and it barfed, but no where near the way yours did: > > echo "foo bar baz" | mail [email protected] -s "foo bar baz test" > [jbroome@host ~]$ send-mail: invalid option -- 's' > send-mail: invalid option -- 's' > send-mail: fatal: usage: send-mail [options] > Gotta ask some questions before evaluating whether this is useful or relevant: What OS? What package was installed? Was it mailx? What package and what version of said package provides your "mail" command? On Mon, Dec 3, 2012 at 7:13 PM, John Broome <[email protected]> wrote: > First hit for your error: > > http://setaoffice.com/2009/12/17/sendmail-warning-runasuser-for-msp-ignored-check-group-ids/ Thanks for that, but I had already checked about 5 of the top ten search results, and had reworked my search several different ways. The suggestions in those threads dealt with the /usr/sbin/sendmail.sendmail command needing to be setgid and owned by the same group that has access to /var/spool/clientmqueue. Both of these conditions were already satisfied on the affected system. There was another suggestion that the clientmqueue be made world writeable. Bad idea, in my opinion, which was verified in later comments on the threads in question. On Mon, Dec 3, 2012 at 7:13 PM, John Broome <[email protected]> wrote: > You mean the way it's listed in the manpage for mail? > Oh, did you mean to say 'RTFM n00b!'? Are you implying that all arguments listed on manpages must strictly adhere to the order in which they are listed in the first examples on the manpage? I have never assumed those examples to be an exclusive list of argument permutations. For instance: 'ssh -l user host command', and 'ssh host -l user command' ...both work and perform the exact same task. That's the whole point of "named arguments". It means that the order in which they are provided on the command line should not matter. When there is only one (type) of unnamed argument on a command line, such as the list of recipients of a mail command, then there is no _technical_ reason that the order of arguments should matter. (Full disclosure, the "host" argument can be repositioned in an ssh command, but not the "command" argument...probably because ssh assumes all arguments that follow a token it doesn't recognize must be arguments to the 'command', and not to ssh, itself. So in that case, there _is_ a technical reason for the dependency...) I hate to ask this of you, John, but please keep your snarky 'RTFM n00b!' comments to yourself. This is a public list, and like it or not, you are representing all of LOPSA when you make comments like that in this communication forum. Snarkiness is unprofessional. It does not reflect well upon you and it does not reflect well upon the LOPSA community; and I'm really not certain what you intended to accomplish. If you just wanted to somehow shame me into silence, then obviously you didn't meet your objective. So again, thank you for your contribution. I really do welcome any useful contribution. I do not welcome further snarky comments. Thanks, all!
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
