Re: [PLUG] Syllable Operating System, what happened?
The developers have definitely given up. But there are at least a few people still trying to use it: https://sourceforge.net/p/syllable/mailman/syllable-developer/ -wes On Wed, Oct 24, 2018 at 7:29 PM wrote: > I notice that my link to http://www.syllable.org doesn't work these days. > Did the community behind Syllable give up on it? > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] Syllable Operating System, what happened?
I notice that my link to http://www.syllable.org doesn't work these days. Did the community behind Syllable give up on it? ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] GPLv2 verses Oracle java license...
Oracle has a weird license for Java 11 SE. I'm wondering what the state of openjdk is and if I can use that in Windows 7? What is the difference between JDK 11.0.1 Oracle license and JDK 11.0.1 GPL v2 with an exclusion clause? I am writing a financial calculator for a company that sells insurance, so I need to pay attention to licensing. I prefer to implement this license wise in a Linux friendly/ReactOS friendly manner. One never knows if ReactOS stabilizes whether or not this company will stick with Microsoft Windows 7. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Paul Heinlein wrote: By default, the regex is run only against the mail headers, though procmail recipes can grep the message body as well if you'd like. Paul, I didn't know this. The reason I like grep-ing the List-Id header is that, for instance, personal replies to list messages will end up in my inbox rather than in the list folder. Good point; I'll change all recipes to use List-Id. Often response messages sent to 'all' end up in my inbox as well as the mail list, but those sent to me don't appear on the latter. If you choose to match the Subject: header, make sure your rule is flexible enough to match reply (re:, Re:, etc) strings prior to the group name. See, for instance, the Subject: header in this message. Meh. The current recipes for most mail lists work OK. Why this one list changed its behavior I've no idea, except that it's sent via osgeo.org rather than grass.org. Thanks for the insights, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Rich Shepard wrote: On Wed, 24 Oct 2018, Paul Heinlein wrote: There's nothing special about the List-Id header; it's just something that Mailman inserts into outbound messages. Perhaps other list managers use it as well. Open a list message in Alpine and press the H key to see the full headers. You should be able to spot that header if it's there. If not, the osgeo.org list server may have another header that procmail can spot. Paul, Yep, it's there all right. I was thinking of using the subject line tag associated with that list: Subject: [GRASS-user] because I was not familiar with all recipe options for procmail. All procmail does is run a case-insensitive egrep regular expression against your inbound messages. By default, the regex is run only against the mail headers, though procmail recipes can grep the message body as well if you'd like. The reason I like grep-ing the List-Id header is that, for instance, personal replies to list messages will end up in my inbox rather than in the list folder. If you choose to match the Subject: header, make sure your rule is flexible enough to match reply (re:, Re:, etc) strings prior to the group name. See, for instance, the Subject: header in this message. -- Paul Heinlein heinl...@madboa.com 45°38' N, 122°6' W___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Paul Heinlein wrote: There's nothing special about the List-Id header; it's just something that Mailman inserts into outbound messages. Perhaps other list managers use it as well. Open a list message in Alpine and press the H key to see the full headers. You should be able to spot that header if it's there. If not, the osgeo.org list server may have another header that procmail can spot. Paul, Yep, it's there all right. I was thinking of using the subject line tag associated with that list: Subject: [GRASS-user] because I was not familiar with all recipe options for procmail. Thanks again, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Rich Shepard wrote: On Wed, 24 Oct 2018, Paul Heinlein wrote: Does the list provide a List-Id header? That's usually the one I use, e.g., # mailing lists : 0 * ^List-Id:.*<(plug|plug-talk)\.pdxlinux\.org> .mailinglists.plug/ Paul, Yes. In this case the grass-u...@lists.osgeo.org. I tried that preceeded by ^(From|Cc|To) as well as the above address and both failed. I was unaware of the List-Id: label, even after reading the man and web pages. I'll try that now. There's nothing special about the List-Id header; it's just something that Mailman inserts into outbound messages. Perhaps other list managers use it as well. Open a list message in Alpine and press the H key to see the full headers. You should be able to spot that header if it's there. If not, the osgeo.org list server may have another header that procmail can spot. -- Paul Heinlein heinl...@madboa.com 45°38' N, 122°6' W___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Paul Heinlein wrote: Does the list provide a List-Id header? That's usually the one I use, e.g., # mailing lists :0 * ^List-Id:.*<(plug|plug-talk)\.pdxlinux\.org> .mailinglists.plug/ Paul, Yes. In this case the grass-u...@lists.osgeo.org. I tried that preceeded by ^(From|Cc|To) as well as the above address and both failed. I was unaware of the List-Id: label, even after reading the man and web pages. I'll try that now. Thanks, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Sorting mail with procmail recipe
On Wed, 24 Oct 2018, Rich Shepard wrote: One mail list to which I am subscribed is no longer obeying the recipe in ~/procmail/recipes.rc. It's probably a regex error and I'd like to learn why so I can fix it. The current recipe is: : 0: * ^(From|Cc|To).*lists.osgeo.org spatial-analyses A recent message in my INBOX rather than that file is addressed this way: To: grass-u...@lists.osgeo.org Rich, Does the list provide a List-Id header? That's usually the one I use, e.g., # mailing lists :0 * ^List-Id:.*<(plug|plug-talk)\.pdxlinux\.org> .mailinglists.plug/ -- Paul Heinlein heinl...@madboa.com 45°38' N, 122°6' W___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] Sorting mail with procmail recipe
One mail list to which I am subscribed is no longer obeying the recipe in ~/procmail/recipes.rc. It's probably a regex error and I'd like to learn why so I can fix it. The current recipe is: :0: * ^(From|Cc|To).*lists.osgeo.org spatial-analyses A recent message in my INBOX rather than that file is addressed this way: To: grass-u...@lists.osgeo.org The former recipe had this form: :0: * ^TO_.*@lists.osgeo.org spatial-analyses which works for To: and Cc: on other mail lists (and used to work for the osgeo.org maillists, too. Your thoughts welcomed. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
