Quoting Suresh Ramasubramanian <[EMAIL PROTECTED]>, who wrote:
> Sam Roberts [mutt-users] <19/06/01 11:51 -0400>:
> > Have you tried this, Suresh?
> > It says "emulates mailx", and that's it.
> > And on my system (RedHat, which is fairly mainstream) mailx
> > does not exist.
>
> So? It'll work. And mailx == /bin/mail, more or less.
Huh? What will work? mailx? And the man page for mail also
only describes it's use as an interactive mail program, not
for programmatic injection of mail into the mail transfer
system.
> > to do this programmatically, I'd like to see them, I am
> > collecting docs on mail interfaces. If you use /sbin/sendmail
> > it's man page has an extremely terse description of what it
>
> suresh@blackehlo:~$ cat test.txt |sendmail -v [EMAIL PROTECTED] [EMAIL PROTECTED]
Why thanks for that even MORE terse example of sendmails command
line. I hope it didn't take you too much time, since it surely
does not describe what sendmail did.
> [EMAIL PROTECTED] Connecting to localhost via relay...
RFC 821 protocol trace, for the RFC-impaired, snipped.
> 250 2.1.5 <[EMAIL PROTECTED]>... Recipient ok
> 354 Enter mail, end with "." on a line by itself
> >>> .
Note that a 0-length message doesn't even come close to being
an RFC822 mail message. Hopefully the receiving MTA will be
adding some headers.
But which ones? Will From: be your user name, or will it be made
equivalent to the envelope sender you provided on the cmd
line? Will a message-id: and date: be added? What about a subject?
And if was an rfc822 message, would any headers it had
be honored? And what about BCC: fields, would they be stripped?
My point is that the documentation of how submitted mail
is processed by mail, mailx, or sendmail is conspiculously
absent, a problem I'm sure you're aware of since you
(rightly) seem to have an appreciation for the value of RTFM.
It's a gaping hole in Unix documentation.
Sam
--
Sam Roberts <[EMAIL PROTECTED]>
