If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Filter
Running Seamonkey for newsgroups.
How do I automatically filter crap (i.e. delete) from anon etc ? |
Ads |
#2
|
|||
|
|||
Filter
FreeMan wrote:
Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? Can Seamonkey test on the PATH header? It's a non-overview header and typically most NNTP clients only test on the overview headers. |
#3
|
|||
|
|||
Filter
On Sat, 21 Jul 2018 11:45:52 -0700
FreeMan wrote: Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? Get a good newsreader that will filter on a phrase in the headers, and take the time to learn how to use it. Filter dizum.com and mixmin.net and that will get rid of most of the garbage. https://www.claws-mail.org/downloads...tion=downloads |
#4
|
|||
|
|||
Filter
FreeMan wrote:
Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? I could not find a way to delete such, but I filter on the name and mark it as read. -- G Ross |
#5
|
|||
|
|||
Filter
Subject From Date Size Custom Header There is NO local help for any of this ! Side note: The developers have let us down on HELP and features that were extremely important and provided by 3rd parties that now do not work ! And don't tell me about security. That is a false cognate. In trying to protect use against ourselves is an endless taks so let them screw up and learn. VanguardLH wrote: FreeMan wrote: Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? Can Seamonkey test on the PATH header? It's a non-overview header and typically most NNTP clients only test on the overview headers. |
#6
|
|||
|
|||
Filter
FreeMan,
Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? As you have not mentioned which version you are using the below links might not be exactly what you are looking for, but maybe they gives enough clues to what you want. http://www.dwx.com/support/faqs/seam...onkeyrules.php http://www.freeemailtutorials.com/mo...amJunkMail.cwd I found the above on the first result page googeling for "Seamonkey blocking sender" (without the quotes) Regards, Rudy Wieser |
#7
|
|||
|
|||
Filter
On Sat, 21 Jul 2018 13:58:30 -0500, VanguardLH wrote:
FreeMan wrote: Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? Can Seamonkey test on the PATH header? It's a non-overview header and typically most NNTP clients only test on the overview headers. Seamonkey can test on the PATH header provided the news server supports the XHDR command for non-overview headers such as the PATH header. Some news servers do, some don't. Today, the big "premium" news servers (which cater for binary users) generally do NOT support the XHDR command for non-overview headers. I don't know whether or not the OP's news server freenews.netfront.net (which is based in Hong Kong) supports the XHDR command for non-overview headers. -- Kind regards Ralph |
#8
|
|||
|
|||
Filter
On Sat, 21 Jul 2018 14:39:02 -0700, FreeMan wrote:
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 Latest Seamonkey. Not according to your headers. Latest SeaMonkey is version 2.49.3. Your headers say you are running version 2.48. -- Kind regards Ralph |
#9
|
|||
|
|||
Filter
On Sat, 21 Jul 2018 21:18:16 -0500, VanguardLH wrote:
The valid syntax for a header is: headername:spacevalue To: FreeMan To avoid confusion, the above does NOT apply to SeaMonkey filters. Here is a screen-shot of setting up a kill filter in SeaMonkey to automatically delete posts from anon: https://i.imgur.com/IHbcbAX.png * The header name is in column 1, *without* a colon after it. * The value is in column 3, without a space before it. * Column 2 has the test to perform - in this case, "contains". The headername:spacevalue applies to when you look at the headers in the message source in SeaMonkey View Message Source (Ctrl+U) Some clients will let you specify just the headername, like Path. However, if you're not matching on a standard header (overview or non-overview) then you might have to use regex to match on a substring, like ^headername:\s where ^ anchors to column 1 (start of line), you add the colon character, and specify the intervening space between header name and its value. To: FreeMan To avoid confusion, SeaMonkey itself does not support regex. SeaMonkey also does not need regex to match on a substring. -- Kind regards Ralph |
#10
|
|||
|
|||
Filter
FreeMan wrote on 22/07/2018 4:45 AM:
Running Seamonkey for newsgroups. How do I automatically filter crap (i.e. delete) from anon etc ? Freeman, although there has been some very useful suggestions made here, if you were to set yourself up a news account to news.mozilla.com on Port 119 and then subscribe to the mozilla.support.seamonkey news group, you might also get some informative answers from other SeaMonkey users .... and developers, as well. I believe that groups.google.com also carries the mozilla.support.seamonkey news group. And, as mentioned by others, the latest release version of SeaMonkey is 2.49.3 .... and 2.49.4 could be out any day now. -- Daniel |
#11
|
|||
|
|||
Filter
Ralph Fox wrote:
On Sat, 21 Jul 2018 21:18:16 -0500, VanguardLH wrote: The valid syntax for a header is: headername:spacevalue To: FreeMan To avoid confusion, the above does NOT apply to SeaMonkey filters. Here is a screen-shot of setting up a kill filter in SeaMonkey to automatically delete posts from anon: https://i.imgur.com/IHbcbAX.png * The header name is in column 1, *without* a colon after it. * The value is in column 3, without a space before it. * Column 2 has the test to perform - in this case, "contains". The headername:spacevalue applies to when you look at the headers in the message source in SeaMonkey View Message Source (Ctrl+U) Some clients will let you specify just the headername, like Path. However, if you're not matching on a standard header (overview or non-overview) then you might have to use regex to match on a substring, like ^headername:\s where ^ anchors to column 1 (start of line), you add the colon character, and specify the intervening space between header name and its value. To: FreeMan To avoid confusion, SeaMonkey itself does not support regex. SeaMonkey also does not need regex to match on a substring. The problem then is that, say, filtering on "mixman" will fire on any substring in Path with "mixman" anywhere within it. You want to filter out posts that *originate* from a mixman server, not posts that peered through mixman servers. Someone could submit to, say, individual.net who peers to many NNTP servers who also peer to others. When you retrieve articles from your NNTP server, one of the peering routes might've gone through a mixman server - but it did not *originate* from there! I filter on anon posts submitted to mixman servers, not peered through them and that would result in a lot false positives. Without bounding the "mixman" string by delimiters present in the Path header and without fixing its position at the end of the Path header to identify it as the injection node, the OP with Seamonkey would be filtering out posts that were never submitted to a mixman server but merely peered through one. Pity Seamonkey doesn't support regex. It allows focusing on WHERE within a string that a substring will appear for firing a rule. |
#12
|
|||
|
|||
Filter
On Sun, 22 Jul 2018 22:25:19 -0500, VanguardLH wrote:
Ralph Fox wrote: On Sat, 21 Jul 2018 21:18:16 -0500, VanguardLH wrote: The valid syntax for a header is: headername:spacevalue To: FreeMan To avoid confusion, the above does NOT apply to SeaMonkey filters. Here is a screen-shot of setting up a kill filter in SeaMonkey to automatically delete posts from anon: https://i.imgur.com/IHbcbAX.png * The header name is in column 1, *without* a colon after it. * The value is in column 3, without a space before it. * Column 2 has the test to perform - in this case, "contains". The headername:spacevalue applies to when you look at the headers in the message source in SeaMonkey View Message Source (Ctrl+U) Some clients will let you specify just the headername, like Path. However, if you're not matching on a standard header (overview or non-overview) then you might have to use regex to match on a substring, like ^headername:\s where ^ anchors to column 1 (start of line), you add the colon character, and specify the intervening space between header name and its value. To: FreeMan To avoid confusion, SeaMonkey itself does not support regex. SeaMonkey also does not need regex to match on a substring. The problem then is that, say, filtering on "mixman" will fire on any substring in Path with "mixman" anywhere within it. Not so. In SeaMonkey the match criteria can be something other than "contains". For example the match criteria can be "ends with", as in this screen-shot of a SeaMonkey filter: https://s8.postimg.cc/b1923lwdx/Sea_Monkey-filter-to-match-end-of-_Path-header.png You want to filter out posts that *originate* from a mixman server, not posts that peered through mixman servers. Someone could submit to, say, individual.net who peers to many NNTP servers who also peer to others. When you retrieve articles from your NNTP server, one of the peering routes might've gone through a mixman server - but it did not *originate* from there! I filter on anon posts submitted to mixman servers, not peered through them and that would result in a lot false positives. Without bounding the "mixman" string by delimiters present in the Path header and without fixing its position at the end of the Path header to identify it as the injection node, the OP with Seamonkey would be filtering out posts that were never submitted to a mixman server but merely peered through one. Pity Seamonkey doesn't support regex. It allows focusing on WHERE within a string that a substring will appear for firing a rule. One does not require regex to do this. For example, in SeaMonkey one can create a filter like this: Header: Path Match criteria: ends with Value: !news.mixman.net!.POSTED!not-for-mail -- Kind regards Ralph |
#13
|
|||
|
|||
Filter
Ralph Fox wrote:
On Sun, 22 Jul 2018 22:25:19 -0500, VanguardLH wrote: Ralph Fox wrote: On Sat, 21 Jul 2018 21:18:16 -0500, VanguardLH wrote: The valid syntax for a header is: headername:spacevalue To: FreeMan To avoid confusion, the above does NOT apply to SeaMonkey filters. Here is a screen-shot of setting up a kill filter in SeaMonkey to automatically delete posts from anon: https://i.imgur.com/IHbcbAX.png * The header name is in column 1, *without* a colon after it. * The value is in column 3, without a space before it. * Column 2 has the test to perform - in this case, "contains". The headername:spacevalue applies to when you look at the headers in the message source in SeaMonkey View Message Source (Ctrl+U) Some clients will let you specify just the headername, like Path. However, if you're not matching on a standard header (overview or non-overview) then you might have to use regex to match on a substring, like ^headername:\s where ^ anchors to column 1 (start of line), you add the colon character, and specify the intervening space between header name and its value. To: FreeMan To avoid confusion, SeaMonkey itself does not support regex. SeaMonkey also does not need regex to match on a substring. The problem then is that, say, filtering on "mixman" will fire on any substring in Path with "mixman" anywhere within it. Not so. In SeaMonkey the match criteria can be something other than "contains". For example the match criteria can be "ends with", as in this screen-shot of a SeaMonkey filter: https://s8.postimg.cc/b1923lwdx/Sea_Monkey-filter-to-match-end-of-_Path-header.png You want to filter out posts that *originate* from a mixman server, not posts that peered through mixman servers. Someone could submit to, say, individual.net who peers to many NNTP servers who also peer to others. When you retrieve articles from your NNTP server, one of the peering routes might've gone through a mixman server - but it did not *originate* from there! I filter on anon posts submitted to mixman servers, not peered through them and that would result in a lot false positives. Without bounding the "mixman" string by delimiters present in the Path header and without fixing its position at the end of the Path header to identify it as the injection node, the OP with Seamonkey would be filtering out posts that were never submitted to a mixman server but merely peered through one. Pity Seamonkey doesn't support regex. It allows focusing on WHERE within a string that a substring will appear for firing a rule. One does not require regex to do this. For example, in SeaMonkey one can create a filter like this: Header: Path Match criteria: ends with Value: !news.mixman.net!.POSTED!not-for-mail That works to test if mixmin is the injection node, not a peer. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|