Description of problem:
When forwarding an email that itself is a forward with an attachment, the
attachments are dropped. This occurs if you use "Quoted" or "inline" method for
attachment. If you use the "attachment" forwarding method, the full email is
attached, but as a text file, and evolution does not parse the internal MIME headers
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Receive a forwarded mail with an attachment
2 [details]. Attempt to forward the email using inline or quoted methods
forwarded email contains message, but no attachments
Attachments should be attached
When you forward the message as an attachment, you cannot see the internally
attached files in the forwarded mail. When you get the email, however, it shows
the nested attachments correctly.
seems very similar to bug 176263
RHEL 5.2 will re-base Evolution from version 2.8.0 to version 2.12.3.
Can you please test whether this bug is still present in RHEL 5.2?
Reporter, could you please reply to the previous question?
It depends on the content type of the attachment, I can reproduce this with a
text/plain attachment, not necessarily forwarder mail. Thus confirming.
I will pick this upstream bug:
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Richard, if you're still seeing this problem in RHEL 5.3, can you provide a sample email with attachments that we can use to verify? We think we found at least a partial solution, but we're not sure if it would fully cover the problem you're seeing. And I don't want to send this to QA without specific test cases.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.