1135608 - Base64 encoded iCalendar attachment is not displayed in any way

Status: RESOLVED INCOMPLETE

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Adam Hauner]

Attachment: source of e-mail with vCalendar attachment

User agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32.1
Build: 20150204202218

I received attached e-mail, which looks in SeaMonkey as totally blank. In source is visible Base64 encoded attachment containing vCalendar file. Attachment visible in e-mail source is not present in Attachments list. I haven't Lightning installed.

xref:
bug 242937 - vcalendar /ical attachment displayed as text in mail 
             in stead of attachment

Comment 1

[Rainer Bielefeld]

a1) Also Attachment does not show a calendar in SeaMonkey Browser 2.44  Mozilla/5.0
   (en-US Language pack) (Windows NT 6.1; Win64; x64; rv:47.0)  Gecko/20100101 
   Firefox/47.0 Build 20160608085536  (Default Classic Theme) on German WIN7 64bit
a2) But FF 50.0a1 (2016-06-13) fails either, also shows "Attachment is not
    viewable in your browser because its MIME type (message/rfc822) is not
    one that your browser is able to display. " So this one might be a core 
    problem?

@reporter:
b) Any indication that we promise to be able to show such attachments?
   If not "Enhancement Request" for this one might be more applicable.
c) What other email clients are able to show such attachments

Please answer without citing, simply start your reply like
a): <answer>

Comment 2

[Rainer Bielefeld]

Probably a DUP of one of our "Does not show Att. / ics attachments" like "[Bug 1334937] No preview and no reading of email attachment files .ics in ver 2.46 - in 2.39 all worked OK", but without more information it's impossible to decide ...

Never confirmed by a second user, no response, so I close this one for now.
@Reporter: Please feel free to reopen this Bug if you still can reproduce the problem with a current SeaMonkey version and a current OS and if you can contribute a step by step instruction how other users can reproduce the problem reliably due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>  (containing every key press and every mouse click).