Greetings,
The PEAR::Mail library works fine..no it works GREAT for
sending plaintext
messages (without any attachments). However, when I
recently had to create
a little script to send emails with logfile attachments, I
started by trying
to use PEAR::Mime_Mail. I am left wondering if this
library is actually
not intended for allowing one to compose email messages with
attachments and
serves some other obscure purpose. I had so much difficulty
getting it to
work that I ended up having to go find a different library
to do what I
needed. The alternative I found was htmlMimeMail15, which
is available from
htt
p://www.phpguru.org/static/htmlMimeMail5.html.
The htmlMimeMail library seems very similar
PEAR::Mail/PEAR::Mail_Mime,
except that you can add attachments without having to know
the intimate
inner workings of the MIME/email formats, encoding, and/or
protocols. It
also had clear documententation with good examples (compared
to Mail_Mime)
(I would love to help PEAR with the documentation for
Mail_Mime, but that
would be difficult seeing as how I am unable to get it to
work myself).
Is it possible that another PEAR package needs to created
on top of
Mail_Mime to further abstract the large amount of nitty
gritty protocol
details that PEAR::Mail_Mime requires? Or perhaps the
mistake is simply on
my end due to the confusing documentation? Or is this
package intended for
some other purpose than sending emails with attachments?
Regardless..I just
wanted to find out if there is some way we can turn this
thing around..
Best,
Jay Taylor
--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php
|