当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

One of your filters uses a custom header that contains an invalid character ....

  • 1 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: Magini

more options

When I send an email the following error message is displayed:

"One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers."

This is followed by a message saying that the email has been sent and saved despite the error.

The problem happened after transferring to Windows 10 (from Win 7)

I have deleted ALL msgFilterRules.dat files and ALL filters, but the message persist.

Any suggestions on what else to try?

Thanks, Ben

When I send an email the following error message is displayed: "One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers." This is followed by a message saying that the email has been sent and saved despite the error. The problem happened after transferring to Windows 10 (from Win 7) I have deleted ALL msgFilterRules.dat files and ALL filters, but the message persist. Any suggestions on what else to try? Thanks, Ben

選ばれた解決策

Problem solved.

After deleting all imap mail folders/entries the problem went away.

この回答をすべて読む 👍 0

すべての返信 (1)

more options

選ばれた解決策

Problem solved.

After deleting all imap mail folders/entries the problem went away.