Rails 3 ActionMailer attachments incorrectly shown inline by Yahoo! Mail #895

Closed
lighthouse-import opened this Issue May 16, 2011 · 2 comments

Comments

Projects
None yet
1 participant

Imported from Lighthouse. Original ticket at: http://rails.lighthouseapp.com/projects/8994/tickets/6514
Created by Mohit Jain - 2011-03-03 23:45:55 UTC

I sent attachments to Yahoo mail from a few different sources and I tried different content types, transfer encodings (e.g., Base64), different kinds of attachments, etc. The only constant I can find between those that Yahoo shows properly and those it fails on is that the successes do not use parameter folding, e.g.,

Success

Content-Disposition: attachment; filename="event.ics"

Fail

Content-Disposition: attachment;
filename="event.ics"

This (correct) folding appears to be hardwired into the mail gem that Rails uses and I didn't try another way of truly isolating it; I have to say I'd be surprised if that were really the problem.

Regardless, Yahoo is rendering non-inline attachments as inline, so if this is a significant problem for your customer base, I'd take it up with Yahoo directly; maybe they'll fix it or offer you a more concrete statement about what triggers it so you can work around it. For what it's worth, Yahoo does allow the user to access the attachment correctly as it should with Content-Disposition of "attachment"; it's just also showing it as if the Disposition where "inline."

The problem is with New yahoo mail. (Claasic yahoo, Gmail, Hotmail every where its fine.)
Detailed stuff is present here

[Stackoverflow Question](http://stackoverflow.com/questions/5062531/rails-3-actionmailer-attachments-incorrectly-shown-inline-by-yahoo-mail/ "Stackoverflow Question"

Imported from Lighthouse.
Comment by Andrew White - 2011-03-04 07:26:23 UTC

The RFC talks about parameter values of less than 78 characters being presented as a single token - what happens if you send a file with a really long name?

Attachments saved to Gist: http://gist.github.com/971799

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment