Blanton Lewis wrote:
>
> This is the way that the "memo" headers are created (headers, like
> "subject", that are actually part of the mail body and not the envelope), so
> as far as the mail client is concerned, you're giving more headers for the
> email. You need the blank line to tell the mail client that the body has
> begun.
>
> from RFC 822, section 4.1 ("Message specification, Syntax"):
> message = fields *( CRLF *text ) ; Everything after
> ; first null line
> ; is message body
>
> > [1] If the first line of the mail body begins with at least one (1)
> > non-whitespace, non-colon (:) character and is followed by a
> > colon (:) and anything else, then *NO* body will be received
> > with the Email !?!? For example:
> >
> > host: Odin
> > date: Fri Oct 26 20:35:13 CDT 2001
> > src : trout
Perhaps, that is the case -- need to scrounge around in POSIXness.mail,
again, to see . . .
However, my point is centered around the pingcheck() function in
/etc/cron.daily/multicron-d, which *does not* work in my testing; but,
succeeds with the prepended echo. Of course, this also applies to
mailspacelow() function in that same script, as well as any other
similarly constructed calls to mail.
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
