• winpoint: kill thread/twit filter?

    From August Abolins@2:221/1.59 to Martin Foster on Wed Apr 24 00:27:01 2019
    Hello Martin,

    Does WinPoint have a kill thread or twit filter?


    ../|ug

    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)
  • From Martin Foster@2:240/2188.31 to August Abolins on Wed Apr 24 11:52:00 2019
    Hello August!

    On 24.04.19 at 00:27, August Abolins wrote to Martin Foster:

    Does WinPoint have a kill thread or twit filter?

    Not that I'm aware of.

    Regards,
    Martin

    --- OpenXP 5.0.38
    * Origin: Bitz-Box - Bradford - UK (2:240/2188.31)
  • From Martin Foster@2:310/31.3 to August Abolins on Sun Apr 28 11:40:00 2019
    Hello August!

    On 24.04.19 at 11:52, Martin Foster wrote to August Abolins:

    Does WinPoint have a kill thread or twit filter?

    Not that I'm aware of.

    Correction, yes it does - I wasn't looking hard enough.

    Twit Filter
    -----------
    - Extras -> Options -> Filters Tab
    - At the side of the Import pane, click "Add"
    - In the "Beschreibung"(Description) field, give the filter a name
    - Click the "Kriterien" Tab
    - In the "Absender"(Sender) field, enter the name of the "twit"
    - Click the "Absender" checkbox
    - Click the "Original" Tab
    - Click the "Originalmail Loschen"(Delete original message) checkbox
    - Click the "Ubernehmen" button
    - Click the "OK" button

    NOTE:
    This deletes *ALL* new incoming mail from the "twit".

    If you want to delete mail from the "twit" in a specific area, click
    the "Zielarea" checkbox on the "Kriterien" Tab and then click on the
    pulldown menu and select the specific area.

    After setting this up, I tested the filter by rescanning(for xx days)
    an echo and here's the result:

    ---------- 8< ----------
    28.04.19 10:47:06 Starting Import
    28.04.19 10:47:06 Decompressed bundle c576b700.su0
    28.04.19 10:47:06 1 messages from 95dff735.pkt
    28.04.19 10:47:06 Packet 95dff735.pkt has been moved to backup
    directory
    28.04.19 10:47:06 26 messages from c576b700.pkt
    28.04.19 10:47:06 Packet c576b700.pkt has been moved to backup
    directory
    28.04.19 10:47:06 Area NETMAIL received 1 messages
    28.04.19 10:47:06 Area ****** received 24 messages
    28.04.19 10:47:06 Tossed 25 messages from 2 packets
    28.04.19 10:47:06 Filter "Twit Filter": 2 hits
    28.04.19 10:47:06 2 messages deleted by filters
    ---------- 8< ----------

    Cool eh? :-))

    As for the kill thread filter, it would be set up in a similar manner
    but instead of searching for the "Sender"(Absender) you would need to
    search for the "Subject"(Betreff) on the "Kriterien" Tab. I haven't
    actually tested this but I don't see why it shouldn't work. I'll leave
    that to you but you try it at your own risk ;)

    Regards,
    Martin

    --- OpenXP 5.0.38
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.59 to Martin Foster on Sun Apr 28 14:10:23 2019
    Hello Martin,

    On 28.04.19, you wrote to August Abolins:

    Twit Filter ----------- - Extras -> Options -> Filters Tab - At the side of the Import pane, click "Add" - In the "Beschreibung"(Description)...

    I *knew* those settings looked like they were for some sophisticated processing!

    I will update the PRO CON table.


    If you want to delete mail from the "twit" in a specific area, click
    the "Zielarea" checkbox on the "Kriterien" Tab and then click on the pulldown menu and select the specific area.

    DONE, at least for one name. When does the purge kick in?


    After setting this up, I tested the filter by rescanning(for xx days)
    an echo and here's the result:

    No option to rescan here, but thanks for reporting the test results.


    messages from 2 packets 28.04.19 10:47:06 Filter "Twit Filter": 2 hits 28.04.19 10:47:06 2 messages deleted by filters

    Cool eh? :-))

    Yes.. Too bad we can't twit *while* reading a message. :( It's a lot of steps just to block one name.


    As for the kill thread filter, it would be set up in a similar manner
    but instead of searching for the "Sender"(Absender) you would need to search for the "Subject"(Betreff) on the "Kriterien" Tab. I haven't actually tested this but I don't see why it shouldn't work. I'll leave that to you but you try it at your own risk ;)

    Maybe, someday. I'm afraid to misinterpret the German and select the wrong setting.

    T-bird has this ability down to a simpler art. Press K while reading the thread.


    ../|ug

    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)
  • From Martin Foster@2:310/31.3 to August Abolins on Mon Apr 29 14:40:00 2019
    Hello August!

    On 28.04.19 at 14:10, August Abolins wrote to Martin Foster:

    [snip]
    I will update the PRO CON table.

    If you want to delete mail from the "twit" in a specific area, click
    the "Zielarea" checkbox on the "Kriterien" Tab and then click on the
    pulldown menu and select the specific area.

    DONE, at least for one name. When does the purge kick in?

    The next time the filter detects new incoming messages from the
    "twit". "Mr.Twit" doesn't even make it into the messagebase :-))

    [snip]
    Yes.. Too bad we can't twit *while* reading a message. :(

    Yes, that would be better.

    It's a lot of steps just to block one name.

    Yup.

    As for the kill thread filter, it would be set up in a similar manner
    but instead of searching for the "Sender"(Absender) you would need to
    search for the "Subject"(Betreff) on the "Kriterien" Tab. I haven't
    actually tested this but I don't see why it shouldn't work. I'll leave
    that to you but you try it at your own risk ;)

    Maybe, someday. I'm afraid to misinterpret the German and select the wrong setting.

    Yeah, well, it does look rather powerful/dangerous.

    Regards,
    Martin

    --- OpenXP 5.0.38
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.59 to Martin Foster on Mon Apr 29 18:28:38 2019
    Hello Martin,

    On 29.04.19, you wrote to August Abolins:

    The next time the filter detects new incoming messages from the "twit". "Mr.Twit" doesn't even make it into the messagebase :-))

    It appears to have worked.

    If WinPoint maintained a LOG of the process I'd post it.

    ..A


    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)
  • From Martin Foster@2:310/31.3 to August Abolins on Tue Apr 30 11:50:00 2019
    Hello August!

    On 29.04.19 at 18:28, August Abolins wrote to Martin Foster:

    The next time the filter detects new incoming messages from the
    "twit". "Mr.Twit" doesn't even make it into the messagebase :-))

    It appears to have worked.

    Excellent!

    If WinPoint maintained a LOG of the process I'd post it.

    Look at your Import logs in the "Reports" folder.

    Regards,
    Martin

    --- OpenXP 5.0.38
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.59 to Martin Foster on Tue Apr 30 17:57:00 2019
    Hello Martin,

    On 4/30/2019, you wrote to August Abolins:

    The next time the filter detects new incoming messages from the "twit".
    "Mr.Twit" doesn't even make it into the messagebase :-))

    It appears to have worked.
    If WinPoint maintained a LOG of the process I'd post it.

    Look at your Import logs in the "Reports" folder.

    Oh.. yeah, I forgot about that iddy biddy folder:

    29.04.19 6:01:52 PM Could not move file Z2DAILY.073 to file area Z2DAILY. 29.04.19 6:01:52 PM Could not move file Z2PNT.Z74 to file area Z2PNT.
    29.04.19 6:01:52 PM Could not move file Z2PNT.Z81 to file area Z2PNT.
    29.04.19 6:01:52 PM Could not move file Z2PNT.Z88 to file area Z2PNT.
    29.04.19 6:01:52 PM Starting Import
    29.04.19 6:01:52 PM 1 messages from c6cf900f.pkt
    29.04.19 6:01:52 PM Packet c6cf900f.pkt has been moved to backup directory 29.04.19 6:01:52 PM 3 messages from c7026809.pkt
    29.04.19 6:01:52 PM Packet c7026809.pkt has been moved to backup directory 29.04.19 6:01:52 PM 1 messages from c732280b.pkt
    29.04.19 6:01:52 PM Packet c732280b.pkt has been moved to backup directory 29.04.19 6:01:52 PM 1 messages from c733f711.pkt
    29.04.19 6:01:52 PM Packet c733f711.pkt has been moved to backup directory 29.04.19 6:01:53 PM Area POINTS received 3 messages
    29.04.19 6:01:53 PM Area MEMORIES received 1 messages
    29.04.19 6:01:53 PM Area FIDOTEST received 1 messages
    29.04.19 6:01:53 PM Tossed 5 messages from 4 packets
    29.04.19 6:01:53 PM Filter "del xxxxxxxxxxx": 1 hits
    29.04.19 6:01:53 PM 1 messages deleted by filters

    @ ORIGINAL: WinPoint Integrated Tosser (0:0/0)

    .: Seems to be working. But what is interesting is that the log does not identify the echo of the "hit". The hit is in none of the above listed echos.

    ../|ug


    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)
  • From Martin Foster@2:310/31.3 to August Abolins on Wed May 1 15:18:38 2019
    Hello August!

    On 30/04/2019 17:57:00, August Abolins wrote to Martin Foster:

    [snip]
    If WinPoint maintained a LOG of the process I'd post it.

    Look at your Import logs in the "Reports" folder.

    Oh.. yeah, I forgot about that iddy biddy folder:

    [snip]
    .: Seems to be working.

    OK, so far so good.

    But what is interesting is that the log does not identify the echo of
    the "hit".

    Yeah, that was the case when I did my tests.

    The hit is in none of the above listed echos.

    Dumb question coming up ... how do you know?

    Regards,
    Martin

    --- APoint 1.25
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.59 to Martin Foster on Wed May 1 12:31:03 2019
    Hello Martin,

    On 01.05.19, you wrote to August Abolins:

    But what is interesting is that the log does not identify the echo of
    the "hit".

    Yeah, that was the case when I did my tests.

    Well then, you know what I mean. :) See sample below.


    The hit is in none of the above listed echos.

    Dumb question coming up ... how do you know?

    30.04.19 10:11:19 PM Starting Import
    30.04.19 10:11:19 PM 1 messages from c8f59b0b.pkt
    30.04.19 10:11:19 PM Packet c8f59b0b.pkt has been moved to backup directory 30.04.19 10:11:19 PM Tossed 0 messages from 1 packets
    30.04.19 10:11:19 PM Filter "del xxxxxxxxxx": 1 hits
    30.04.19 10:11:19 PM 1 messages deleted by filters
    + Origin: WinPoint Integrated Tosser (0:0/0)

    I *know* which echo it because it is just one filter for a particular echo for now. BUT, as you can see, the toss does not list it in the logs.


    ../|ug

    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)
  • From August Abolins@2:221/1.59 to Martin Foster on Fri May 3 21:53:08 2019
    Hello Martin,

    On 30.04.19, you wrote to August Abolins:

    The next time the filter detects new incoming messages from the "twit".
    "Mr.Twit" doesn't even make it into the messagebase :-))

    It appears to have worked.

    Excellent!
    Look at your Import logs in the "Reports" folder.

    I am putting WinPoint through its paces (recent abridged and censored results <g>)

    29.04.19 6:01:53 PM Tossed 5 messages from 4 packets
    29.04.19 6:01:53 PM Filter "del xxxxxxxxxx": 1 hits
    29.04.19 6:01:53 PM 1 messages deleted by filters

    4/30/2019 5:58:06 PM Tossed 8 messages from 11 packets
    4/30/2019 5:58:06 PM Filter "del xxxxxxxxxx": 10 hits
    4/30/2019 5:58:06 PM 10 messages deleted by filters

    30.04.19 8:22:05 PM Tossed 4 messages from 4 packets
    30.04.19 8:22:05 PM Filter "del xxxxxxxxxx": 1 hits
    30.04.19 8:22:05 PM 1 messages deleted by filters

    30.04.19 10:11:19 PM Tossed 0 messages from 1 packets
    30.04.19 10:11:19 PM Filter "del xxxxxxxxxx": 1 hits
    30.04.19 10:11:19 PM 1 messages deleted by filters

    01.05.19 12:25:58 PM Tossed 17 messages from 19 packets
    01.05.19 12:25:58 PM Filter "del xxxxxxxxxx": 7 hits
    01.05.19 12:25:58 PM 7 messages deleted by filters

    01.05.19 8:48:46 PM Tossed 20 messages from 9 packets
    01.05.19 8:48:46 PM Filter "del xxxxxxxxxx": 3 hits
    01.05.19 8:48:46 PM 3 messages deleted by filters

    01.05.19 10:31:42 PM Tossed 0 messages from 2 packets
    01.05.19 10:31:42 PM Filter "del xxxxxxxxxx": 5 hits
    01.05.19 10:31:42 PM 5 messages deleted by filters

    03.05.19 7:38:53 PM Tossed 13 messages from 8 packets
    03.05.19 7:38:53 PM Filter "del xxxxxxxxxx": 1 hits
    03.05.19 7:38:53 PM 1 messages deleted by filters

    03.05.19 9:19:00 PM Tossed 5 messages from 5 packets
    03.05.19 9:19:00 PM Filter "del xxxxxxxxxx": 4 hits
    03.05.19 9:19:00 PM 4 messages deleted by filters


    ../|ug

    --- WinPoint Beta 5 (359.1)
    * Origin: Reluctantly Revisiting Fidonet (2:221/1.59)