Does WinPoint have a kill thread or twit filter?
Does WinPoint have a kill thread or twit filter?
Not that I'm aware of.
Twit Filter ----------- - Extras -> Options -> Filters Tab - At the side of the Import pane, click "Add" - In the "Beschreibung"(Description)...
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:
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? :-))
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 ;)
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?
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.
The next time the filter detects new incoming messages from the "twit". "Mr.Twit" doesn't even make it into the messagebase :-))
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.
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.
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:
.: 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.
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?
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.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 513 |
Nodes: | 10 (1 / 9) |
Uptime: | 01:27:56 |
Calls: | 8,292 |
Calls today: | 5 |
Files: | 15,520 |
Messages: | 928,951 |