Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Thhunderbird filter not working.

  • 2 Antworten
  • 1 hat dieses Problem
  • 16 Aufrufe
  • Letzte Antwort von quakerdave

quakerdave
quakerdave
more options

I often receive spoof messages saying that my account has been hacked and which demand bitcoin payments. The subject line is "Message need your participation in processing :You have an outstanding payment." These are "hacked" to appear to come from my own email address so they do not get trapped by ordinary spam engines. I set up a filter for the subject line using all of this subject line to be deleted but that didn't work. I tried it for the subject line simply beginning with "Message" and that didn't work either. Has the rest of the header been hacked in a way that means Thunderbird isn't picking up the expected information and thus not actually working on the alledged subject line. I notice that the bit of the subject line from the ":" onwards isn't actually showing in the header that appears in the email when it is in the "inbox". Curious

Thanks for any help!

I often receive spoof messages saying that my account has been hacked and which demand bitcoin payments. The subject line is "Message need your participation in processing :You have an outstanding payment." These are "hacked" to appear to come from my own email address so they do not get trapped by ordinary spam engines. I set up a filter for the subject line using all of this subject line to be deleted but that didn't work. I tried it for the subject line simply beginning with "Message" and that didn't work either. Has the rest of the header been hacked in a way that means Thunderbird isn't picking up the expected information and thus not actually working on the alledged subject line. I notice that the bit of the subject line from the ":" onwards isn't actually showing in the header that appears in the email when it is in the "inbox". Curious Thanks for any help!

Alle Antworten (2)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Open the Message Source (Ctrl+U) and examine the headers. A filter rule can be tested by entering the same criteria in Classic Search Ctrl+Shift+F. Custom headers such as Reply-to can be added to filters (and search).

quakerdave
quakerdave Fragesteller
more options

Thanks for the reply. Unfortunately, this doesn't work but I have now found what the problem is. The main body of the header is:

From: (my email address is here) To: (my email address is here) Subject: Message need your participation in processing :You have an outstanding payment. Date: 17 Oct 2021 18:12:57 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE X-Spam-Status: No, score=-67.0 X-Spam-Score: -669 X-Spam-Bar: --------------------------------------------------- X-Spam-Flag: NO

I entered this line exactly as it says from the header but the filter using that insertion doesn't work. NB Despite what the header says, the subject line appearing for the email in the inbox only shows the section AFTER the : I think the ":" in the header stops Thunderbird displaying the text BEFORE that point. If I Set a filter for subject line component AFTER the : this DOES work. To sum up - the ":" in the header stops Thunderbird processing the subject line or filtering it properly. This therefore seems to me a bug worthy of addressing.