XML attachment error
Dear address!
I need help. For Thunderbird mail, I attach an XML file to a new mail. After sending the xml file is modified with a short line of 20-30 characters ( -------------- dXZxX3pvjmlmbzg880ZXQOez--) at the end. This causes an error when reusing the xml file.
XML file: <...>
-------------- dXZxX3pvjmlmbzg880ZXQOez--
I am using the latest version. 91.1.0 (64 bites) These characters are always changed each time you send an email.I disabled all add-ons and did a virus scan, but the error still occurs. Why this code is at the end of the file. What a correspondent does is some kind of timestamp or filing number. Why the mailer writes to the XML attachment when sending.We did not find such an error for other file types.
Thanks for the help
すべての返信 (5)
Do you have a security/antivirus scanning outgoing mail? It might be adding the characters. Are the characters visible in the Sent folder or only at the recipient's end? Perhaps the recipient's mail service, or your own mail provider, is scanning the attachment and adding the characters.
So far, I've found out: This new line is nothing more than a MIME multipart Content-Type delimiter, it tells you when to start and how long a member of a MIME multipart attachment will last. See https://datatracker.ietf.org/doc/html/rfc2046#section-5.1.1 But it hasn't helped yet, there is an antivirus. There are several machines with similar systems, mail versions and antivirus, but only this one does it. It works well from other places.
Is there an entry for xml content in Preferences/General/Files & Attachments? If there is one, it might affect how TB encodes that type of attachment.
There is nothing associated with the xml content in Preferences / General / Files & Attachments.
I don't know why this particular setup adds the extra line when others do not. If there's some hidden flaw in the profile, you could try creating a new profile from Help/More Troubleshooting, about:profiles, add an account, and see if the problem remains. This might also indicate if it's a profile flaw or a TB bug.