--
You received this message because you are subscribed to the Google Groups "Lift" group.
To view this discussion on the web visit https://groups.google.com/d/msg/liftweb/-/YzltMkJfSTdfRWNK.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
but put's them all in the end anyways. I'm gonna try to change it to
rel_bpi.setDisposition("attachment")
and see what happens. I'll report back.--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
val html_mp = new MimeMultipart("related")
->
val html_mp = new MimeMultipart("mixed")
Diego
--
Diego Medina
Lift/Scala Developer
di...@fmpwizard.com
http://www.fmpwizard.com
It didn't seem to be just Exchange that had problems showing the PDF:s. I colleague with iPhone to Gmail over iMAP experienced the problem too…Just a further thought:I now understand why it's called XHTMLPlusImages. I guess "multipart/related" is typically used to send a complete web page with images that can be referred too by the html [1]. So I guess that was the original use case for this part of Mailer. And I guess "related" is needed in this case. Maybe original author (dpp?) can confirm…?
However, "related" seems to break MY use case for lots of clients, so maybe we should have either a way to control this by the user of Mailer or something more than PlusImageHolder to hold other attachments like PDF:s and some smart way of deciding what header to choose.
I don't remember why I did it that way. :-(
Can you open a ticket with some enhancements to Mailer so we can make it better?