Re: Re: Need help tracking down a Mail_Mime bug

On Wednesday 19 May 2004 11:58 am, Justin Patrin wrote: > Klaus Guenther wrote: > > Justin Patrin wrote: > >> Ian Eure wrote: > >>> On Tuesday 18 May 2004 03:17 pm, Justin Patrin wrote: > >>>> Ian Eure wrote: > >>>>> What's going on here? Where is the Content-Type header getting > >>>>> lost, and > >>>>> why is it only when it's coming from Mail_Mime? > >>>> > >>>> Are you trying to set the multipart content type yourself? If so, you > >>>> shouldn't be. All you have to do is use setHTMLBody() and it will > >>>> automatically set up the content type(s) for you. If you also have a > >>>> setTXTBody(), you'll get a multipart/alternative message. > >>> > >>> No, I'm using setHTML/TextBody(). Oddly enough, it's working now. I > >>> had mistyped the name of the variable which had the regular > >>> (From/Subject) headers when passing that to Mail_Mime::headers(), and > >>> that appears to be the source of the problem. > >>> > >>> It still doesn't make sense to me, but it is working. > >> > >> Ah...well, if there's no From, I believe that it won't send the message. > > > > Afaik, if you're using the php mail function, there's usually a default > > From. > > But if you're using PEAR::Mail, there may not be. > The 'mail' back-end uses mail() to send the message.