It's not a bug, it's a security feature...
Email systems can handle attachments differently. My email server, for example, includes virus scanning for all incoming emails. Some attachments will be automatically stripped (i.e. any with a .exe extension), and any flagged with a virus will also be stripped. I can set a size limit on attachments, too - any that are too big are also stripped. I can whitelist and/or blacklist senders, so that only authorized users can send attachments; I can even limit the kinds of attachments (by filename extension) they can send. This does not represent a bug in the system, it represents my ideal of how security should be handled within my email system, and my requirements are probably different than yours or Hitoshi's or Gmail's.
Much of this would be totally transparent to the process sending the email w/ the attachment - it will get the response code indicating success, but the attachment will not be available in the email.
Who knows what gmail may or may not be doing w/ your attachment, since there is no visibility inside of their system to determine what is going on or why.
Long story short, no production Liferay system should ever be using an individual's gmail account for sending out emails.
6.0 has been out for quite awhile and, had there been any issues w/ attachments, there would have been lots of folks complaining about it long before now.
I'm fairly certain it is not a bug. The only way you could prove to me that it was would be to create a stand-alone java program sending email to gmail using your attachment and it going through. I'm willing to bet that if you boiled it down to just these steps you'd probably find gmail was tossing out the attachment and was probably the culprit, not Liferay.
Firmi prego dentro per inbandierare questo come inadeguato.