A filename in another script is still a filename

Answer A filename in another script is still a filename. RFC 2231 specifies how MIME parameter values can carry a character set, a language tag, and a long value split into continuations. The filename on an attachment is a parameter. When the name is not ASCII, the document gives a way to say so without pretending the name was English. Deleting the characters is not a cleanup. It is a different file name than the one you approved.

The note that started this: RFC 2231, MIME Parameter Value and Encoded Word Extensions, RFC 2231.

This is narrower than the question of an internationalized header. A From name lives in a header. A filename lives on a part. Both can break, and they break in different software. If you use solo ads for affiliate marketing and the creative includes a file whose name is part of the pitch, test that name in a received copy. The affiliate page cannot repair a file the reader saved under a garbled name.

Continuations matter when the value is long. A parameter can be split so older parsers have a chance, and put back together by software that understands the document. A tool that keeps only the first piece will ship a chopped name. Chopped is not a style choice. Ask the seller if their platform preserves the whole value. If they do not know what a continued parameter is, ask them to show the received filename instead of defining the word.

What does RFC 2231 add to a MIME parameter?

It specifies how a parameter value can carry a character set, a language, and a long value continued across pieces. A filename written in another script can be a real parameter. It is not noise to delete.

Character set means which repertoire the bytes belong to. Language means which language a reader might associate with the text. Neither one is a guess a later hop should invent. If the sending software drops the marker and keeps the bytes, the receiver may decode them as the wrong script. The reader sees nonsense and trusts the message less. That is a self-inflicted complaint, and it will not show up as a syntax error in the seller's editor.

You can test without a lab. Attach a file whose name uses the script of the list, send it through the platform to yourself, and save the file from a web mailbox. Compare the saved name to the name you uploaded. Match or mismatch. The brochure is not a third outcome.

• The received filename matches the approved name.
• A long name is not chopped to the first piece.
• Replacement characters are treated as a failed test.
• Headers and filenames are checked as two tests.

Should a sender strip a filename because it is not ASCII?

No. Stripping or replacing the name changes the part the reader saves. Ask the platform what it does with a filename it cannot show. A row of question marks is a failed test, not hygiene.

Hygiene is removing addresses that bounce and people who never asked. Renaming a file to survive an old parser is a compatibility hack, and it should be visible. If the only way their system will send the creative is to rename everything to a short English stub, say that in the order. The reader will see the stub. Do not let the pitch promise a name the bytes will not carry.

There is a difference between a filename and the offer. The offer should still be in the letter, in text, even if the file name travels badly. A solo that hides the pitch inside a file, and then mangles the file's name, has failed twice. Put the action on a link in the letter. Let the file be support, with a name you have seen survive.

Does a correct filename place the solo ad?

No. The parameter describes a part. Placement is a separate decision. The buyer's check is whether the received file still has the name you approved, in the script you approved.

A perfect name on unwanted mail is still unwanted mail, now with the right file name, which makes the sender easier to remember. Get the name right so you are not lying by accident. Get the list right so the name is attached to mail someone asked for. The parameter cannot do the second job.

RFC 2231 is a way to tell the truth about a parameter. Use it, or do not attach the file. A filename in another script is still a filename. Sanding it off is how a careful creative becomes a stranger's download.