1245157 - "After junk" filter fails to find "://t.co/" in body of message outside URL on Linux (comment #6) - not finding inside URL is covered by bug 1211128

Status: NEW

(Thunderbird :: Filters, defect)

Description

[u328884]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.7) Gecko/20150929 Firefox/31.9 PaleMoon/25.7.2
Build ID: 20150929234510

Steps to reproduce:

Body
Contains
://t.co/

Move message to

All other settings are default.

This doesn't work when fetching mail or manually running filter. It used to work (a few days ago). I did nothing to stop it from working.


Actual results:

Filter does not filter.


Expected results:

message should be moved by the filter.

Comment 1

[Jorg K (CEST = GMT+2)]

(Thank goodness) I cannot reproduce this in TB 38 or TB 45 (beta) on Windows.
I don't understand what the reporter wrote:
  It used to work (a few days ago). I did nothing to stop it from working.
Maybe there was an update?

Anyway, I created a rule that says
"Body" "contains" "Voici"
"Move Message to" "some folder"
and that works when run manually and on incoming POP mail.

I've also tried with the string "://t.co/" (without the quotes) and that works, too.

Comment 2

[u328884]

Jorg K wrote: "(Thank goodness) I cannot reproduce this in TB 38 or TB 45 (beta) on Windows."

I'm running TBird version 38.5.1 in 64-bit Linux Mint version 17.2. I'm not running TBird in Windows. Perhaps your test experience in Windows isn't relevant.

Jorg K wrote: "I don't understand what the reporter wrote:
  It used to work (a few days ago). I did nothing to stop it from working."

The filter spontaneously stopped functioning. I did not disable it or move it down in the filter chain or alter it.

Jorg K wrote: "Maybe there was an update?"

No.

Jorg K wrote: "Anyway, I created a rule that says
"Body" "contains" "Voici"
"Move Message to" "some folder"
and that works when run manually and on incoming POP mail."

Not relevant because it's not the filter string for the filter having difficulty.

Jorg K wrote: "I've also tried with the string "://t.co/" (without the quotes) and that works, too."

Perhaps there's a difference between TBird for Windows and TBird for Linux?

I have no abilty to run tests. I have no tools. I cannot post to the TBird support list because troubleshooting is beyond its scope and the natives there resent such posts.

How can I move this along and upgrade the problem to a level above UNCONFIRMED?

Comment 3

[Jorg K (CEST = GMT+2)]

