Why is Thunderbird still forwarding email with attachments as eml file
I have have followed all suggestions on this forum and others on how to fix this problem but it still occurs.
It is not the email servers problem as it happens in the thunderbird client as soon as I select to forward an email that has attachments.
In effect it turns the forward email into an eml file and adds it as an attachment to a new email.
As a result the email gets bounced back saying that eml attachments are used to spam people and my email is undeliverable.
I have tried other clients such as outlook connected to the same network and this does not happen.
This only started happening with the last update of the software, which I admit they hadn't done for a while.
Going out of my mind please help.
所有回复 (3)
It's only forwarded as an eml attachment if the message is forwarded as attachment, instead of inline. The default setting is in Options/Composition/General. Individual choices can be made from the context menu, Forward As.
Thanks for the reply
However
The email is received as an ordinary email with jpg files attached.
When I forward this email the original message and the jpg files are encapsulated as an eml file and attached to a new email automatically showing the recipient email address and fwd in the subject
Before this the forwarded email would show the original message in the body and the attached files would be the same jpg files.
I have checked and unchecked and tried all the variants as suggested in this forum and elsewhere but thunderbird still turns every forwarded email that has attachments into an encapsulated eml and attaches that to a new email.
I can only say what happens here: forwarding messages that have attachments, inline, results in a message with the original attachments attached; forwarding as attachment results in a message with the original message attached as an eml file.
Try sending yourself a message with an attachment, using TB, and see if the two ways of forwarding the received message conforms with the above. It may be that it doesn't work for you with only some received messages that are created by certain email clients. Try also with TB in safe mode.