<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/leafnode/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/leafnode/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/leafnode/feature-requests/</id><updated>2022-05-27T19:03:56.049000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#6 Support for PCRE2?</title><link href="https://sourceforge.net/p/leafnode/feature-requests/6/?limit=25#7ac0" rel="alternate"/><published>2022-05-27T19:03:56.049000Z</published><updated>2022-05-27T19:03:56.049000Z</updated><author><name>Matthias Andree</name><uri>https://sourceforge.net/u/m-a/</uri></author><id>https://sourceforge.net8ff2350126064fd3f3e9e5a5949e5133ba6d9fb0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;assigned_to&lt;/strong&gt;: Matthias Andree&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#6 Support for PCRE2?</title><link href="https://sourceforge.net/p/leafnode/feature-requests/6/?limit=25#64ab" rel="alternate"/><published>2022-05-27T19:03:34.285000Z</published><updated>2022-05-27T19:03:34.285000Z</updated><author><name>Matthias Andree</name><uri>https://sourceforge.net/u/m-a/</uri></author><id>https://sourceforge.net45983fdcd4d2b93c606c6a7244fb9f2fbd2a7431</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;1.12.0 released.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#6 Support for PCRE2?</title><link href="https://sourceforge.net/p/leafnode/feature-requests/6/?limit=25#a400" rel="alternate"/><published>2021-12-28T17:39:50.202000Z</published><updated>2021-12-28T17:39:50.202000Z</updated><author><name>Matthias Andree</name><uri>https://sourceforge.net/u/m-a/</uri></author><id>https://sourceforge.net83cca85283ccc26b2400ddda554ff5f1a7a9f2da</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;confirmed &amp;amp; work in progress. Gitlab has a preliminary leafnode 1.12.0 state that contains PCRE2-capable code and further updates and cleanups. &lt;/p&gt;
&lt;p&gt;Before release, I would also like to add systemd configuration examples since (x)inetd is going away on the Linux distros, too. Fedora 34 has neither.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for PCRE2?</title><link href="https://sourceforge.net/p/leafnode/feature-requests/6/" rel="alternate"/><published>2021-12-27T23:34:09.020000Z</published><updated>2021-12-27T23:34:09.020000Z</updated><author><name>Moritz Mühlenhoff</name><uri>https://sourceforge.net/u/jmmdebian/</uri></author><id>https://sourceforge.net0ee297832a16683349fcc1d802467205674c35e3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;PCRE is deprecated (there won't be further releases) in favour of PCRE2 and Debian plans to remove the legacy PCRE at some point: &lt;a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000110" rel="nofollow"&gt;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000110&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately PCRE-&amp;gt;PCRE2 porting documentation is pretty much non-existent, but the issue tracker at least provides some conversion examples: &lt;a href="https://github.com/PhilipHazel/pcre2/issues/51" rel="nofollow"&gt;https://github.com/PhilipHazel/pcre2/issues/51&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for PCRE2?</title><link href="https://sourceforge.net/p/leafnode/feature-requests/6/" rel="alternate"/><published>2021-12-27T23:34:09.020000Z</published><updated>2021-12-27T23:34:09.020000Z</updated><author><name>Moritz Mühlenhoff</name><uri>https://sourceforge.net/u/jmmdebian/</uri></author><id>https://sourceforge.net45c0edd63c75303cdee44e46493944e61ef5ffe6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 6 has been modified: Support for PCRE2?&lt;br/&gt;
Edited By: Matthias Andree (m-a)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'closed'&lt;br/&gt;
Owner updated: None =&amp;gt; 'm-a'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>configure --with-user at runtime</title><link href="https://sourceforge.net/p/leafnode/feature-requests/5/" rel="alternate"/><published>2015-10-25T16:20:02.541000Z</published><updated>2015-10-25T16:20:02.541000Z</updated><author><name>Alex</name><uri>https://sourceforge.net/u/alex-d/</uri></author><id>https://sourceforge.nete352b9b81a1bee2da44ea96970d00e06df61fd14</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Right now, as far as I can tell, the user allowed to run leafnode (default 'news') is set during compile.  Is it possible, or could it be, to change that user afterwards?  This would help us over at Homebrew (see &lt;a href="https://github.com/Homebrew/homebrew/issues/45255#issuecomment-150898912" rel="nofollow"&gt;https://github.com/Homebrew/homebrew/issues/45255#issuecomment-150898912&lt;/a&gt;)  since we require that builds be sudo-free.  We can set &lt;code&gt;--with-user&lt;/code&gt; during the build, but we won't be able to provide our own compiled binaries and those will have &lt;code&gt;user&lt;/code&gt; set to 'brew' .&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Programmatic access to passwords</title><link href="https://sourceforge.net/p/leafnode/feature-requests/4/" rel="alternate"/><published>2012-11-15T18:08:56Z</published><updated>2012-11-15T18:08:56Z</updated><author><name>Dave Abrahams</name><uri>https://sourceforge.net/u/userid-52572/</uri></author><id>https://sourceforge.netd5125fdc476f8d60a15de9edddd2397a03baec7d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Instead of leaving a plaintext password in the config file, it would be awesome if I could specify a command that is expected to print the password on stdout.  That way I could store the passwords in my Mac's keychain and they'd be looked up automatically.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>should leafnode also provide an imap interface</title><link href="https://sourceforge.net/p/leafnode/feature-requests/3/" rel="alternate"/><published>2009-10-18T07:13:52Z</published><updated>2009-10-18T07:13:52Z</updated><author><name>Ritesh Raj Sarraf</name><uri>https://sourceforge.net/u/riteshsarraf/</uri></author><id>https://sourceforge.netb53c9312698d02ff637fa938bbd7a03b5c1fc92d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am not sure if this is right, but for client side, should leafnode provide an IMAP interface ?&lt;/p&gt;
&lt;p&gt;Why am I asking this ?&lt;br /&gt;
Most of the times, Email clients are much well maintained than News Readers.  :-(&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>group access control</title><link href="https://sourceforge.net/p/leafnode/feature-requests/2/" rel="alternate"/><published>2006-07-20T01:12:32Z</published><updated>2006-07-20T01:12:32Z</updated><author><name>Matthew Parry</name><uri>https://sourceforge.net/u/mettw/</uri></author><id>https://sourceforge.net2119c3e4f1665250f2981aab0d56cafc71bd8193</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;If I create some local groups and give my friends&lt;br /&gt;
access to them, then (as far as I can tell) there is&lt;br /&gt;
no way to stop them from reading any other newsgroup&lt;br /&gt;
on USENET, thus possibly clogging up my hard-drive.&lt;/p&gt;
&lt;p&gt;It would be useful to have some way to control the&lt;br /&gt;
output of a LIST NNTP command so that I can restrict&lt;br /&gt;
access to groups depending on who is connected.&lt;/p&gt;
&lt;p&gt;Perhaps have a NNTP_LIST environment variable that&lt;br /&gt;
gives the name of a file containing a glob style&lt;br /&gt;
list of newsgroups to be given at a LIST command.&lt;br /&gt;
I could then control access through hosts.allow&lt;br /&gt;
as with the NOPOSTING env. var.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>New Feature Requst: Filtering OUTGOING</title><link href="https://sourceforge.net/p/leafnode/feature-requests/1/" rel="alternate"/><published>2005-07-25T19:02:51Z</published><updated>2005-07-25T19:02:51Z</updated><author><name>Andrzej Filip</name><uri>https://sourceforge.net/u/anfi/</uri></author><id>https://sourceforge.net18b300ae58936f83d4a519593a5407325a7a6b58</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would it be possible to create hook for filtering&lt;br /&gt;
OUTGOING messages?&lt;br /&gt;
I would like to remove some headers.&lt;/p&gt;
&lt;p&gt;Simple external STDIN&amp;gt;STDOUT program/script would be&lt;br /&gt;
sufficient. Some special exit codes may be used to&lt;br /&gt;
signal "do not accept post" to leafnode.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>