(In reply to Mark Filipak from comment #2)
> I'm running TBird version 38.5.1 in 64-bit Linux Mint version 17.2. I'm not
> running TBird in Windows. Perhaps your test experience in Windows isn't
> relevant.
I'll try it with your particular string "://t.co/" on a 64-bit Linux Mint 17.1/17.2(?) box, OK?

> Perhaps there's a difference between TBird for Windows and TBird for Linux?
There shouldn't be.

> How can I move this along and upgrade the problem to a level above
> UNCONFIRMED?
If I can confirm it, I will move it along. We have active developers for Linux who can look at it afterwards.

Comment 4

[Wayne Mery (:wsmwk)]

other recent filter body bug reports:
bug 1230815
bug 1245532

Comment 5

[Jorg K (CEST = GMT+2)]

And bug 1244094.

Comment 6

[Jorg K (CEST = GMT+2)]

OK, here are my findings:

I sent a message containing "://t.co/" (without the quotes). I received the message on a Linux machine with Mint 17.x 64bit installed. TB version on Linux: 38.5.1. There was a rule configured to move a message containing the said string in the body to the trash.

If the filter is configured to run before junk classification, the message does get filtered and moved.
If the filter is configured to run after  junk classification, the message is NOT filtered. However, in this case, running the filter manually, the message gets moved, which is NOT what the reporter said in comment #0.

Mark: How is you filter configured? To run before or after the junk classification? Have you tried the "before" setting?

This cannot be reproduced on Windows, neither with TB 38.5.1 nor TB 45 (beta). On Windows in all versions the message always gets moved.

So now it's over to the Linux people. Aceman, can you please try this on Linux on a developer version.

Also note Mark's other bug on filters, bug 1239359.

Comment 7

[u328884]

Thank you, Jorg,

(In reply to Jorg K (GMT+1) from comment #6)
-snip-
> Mark: How is you filter configured? To run before or after the junk
> classification? Have you tried the "before" setting?

I don't do any junk filtering. Specifically,
- for '<account-name>' | 'Junk Settings' for each account, all check boxes are unchecked,
- for 'Thunderbird Preferences' | 'Security' tab | 'Junk' tab, all check boxes are unchecked,
- each Filter Rule has the following settings: 'Apply filter when:' '[X] Manually Run', and '[X] Getting New Mail: [_Filter_before_Junk_Classification_]'.

The filter chain is (top to bottom):

Filter name: [_Trash________________]
Apply filter when:
[X] Manually Run
[X] Getting New Mail: [_Filter_before_Junk_Classification_]
[_] Archiving
[_] After Sending
(o) Match all of the following ( ) Match any of the following ( ) Match all messages
[_Body______________________][_contains_______][_://t.co/________]
Perform these actions:
[_Move_Message_to_______][_Trash_on_maildir_______]

Filter name: [_maildir_blacklist____]
Apply filter when:
[X] Manually Run
[X] Getting New Mail: [_Filter_before_Junk_Classification_]
[_] Archiving
[_] After Sending
( ) Match all of the following (o) Match any of the following ( ) Match all messages
[_From______________________][_ends_with______][_.xyz____________]
[_From______________________][_ends_with______][_.date___________]
[_From______________________][_ends_with______][_.club___________]
[_Content-Transfer_Encoding_][_is_____________][_base64__________]
Perform these actions:
[_Move_Message_to_______][_suspicious_on_maildir__]

Filter name: [_maildir_whitelist____]
Apply filter when:
[X] Manually Run
[X] Getting New Mail: [_Filter_before_Junk_Classification_]
[_] Archiving
[_] After Sending
( ) Match all of the following (o) Match any of the following ( ) Match all messages
[_From______________________][_ends_with______][_.com____________]
[_From______________________][_ends_with______][_.edu____________]
[_From______________________][_ends_with______][_.gov____________]
[_From______________________][_ends_with______][_.net____________]
[_From______________________][_ends_with______][_.org____________]
Perform these actions:
[_Move_Message_to_______][_linux_on_maildir_______]

Filter name: [_maildir_whitelist____]
Apply filter when:
[X] Manually Run
[X] Getting New Mail: [_Filter_before_Junk_Classification_]
[_] Archiving
[_] After Sending
( ) Match all of the following ( ) Match any of the following (o) Match all messages
Perform these actions:
[_Move_Message_to_______][_suspicious_on_maildir__]

The subject email contains:

...
From: "Education Services" <[e-mail]>
...
<a href="https://t.co/gxkby3Havb"><img src="https://pbs.twimg.com/media/Caw5X9nVIAAqvDH.jpg"></a><br>
...

So you see that the 1st filter should send it to 'Trash', but it doesn't. The 2nd filter ('maildir blacklist') does send it to 'suspicious'.

I tested with all plugins disabled (so-called 'safe mode').
(Note: 'account90', mail.x, is the account named 'maildir'. It is a maildir. In the maildir, there is a folder for each of the other accounts (which are the existing mboxes). Filters are supposed to do the moving, but the body filter is failing.)


  Application Basics

    Name: Thunderbird
    Version: 38.5.1
    User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
    Profile Directory: Open Directory

              (Network drive)
    Application Build ID: 20160106101225
    Enabled Plugins: about:plugins
    Build Configuration: about:buildconfig
    Memory Use: about:memory

  Mail and News Accounts
    account1:
      INCOMING: account1, , (none) Local Folders, plain, passwordCleartext

    account4:
      INCOMING: account4, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account7:
      INCOMING: account7, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account11:
      INCOMING: account11, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account12:
      INCOMING: account12, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account14:
      INCOMING: account14, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account16:
      INCOMING: account16, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account18:
      INCOMING: account18, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account20:
      INCOMING: account20, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account22:
      INCOMING: account22, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account23:
      INCOMING: account23, , (pop3) pop.googlemail.com:110, alwaysSTARTTLS, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account24:
      INCOMING: account24, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account25:
      INCOMING: account25, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account26:
      INCOMING: account26, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account28:
      INCOMING: account28, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account29:
      INCOMING: account29, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account32:
      INCOMING: account32, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account37:
      INCOMING: account37, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account38:
      INCOMING: account38, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account39:
      INCOMING: account39, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account42:
      INCOMING: account42, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account44:
      INCOMING: account44, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account45:
      INCOMING: account45, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account46:
      INCOMING: account46, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account47:
      INCOMING: account47, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account51:
      INCOMING: account51, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account57:
      INCOMING: account57, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account58:
      INCOMING: account58, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account59:
      INCOMING: account59, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account60:
      INCOMING: account60, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account71:
      INCOMING: account71, , (pop3) pop3.inbox.com:995, SSL, passwordEncrypted
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account72:
      INCOMING: account72, , (pop3) my.inbox.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account73:
      INCOMING: account73, , (pop3) pop-server.neo.rr.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account74:
      INCOMING: account74, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account76:
      INCOMING: account76, , (pop3) pop.googlemail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account83:
      INCOMING: account83, , (pop3) pop.gmail.com:995, SSL, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

    account90:
      INCOMING: account90, , (pop3) mail.x:110, alwaysSTARTTLS, passwordCleartext
      OUTGOING: mail.twc.com:587, alwaysSTARTTLS, passwordCleartext, true

  Crash Reports

  Extensions
    CompactHeader, 2.1.0, false, {58D4392A-842E-11DE-B51A-C7B855D89593}
    ImportExportTools, 2.8.0.4, false, {3ed8cc52-86fc-4613-9026-c1ef969da4c3}
    Manually sort folders, 1.1, false, [e-mail]
    Messaging Menu and Unity Launcher integration, 1.3.1, false, [e-mail]
    QuickFolders, 4.3, false, [e-mail]
    Show Address Only, 0.1.9, false, [e-mail]

  Important Modified Preferences

    Name: Value

      accessibility.typeaheadfind.flashBar: 0
      browser.cache.disk.capacity: 358400
      browser.cache.disk.smart_size_cached_value: 358400
      browser.cache.disk.smart_size.first_run: false
      browser.cache.disk.smart_size.use_old_max: false
      browser.display.use_document_fonts: 0
      browser.fixup.alternate.enabled: false
      extensions.lastAppVersion: 38.5.1
      font.internaluseonly.changed: false
      font.language.group: x-western
      font.name.monospace.x-western: Lucida Console
      font.name.sans-serif.x-western: Lucida Console
      font.name.serif.x-western: Lucida Console
      font.size.fixed.x-western: 11
      font.size.variable.x-unicode: 10
      font.size.variable.x-western: 11
      gfx.blacklist.suggested-driver-version: 257.21
      javascript.enabled: false
      layers.acceleration.disabled: false
      mail.openMessageBehavior.version: 1
      mailnews.database.global.datastore.id: 027a265e-c015-4a19-a1c4-0d404ef3e13
      mailnews.database.global.views.conversation.columns: {"threadCol":{"visible":true,"ordinal":"1"},"flaggedCol":{"visible":true,"ordinal":"3"},"attachmentCol":{"visible":false…
      mailnews.database.global.views.global.columns: {"threadCol":{"visible":true,"ordinal":"1"},"flaggedCol":{"visible":true,"ordinal":"3"},"attachmentCol":{"visible":false…
      network.cookie.cookieBehavior: 2
      network.cookie.prefsMigrated: true
      network.predictor.cleaned-up: true
      network.protocol-handler.app.http: /usr/bin/palemoon
      network.protocol-handler.warn-external.http: true
      network.protocol-handler.warn-external.https: true
      places.database.lastMaintenance: 1373926605
      places.history.enabled: false
      places.history.expiration.transient_current_max_pages: 53637
      places.history.expiration.transient_optimal_database_size: 85818408
      plugin.disable_full_page_plugin_for_types: application/pdf
      plugin.importedState: true
      plugin.state.flash: 0
      plugin.state.npctrl: 0
      plugin.state.npdrmv: 0
      plugin.state.npdsplay: 0
      plugin.state.npgoogleupdate: 0
      plugin.state.npwmsdrm: 0
      print.printer_CutePDF_Writer.print_bgcolor: false
      print.printer_CutePDF_Writer.print_bgimages: false
      print.printer_CutePDF_Writer.print_colorspace:
      print.printer_CutePDF_Writer.print_command:
      print.printer_CutePDF_Writer.print_downloadfonts: false
      print.printer_CutePDF_Writer.print_duplex: 0
      print.printer_CutePDF_Writer.print_edge_bottom: 0
      print.printer_CutePDF_Writer.print_edge_left: 0
      print.printer_CutePDF_Writer.print_edge_right: 0
      print.printer_CutePDF_Writer.print_edge_top: 0
      print.printer_CutePDF_Writer.print_evenpages: true
      print.printer_CutePDF_Writer.print_footercenter:
      print.printer_CutePDF_Writer.print_footerleft:
      print.printer_CutePDF_Writer.print_footerright:
      print.printer_CutePDF_Writer.print_headercenter:
      print.printer_CutePDF_Writer.print_headerleft:
      print.printer_CutePDF_Writer.print_headerright:
      print.printer_CutePDF_Writer.print_in_color: true
      print.printer_CutePDF_Writer.print_margin_bottom: 0.100000001490116
      print.printer_CutePDF_Writer.print_margin_left: 0.100000001490116
      print.printer_CutePDF_Writer.print_margin_right: 0.100000001490116
      print.printer_CutePDF_Writer.print_margin_top: 0.100000001490116
      print.printer_CutePDF_Writer.print_oddpages: true
      print.printer_CutePDF_Writer.print_orientation: 0
      print.printer_CutePDF_Writer.print_page_delay: 50
      print.printer_CutePDF_Writer.print_paper_data: 1
      print.printer_CutePDF_Writer.print_paper_height: 11.00
      print.printer_CutePDF_Writer.print_paper_name:
      print.printer_CutePDF_Writer.print_paper_size_type: 0
      print.printer_CutePDF_Writer.print_paper_size_unit: 0
      print.printer_CutePDF_Writer.print_paper_width: 8.50
      print.printer_CutePDF_Writer.print_plex_name:
      print.printer_CutePDF_Writer.print_resolution: 0
      print.printer_CutePDF_Writer.print_resolution_name:
      print.printer_CutePDF_Writer.print_reversed: false
      print.printer_CutePDF_Writer.print_scaling: 1.20
      print.printer_CutePDF_Writer.print_shrink_to_fit: true
      print.printer_CutePDF_Writer.print_to_file: false
      print.printer_CutePDF_Writer.print_unwriteable_margin_bottom: 0
      print.printer_CutePDF_Writer.print_unwriteable_margin_left: 0
      print.printer_CutePDF_Writer.print_unwriteable_margin_right: 0
      print.printer_CutePDF_Writer.print_unwriteable_margin_top: 0
      print.printer_Generic_/_Text_Only.print_bgcolor: false
      print.printer_Generic_/_Text_Only.print_bgimages: false
      print.printer_Generic_/_Text_Only.print_evenpages: true
      print.printer_Generic_/_Text_Only.print_footercenter:
      print.printer_Generic_/_Text_Only.print_footerleft:
      print.printer_Generic_/_Text_Only.print_footerright:
      print.printer_Generic_/_Text_Only.print_headercenter:
      print.printer_Generic_/_Text_Only.print_headerleft:
      print.printer_Generic_/_Text_Only.print_headerright: &U
      print.printer_Generic_/_Text_Only.print_in_color: true
      print.printer_Generic_/_Text_Only.print_margin_bottom: 0.100000001490116
      print.printer_Generic_/_Text_Only.print_margin_left: 0.100000001490116
      print.printer_Generic_/_Text_Only.print_margin_right: 0.100000001490116
      print.printer_Generic_/_Text_Only.print_margin_top: 0.100000001490116
      print.printer_Generic_/_Text_Only.print_oddpages: true
      print.printer_Generic_/_Text_Only.print_orientation: 0
      print.printer_Generic_/_Text_Only.print_reversed: false
      print.printer_Generic_/_Text_Only.print_scaling: 1.00
      print.printer_Generic_/_Text_Only.print_shrink_to_fit: false
      print.printer_Lexmark_2600_Series.print_bgcolor: false
      print.printer_Lexmark_2600_Series.print_bgimages: false
      print.printer_Lexmark_2600_Series.print_colorspace:
      print.printer_Lexmark_2600_Series.print_command:
      print.printer_Lexmark_2600_Series.print_downloadfonts: false
      print.printer_Lexmark_2600_Series.print_duplex: 0
      print.printer_Lexmark_2600_Series.print_edge_bottom: 0
      print.printer_Lexmark_2600_Series.print_edge_left: 0
      print.printer_Lexmark_2600_Series.print_edge_right: 0
      print.printer_Lexmark_2600_Series.print_edge_top: 0
      print.printer_Lexmark_2600_Series.print_evenpages: true
      print.printer_Lexmark_2600_Series.print_footercenter:
      print.printer_Lexmark_2600_Series.print_footerleft:
      print.printer_Lexmark_2600_Series.print_footerright:
      print.printer_Lexmark_2600_Series.print_headercenter:
      print.printer_Lexmark_2600_Series.print_headerleft:
      print.printer_Lexmark_2600_Series.print_headerright:
      print.printer_Lexmark_2600_Series.print_in_color: true
      print.printer_Lexmark_2600_Series.print_margin_bottom: 0.100000001490116
      print.printer_Lexmark_2600_Series.print_margin_left: 0.100000001490116
      print.printer_Lexmark_2600_Series.print_margin_right: 0.100000001490116
      print.printer_Lexmark_2600_Series.print_margin_top: 0.100000001490116
      print.printer_Lexmark_2600_Series.print_oddpages: true
      print.printer_Lexmark_2600_Series.print_orientation: 0
      print.printer_Lexmark_2600_Series.print_page_delay: 50
      print.printer_Lexmark_2600_Series.print_paper_data: 1
      print.printer_Lexmark_2600_Series.print_paper_height: 11.00
      print.printer_Lexmark_2600_Series.print_paper_name:
      print.printer_Lexmark_2600_Series.print_paper_size_type: 0
      print.printer_Lexmark_2600_Series.print_paper_size_unit: 0
      print.printer_Lexmark_2600_Series.print_paper_width: 8.50
      print.printer_Lexmark_2600_Series.print_plex_name:
      print.printer_Lexmark_2600_Series.print_resolution: 0
      print.printer_Lexmark_2600_Series.print_resolution_name:
      print.printer_Lexmark_2600_Series.print_reversed: false
      print.printer_Lexmark_2600_Series.print_scaling: 1.50
      print.printer_Lexmark_2600_Series.print_shrink_to_fit: false
      print.printer_Lexmark_2600_Series.print_to_file: false
      print.printer_Lexmark_2600_Series.print_unwriteable_margin_bottom: 0
      print.printer_Lexmark_2600_Series.print_unwriteable_margin_left: 0
      print.printer_Lexmark_2600_Series.print_unwriteable_margin_right: 0
      print.printer_Lexmark_2600_Series.print_unwriteable_margin_top: 0
      privacy.donottrackheader.enabled: true

  Graphics

      Adapter Description: Humper -- Chromium
      Vendor ID: Humper
      Device ID: Chromium
      Driver Version: 2.1 Chromium 1.9
      WebGL Renderer: Blocked for your graphics card because of unresolved driver issues.
      GPU Accelerated Windows: 0. Blocked for your graphics card because of unresolved driver issues.

      AzureCanvasBackend: cairo
      AzureSkiaAccelerated: 0
      AzureFallbackCanvasBackend: none
      AzureContentBackend: cairo

  JavaScript

  Incremental GC: 1

  Accessibility

    Activated: 0
    Prevent Accessibility: 0

  Library Versions

      Expected minimum version
      Version in use

      NSPR
      4.10.10
      4.10.10

      NSS
      3.19.2.1 Basic ECC
      3.19.2.1 Basic ECC

      NSS Util
      3.19.2.1
      3.19.2.1

      NSS SSL
      3.19.2.1 Basic ECC
      3.19.2.1 Basic ECC

      NSS S/MIME
      3.19.2.1 Basic ECC
      3.19.2.1 Basic ECC

Comment 8

[u328884]

Oops!
That 4th filter is not
'Filter name: [_maildir_whitelist____]'.
It is
'Filter name: [_maildir_suspicious___]'.
Sorry.

Comment 9

[Jorg K (CEST = GMT+2)]

(In reply to Mark Filipak from comment #7)
> ...
> From: "Education Services" <[e-mail]>
> ...
> <a href="https://t.co/gxkby3Havb"><img
> src="https://pbs.twimg.com/media/Caw5X9nVIAAqvDH.jpg"></a><br>
> ...

Oh, the text to be filtered is in a link specification. We noticed in bug 1230815 that the filtering doesn't work if the link is all in one line, but it does work when the link is broken, see bug 1230815 comment #1.

I'm still wondering whether we should filter inside links or only in visible text.

The puzzling observation I made today on Linux that your string sometimes doesn't get filtered when included in the body of an e-mail but not in a link, is also something to look at. Looks like filtering is a little flaky ;-(

Anyway, if you problem is like bug 1230815, then messages received with
<a href="https://t.co/gxkby3Havb"> (in one line) would not be filtered, messages with
<a
href="https://t.co/gxkby3Havb"> (broken in two lines) would be filtered. Given that you can't influence the content that the (potential) spammer sends, the filter works sometimes, but not others.

Comment 10

[Jorg K (CEST = GMT+2)]

The main part of the problem is now covered in bug 1211128.

I won't resolve the bug as a duplicate since the "://t.co/" is also not found in the body of a message outside a URL on Linux, see comment #6.

Comment 11

[u328884]

Thank you, Jorg,

If I wanted to pursue this further, into fixing the filter code for example, what would I do? I imagine the source is C (or is Java). No problem.

Let me explain something. I'm a hardware engineer. But I program in many languages, from the hardware, sequential or unclocked, to very close to the hardware (e.g.: 80x52 assembly language) to very far from the hardware (e.g., scripts like Perl). I designed systems, boards, and chips in Silicon Valley for 25 years -- I'm retired now. I had lots of programmer friends. They would give me their code and I would break it. I could break code that no one else could break. I would fiddle with their well-tested UI for a few minutes and break the application. Also, I could find bugs no one else could find. I could find the hard to replicate bugs. I could find the bugs that no one has discovered yet. It has to do with the way I examine code and especially with the particular way that I beautify it. It exposes logical flaws to my eyes. My programmer friends would scoff at that, but I apparently see things in ways they can't. Maybe it has to do with my hardware education. Hardware is like multithreaded code that forks in ways that seem strange to people who know only sequential logic, and that executes asynchronously and almost instantly. Being a hardware designer has built something into my brain. I can't explain it any better than that. So even though I don't have any debugging tools, I can still help. I just don't know how to start because I've never worked as a coder and I don't know coder-lingo.

Comment 12

[Jorg K (CEST = GMT+2)]

(In reply to Mark Filipak from comment #11)
> If I wanted to pursue this further, into fixing the filter code for example,
> what would I do? I imagine the source is C (or is Java). No problem.

Oh, if you want to become a contributor, that's a steep learning curve ;-) But maybe you can start looking at the code. TB is written in C++ and JavaScript.

You can browse the code here:
https://dxr.mozilla.org/comm-central/source/

You might want to start by typing "filter body" into the search box.
Looks like some filtering is done here:
https://dxr.mozilla.org/comm-central/source/mailnews/base/search/src/nsMsgFilter.cpp
and here:
https://dxr.mozilla.org/comm-central/source/mailnews/base/search/src/nsMsgFilterService.cpp

I'm not familiar with filtering, I work mainly on message compose.

BTW, when searching with DXR, you want to ignore all entries that start with mozilla/. TB is basically built on top of Mozilla core code which is used for Firefox. The Mozilla core code is in mozilla/.

Let me know whether you have questions. Perhaps you can work out where the body is filtered and we can see what happens to text in links. Also see bug 1211128.

It you want to build TB on your machine, see here:
https://developer.mozilla.org/en-US/docs/Simple_Thunderbird_build

There is also an IRC channel if you have further questions. (I'm not usually on IRC though.)

Comment 13

[u328884]

Who is the manager? How do I contact the manager?

Comment 14

[Jorg K (CEST = GMT+2)]

(In reply to Mark Filipak from comment #13)
> Who is the manager? How do I contact the manager?
Well, since Mozilla withdrew paid staff from TB, TB is supported by a self-governed group of distributors. There is a Thunderbird Council (https://wiki.mozilla.org/Modules/Thunderbird) and the chairman of this council is Kent James. Also see: https://blog.mozilla.org/thunderbird/2014/11/thunderbird-reorganizes-at-2014-toronto-summit/. You can ask for information from him by clicking the "Need more information" box below and entering :rkent into field. Or you can e-mail him directly.

However, Kent is a busy man, and he is not the manager as we know the term from private companies, since there is no manager in a community project. Every developer basically does what they want. Kent usually describes himself as "herder of cats".

There is no way to exert pressure to get a bug fixed, I tried myself and failed, so I joined the project and started fixing bugs myself. ;-)

Comment 15

[Wayne Mery (:wsmwk)]

(In reply to Mark Filipak from comment #13)
> Who is the manager? How do I contact the manager?

As we say our offices, "What is your real question?".

Note, developers irc hangout is http://tinyurl.com/tbmaildev

Comment 16

[Kent James (:rkent)]

Forgetting my role as Chair, technically I was the implementer of the "after junk" filters, so I would probably review any fixes (though it was a long time ago, when I was fairly new in the project).

In that and in the related work using custom search terms, there was an explicit attempt to support delaying the filter search until after the IMAP process downloaded the message body, so that the body could be used in search. But that never worked properly in custom search, and perhaps this issue is related.

But this is not a trivial problem. Filter search is by design a sync process, but message download is inherently async. Also body search is sort of quasi-async in a kludgy way. You may find that there is no straightforward solution that does not involve refactoring the search to be async.

To get started, first you need to compile the code, which is not a trivial process. Then write an XPCSHELL test that demonstrates your problem. Then debug that test using a C++ debugger.

If the issue is simply that you don't like the HTML stripping, that could be fairly straightforward to investigate. See http://mxr.mozilla.org/comm-central/source/mailnews/base/search/src/nsMsgBodyHandler.cpp

Comment 17

[Jorg K (CEST = GMT+2)]

This bug started generic as "string not found by filter in body". In the end, 95% of the initial problem, that is, not finding strings which are part of links, has been shifted to bug 1211128.

Comment 18

[Patrick Matias]

Attachment: same problem

Thanks from ennisphana1989.