filters/rules handle messages differently
Dear,
I am using some templates in my Thunderbird 115.1.0 for windows 11 that are AUTO-sent based on certain rules/filters. ie when a revieved e-mail contains a specific word in the message a rule will reply to the message using template 1.
I am now attaching a .gpx file with the template message. The message is sent as usual, but the attachement is not attached to the message (no attachement in the e-mail stored in sent-items). The message is recieved as an message with the added line: "This is a multi-part message in MIME format. --------------TwIF08u4BWQAhVjYA9nsShou Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit " Also a lot of asci-characters are in the message.
The strange this is: if I sent the very same template manually it all works like a charm. The message is sent with the GPX-file attached to it, and recieved with the complete and functioning attachement.
This leaves me to think Thunderbird handels message automatically differently from manually. Is there any way around this?
Looking forward to your response.
Kind regards.
Tất cả các câu trả lời (3)
After you modified the template to include the attachment, did you then access Message Filters and edit the auto reply filter - in other words did you reselect the updated, modified and saved template or does it still think it's using the original cached template?
thnx for your response. I've modified the message and edited the auto reply filter to include the new template. Im sure the new template is used.
To be extra certain I've created a new template with the attachement.
Both attempts result in the same response: This is a multi-part message in MIME format. --------------9E6JV0IwnjCBrpsRuNRESS1u Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
without the file attached.
OK I agree with you. I've just done a load of testing. I fully understand the issue.
I've done some digging for bugs and discovered this has been a bug for 18 years. https://bugzilla.mozilla.org/show_bug.cgi?id=326181
Although the info said it did not need reporting again - I decided to report it as a new bug for supernova in the hope it finally gets some attention. https://bugzilla.mozilla.org/show_bug.cgi?id=1848659