Mikhail Teterin wrote:
> = Alter your script to add the 'Content-Type: text/html' header.
> No, I'm afraid, doing this will make the quoted text part of the _body_ of
Ack. Yes, you're quite right. Sorry for the bum advice.
> = > Maybe, cron should apply file(1)-like logic to the e-mailed content?
> = No, cron doesn't need any knowledge of how to render email.
> I was not advocating adding such knowledge. My suggestion was to make cron
> proper Content-Type, so that the /recepient's e-mail program/ will render the
> message correctly. My scripts generate HTML, someone else could be generating
> JPG images (from their web-camera, every morning)...
Hmm, an interesting idea. Now I understand what you meant, that is.
> = The script itself doesn't have to send the mail - cron will handle that if
> = there is any output when it exits, but you /can/ add headers to the message
> = as you need.
> = Just make sure any custom headers come before the empty line delimiter
> = between headers and body, and most mail readers should do the right thing.
> The empty line is inserted by cron before any of the job's own output...
> This method will not work, unless the e-mail reader (incorrectly) acts upon
> parts of the body as if they were headers...
Yep, absolutely right. Got my wrong brain on today!
So it's beginning to look as if your best bet is in fact to make your
script handle sending the mail, and to only have cron itself mail
anything that is the result of an error arising from your script. Not
the cleanest solution, but one that will get your messages formatted
exactly how you want them.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"