Does anyone here have an idea of how I could implement some kind of
killfile when reading news in pine?
On Wed, 21 Feb 2024, D wrote:
Does anyone here have an idea of how I could implement some kind of
killfile when reading news in pine?
You could implement filters in Alpine. Press M S R F to start setting up one.
Great! Thank you very much for the pointer in the right direction Eduardo! =)
I'll have a look there.
Best regards,
Daniel
On Wed, 21 Feb 2024, Eduardo Chappa wrote:
On Wed, 21 Feb 2024, D wrote:
Does anyone here have an idea of how I could implement some kind of
killfile when reading news in pine?
You could implement filters in Alpine. Press M S R F to start setting up
one.
Just to follow up for the benefit of others who might have the same question.
I had a look as per Eduardos advice, and I found the following:
External Categorizer Commands =
Which allows you to call a command to a program that filters for you. So instead of having one rule per user I want to avoid, I can just write a script, and add all the usernames I want to avoid to that killfile, and if I understand things correctly, the rule with an External Categorizer Command will run my script and return if there is a match, and then I just select "delete message" or something similar.
Best regards,
Daniel
On Thu, 22 Feb 2024, D wrote:
Great! Thank you very much for the pointer in the right direction Eduardo! >> =) I'll have a look there.
Best regards,
Daniel
On Wed, 21 Feb 2024, Eduardo Chappa wrote:
On Wed, 21 Feb 2024, D wrote:
Does anyone here have an idea of how I could implement some kind of
killfile when reading news in pine?
You could implement filters in Alpine. Press M S R F to start setting up >>> one.
Good evening, another update on the killfile problem.
Regardless of if I try a filter or use an external categorizer, it is painfully slow on active groups.
On Thu, 22 Feb 2024, D wrote:
Good evening, another update on the killfile problem.
Regardless of if I try a filter or use an external categorizer, it is
painfully slow on active groups.
My advice is that you do not use the categorizer command. That is intended to
be used for the full message. Instead just set up the headers part, which will help.
Once you have set up the headers section (and nothing more) quit Alpine and restart it with the command
alpine -d imap=4,timestamp
repeat the issue, quit Alpine and read the file ~/.pine-debug1. Look for big gaps in the timestamp. What is alpine doing? What is the server doing? If you
do not understand what you are reading, please post what you can here and we will help you understand it. It would be useful to see the capabilities of your server.
Having said all of this, do not expect miracles. Alpine was designed to do operations over IMAP, not NNTP, and doing filtering over a connected line is slow even over IMAP.
For the moment though, it seems like the "winner" is to download all messages, and _then_ use a search filter to delete unwanted messages.
Am I right in suspecting that a search filter is executed on the
downloaded messages only and that it therefore seems to run at lightning speed compared with a filter rule that runs _over_ the nntp connection?
On Sat, 24 Feb 2024, D wrote:
For the moment though, it seems like the "winner" is to download all
messages, and _then_ use a search filter to delete unwanted messages.
Yes, I agree. The speed of Alpine will be determined by several factors. In your case it will also depend on the capabilities of the server. Local access
will make Alpine much faster. That might be the best solution for you.
Am I right in suspecting that a search filter is executed on the downloaded >> messages only and that it therefore seems to run at lightning speed
compared with a filter rule that runs _over_ the nntp connection?
If Alpine has to download the message to process it, then it will do that, and that will seem very slow. However, once the message has been downloaded, it will be cached and any further access will be from cached memory, and it will be very fast.
Great, thank you for the clarification Eduardo! =)
Another question... do you think it would be possible to script some
kind of "nntp sync" that delivers news messages into Maildir folders and have alpine interact with those as news messages?
My idea here is that it would be great to be able to download the news messages locally, interact with them locally, and then once done, send
them to the newsgroup.
On 2024-02-26 11:32, D wrote:...
Great, thank you for the clarification Eduardo! =)
Another question... do you think it would be possible to script some kind >> of "nntp sync" that delivers news messages into Maildir folders and have
alpine interact with those as news messages?
My idea here is that it would be great to be able to download the news
messages locally, interact with them locally, and then once done, send them >> to the newsgroup.
Not with Alpine. If you are on Linux, use "leafnode" instead.
Telcontar:~ # rpm -q leafnode
Note: it has filters and can do a kill file action.
On Mon, 26 Feb 2024, Carlos E.R. wrote:
On 2024-02-26 11:32, D wrote:...
Great, thank you for the clarification Eduardo! =)
Another question... do you think it would be possible to script some kind >>> of "nntp sync" that delivers news messages into Maildir folders and have >>> alpine interact with those as news messages?
My idea here is that it would be great to be able to download the news
messages locally, interact with them locally, and then once done, send
them to the newsgroup.
Not with Alpine. If you are on Linux, use "leafnode" instead.
Telcontar:~ # rpm -q leafnode
Note: it has filters and can do a kill file action.
Oh, that actually sounds _exactly_ like what I'm looking for, and I
could just point alpine to the local nntp, and use it as a local cache
(if it works like I think it does). Brillant! Thank you very much! =)
Best regards, Daniel
On Mon, 26 Feb 2024, D wrote:
On Mon, 26 Feb 2024, Carlos E.R. wrote:
On 2024-02-26 11:32, D wrote:...
Great, thank you for the clarification Eduardo! =)
Another question... do you think it would be possible to script some
kind of "nntp sync" that delivers news messages into Maildir folders
and have alpine interact with those as news messages?
My idea here is that it would be great to be able to download the
news messages locally, interact with them locally, and then once
done, send them to the newsgroup.
Not with Alpine. If you are on Linux, use "leafnode" instead.
Telcontar:~ # rpm -q leafnode
Note: it has filters and can do a kill file action.
Oh, that actually sounds _exactly_ like what I'm looking for, and I
could just point alpine to the local nntp, and use it as a local cache
(if it works like I think it does). Brillant! Thank you very much! =)
And to continue my adventures for the benefit of other seekers, today I compiled leafnode, discovered that it needs tcpd which I installed. Then
got caught by xinetd which was required according to the documentation
and got stuck...(not supported on my linux any longer)
But! Lo and behold!
I saw a leafnode.socket and a leafnode@.service file in the code base
and despite those not being mentioned in the INSTALL file, they looked
good enough! So after enabling those leafnode is up and running!
So far the speed of going through newsgroup on leafnode compared with my regular news provider is an enormous improvement.
The only thing I have not yet figured out is how to get my news-server
view and my localhost server view to line up.
For some reason, messages are not mirrored. I can press "&" and then
I'll get back all messages and my news-server messages are as they
should be, and in my local news server I have _all_ messages including
the latest ones, but when running fetchnews, for some reason, new
messages to not show up in server 127.0.0.1.
But I'll keep on tinkering to see if I can get it to work.
...And to continue my adventures for the benefit of other seekers, today I
compiled leafnode, discovered that it needs tcpd which I installed. Then
got caught by xinetd which was required according to the documentation and >> got stuck...(not supported on my linux any longer)
But! Lo and behold!
The openSUSE rpm supports systemd.
Telcontar:~ # rpm -ql leafnode
I saw a leafnode.socket and a leafnode@.service file in the code base and >> despite those not being mentioned in the INSTALL file, they looked good
enough! So after enabling those leafnode is up and running!
So far the speed of going through newsgroup on leafnode compared with my
regular news provider is an enormous improvement.
The only thing I have not yet figured out is how to get my news-server view >> and my localhost server view to line up.
Huh?
For some reason, messages are not mirrored. I can press "&" and then I'll >> get back all messages and my news-server messages are as they should be,
and in my local news server I have _all_ messages including the latest
ones, but when running fetchnews, for some reason, new messages to not show >> up in server 127.0.0.1.
Is the cron job running or systemd timer enabled?
It is not real time, the fetch job runs at intervals.
But I'll keep on tinkering to see if I can get it to work.
:-)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:43:01 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,188 |