- Announcing Privoxy v.3.0.20 beta
+ Announcing Privoxy 3.0.30 stable
--------------------------------------------------------------------
-This is a beta release that introduces some new features and fixes a number of bugs, some of which are reasonably significant. One new feature (tolerate-pipelining) is enabled by default. See below for details.
+Privoxy 3.0.30 stable fixes a couple of bugs and introduces
+a few new features.
--------------------------------------------------------------------
-ChangeLog for Privoxy
+ChangeLog for Privoxy 3.0.30
--------------------------------------------------------------------
-*** Version 3.0.20 Beta ***
- Bug fixes:
- - Client sockets are now properly shutdown and drained before being
- closed. This fixes page truncation issues with clients that aggressively
- pipeline data on platforms that otherwise discard already written data.
- The issue mainly affected Opera users and was initially reported
- by Kevin in #3464439, szotsaki provided additional information to track
- down the cause.
- - Fix latency calculation for shared connections (disabled by default).
- It was broken since their introduction in 2009. The calculated latency
- for most connections would be 0 in which case the timeout detection
- failed to account for the real latency.
- - Reject URLs with invalid port. Previously they were parsed incorrectly and
- characters between the port number and the first slash were silently
- dropped as shown by curl test 187.
- - The default-server-timeout and socket-timeout directives accept 0 as
- valid value.
- - Fix a race condition on Windows that could cause Privoxy to become
- unresponsive after toggling it on or off through the taskbar icon.
- Reported by Tim H. in #3525694.
- - Fix the compilation on Windows when configured without IPv6 support.
- - Fix an assertion that could cause debug builds to abort() in case of
- socks5 connection failures with "debug 2" enabled.
- - Fix an assertion that could cause debug builds to abort() if a filter
- contained nul bytes in the replacement text.
+ - Check the actual URL for redirects when https inspecting requests.
+ Previously Privoxy would only check the path which resulted in
+ rewrite results being rejected as invalid URLs.
+ Reported by withoutname in #1736.
+ - Let the hide-referrer code tolerate Referer headers with https:// URLs.
+ Previously they would always be treated like a changed host.
+ - Use the https headers if the show-request handler is reached through
+ https://. Previously Privoxy would use the http headers which
+ may be empty on a reused connection.
+ - Make CGI_PREFIX protocol-relative when building with FEATURE_HTTPS_INSPECTION.
+ This unbreaks (at least) https://config.privoxy.org/client-tags whose
+ buttons would previously use a http:// URL resulting in browser warnings.
+ - Support using https-inspection and client-header-order at the same time.
+ Previously Privoxy would crash.
+ Reported by: Kai Raven
+ - Properly reject rewrites from http to https as they currently
+ aren't supported. Previously Privoxy would wait for the client
+ to establish an encrypted connection which obviously would not happen.
+ - When https inspection is enabled and Privoxy has been compiled with
+ FEATURE_GRACEFUL_TERMINATION (not recommended for production builds),
+ the TLS backend resources are free'd later on and only if no active
+ connections are left. Prevents crashes when exiting "gracefully" at the
+ wrong time.
+ - Let the uninstall target remove the config file even if DESTDIR
+ is set and properly announce the deletion of the configuration files.
- General improvements:
- - Significantly improved keep-alive support for both client and server
- connections.
- - New debug log level 65536 which logs all actions that were applied to
- the request.
- - New directive client-header-order to forward client headers in a
- different order than the one in which they arrived.
- - New directive tolerate-pipelining to allow client-side pipelining.
- If enabled (3.0.20 beta enables it by default), Privoxy will keep
- pipelined client requests around to deal with them once the current
- request has been served.
- - New --config-test option to let Privoxy exit after checking whether or not
- the configuration seems valid. The limitations noted in TODO #22 and #23
- still apply. Based on a patch by Ramkumar Chinchani.
- - New limit-cookie-lifetime{} action to let cookies expire before the end
- of the session. Suggested by Rick Sykes in #1049575.
- - Increase the hard-coded maximum number of actions and filter files from
- 10 to 30 (each). It doesn't significantly affect Privoxy's memory usage
- and recompiling wasn't an option for all Privoxy users that reached the
- limit.
- - Add support for chunk-encoded client request bodies. Previously
- chunk-encoded request bodies weren't guaranteed to be forwarded correctly,
- so this can also be considered a bug fix although chunk-encoded request
- bodies aren't commonly used in the real world.
- - Add support for Tor's optimistic-data SOCKS extension, which can reduce the
- latency for requests on newly created connections. Currently only the
- headers are sent optimistically and only if the client request has already
- been read completely which rules out requests with large bodies.
- - After preventing the client from pipelining, don't signal keep-alive
- intentions. When looking at the response headers alone, it previously
- wasn't obvious from the client's perspective that no additional responses
- should be expected.
- - Stop considering client sockets tainted after receving a request with body.
- It hasn't been necessary for a while now and unnecessarily causes test
- failures when using curl's test suite.
- - Allow HTTP/1.0 clients to signal interest in keep-alive through the
- Proxy-Connection header. While such client are rare in the real world, it
- doesn't hurt and couple of curl tests rely on it.
- - Only remove duplicated Content-Type headers when filters are enabled.
- If they are not it doesn't cause ill effects and the user might not want it.
- Downgrade the removal message to LOG_LEVEL_HEADER to clarify that it's not
- an error in Privoxy and is unlikely to cause any problems in general.
- Anonymously reported in #3599335.
- - Set the socket option SO_LINGER for the client socket.
- - Move several variable declarations to the beginning of their code block.
- It's required when compiling with gcc 2.95 which is still used on some
- platforms. Initial patch submitted by Simon South in #3564815.
- - Optionally try to sanity-check strptime() results before trusting them.
- Broken strptime() implementations have caused problems in the past and
- the most recent offender seems to be FreeBSD's libc (standards/173421).
- - When filtering is enabled, let Range headers pass if the range starts at
- the beginning. This should work around (or at least reduce ) the video
- playback issues with various Apple clients as reported by Duc in #3426305.
- - Do not confuse a client hanging up with a connection time out. If a client
- closes its side of the connection without sending a request line, do not
- send the CLIENT_CONNECTION_TIMEOUT_RESPONSE, but report the condition
- properly.
- - Allow closing curly braces as part of action values as long as they are
- escaped.
- - On Windows, the logfile is now written before showing the GUI error
- message which blocks until the user acknowledges it.
- Reported by Adriaan in #3593603.
- - Remove an unreasonable parameter limit in the CGI interface. The new
- parameter limit depends on the memory available and is currently unlikely
- to be reachable, due to other limits in both Privoxy and common clients.
- Reported by Andrew on ijbswa-users@.
- - Decrease the chances of parse failures after requests with unsupported
- methods were sent to the CGI interface.
-
-*** Version 3.0.19 Stable ***
-
-- Bug fixes:
- - Prevent a segmentation fault when de-chunking buffered content.
- It could be triggered by malicious web servers if Privoxy was
- configured to filter the content and running on a platform
- where SIZE_T_MAX isn't larger than UINT_MAX, which probably
- includes most 32-bit systems. On those platforms, all Privoxy
- versions before 3.0.19 appear to be affected.
- To be on the safe side, this bug should be presumed to allow
- code execution as proving that it doesn't seems unrealistic.
- - Do not expect a response from the SOCKS4/4A server until it
- got something to respond to. This regression was introduced
- in 3.0.18 and prevented the SOCKS4/4A negotiation from working.
- Reported by qqqqqw in #3459781.
-
-- General improvements:
- - Fix an off-by-one in an error message about connect failures.
- - Use a GNUMakefile variable for the webserver root directory and
- update the path. Sourceforge changed it which broke various
- web-related targets.
- - Update the CODE_STATUS description.
+ - Allow to rewrite the request destination for https-inspected
+ requests behind the client's back. The documentation already sort
+ of claimed that it was supported by not especially mentioning that
+ it didn't work for https-inspected requests.
+ Fixes SF bug #923 reported by withoutname.
+ - Add support for filtering client request bodies by using
+ CLIENT-BODY-FILTER filters which can be enabled with the
+ client-body-filter action.
+ Patch submitted by Maxim Antonov.
+ Sponsored by: Robert Klemme
+ - Add the new action suppress-tag{} which can be used to prevent
+ a tagger from adding a tag. Patch submitted by Maxim Antonov.
+ Sponsored by: Robert Klemme
+ - Gracefully handle existing website keys without matching certificates.
+ This can happen if Privoxy was previously running with an invalid
+ TLS configuration that didn't allow it to create a certificate.
+ - Recycle debug bit 4 for Tagging-related messages.
+ - Improve the message shown when the client-tags CGI page
+ is requested with no tags configured.
+ - Shorten the 'donate' and 'participate' links used by templates
+ using redirects. Currently the redirects lead to the FAQ entries
+ but in the future we may want to relocate the content and using
+ redirects makes this more convenient.
+ - Log an error when a PCRE-HOST-PATTERN is used with
+ FEATURE_PCRE_HOST_PATTERNS disabled. Don't treat this a
+ fatal error so the regression tests can be used with and
+ without FEATURE_PCRE_HOST_PATTERNS.
+ - The code compiles with older C compilers again.
+ - The chdir() return code is checked to fix a compiler warning.
+ - The packages feed has been removed from the source tarball.
+ It's usually out of date when the source tarball is generated
+ for the release.
+ - Fixed harmless compiler warnings from GCC9 with -D_FORTIFY_SOURCE=2.
+ - windows: Remove obsolete '$(DEST)/doc/images' target.
+ - windows: Install the images referenced in the user manual.
+ - Remove obsolete 'gnu_regex.@OBJEXT@' target.
+ - When installing from the GNUMAkefile, don't create an 'images'
+ directory which is no longer used. The images were relocated to
+ the user-manual directory years ago.
+ - Add new FEATURES to the show-status page and resort list.
+ - Remove unused variable in the OpenSSL-specific code.
+ - Update bug tracker URL in cgi_error_unknown().
+ - Saved a couple of memory allocations when sorting client headers.
+ - Improved a couple of error messages.
+ - Saved memory allocations when using OpenSSL and checking if a
+ key already exists.
+ - The configure script will bail out if OpenSSL and mbedTLS are
+ enabled at the same time.
+ - Log a message right before exiting gracefully.
+ - A couple of structures have been rearranged to require slightly
+ less memory.
+ - When https inspection is enabled and the certificate is invalid
+ the error message is now sent with status code 403 instead of 200.
+ - The Slackware rc script template has been renamed to
+ slackware/rc.privoxy.in to silence complaints when building
+ Debian packages.
+ - When building with MbedTLS support, mbedtls_md5_ret() is used
+ instead of mbedtls_md5() which is deprecated and causes a warning
+ on Debian GNU/Linux.
+
+- Action file improvements:
+ - Block requests to eu-tlp03.kameleoon.com/.
+ - Unblock metrics.sr.ht/.
+ - Disable fast-redirects for .fsf.org/.
+ - Disable fast-redirects for .gravater.com/.
+ - Disable fast-redirects for .ksta.de/.
+ - Block requests to tag.crsspxl.com/.
+ - Block requests to analytics.slashdotmedia.com/.
+ - Block requests to ml314.com/.
+ - Block requests to .adroll.com/.
+ - Block requests to fastlane.rubiconproject.com/.
+ - Block requests to api.theadex.com/.
+ - Block requests to ih.adscale.de/.
+ - Block requests to .s400.meetrics.net/.
+ - Block requests for pp.lp4.io/.
+ - Block requests for trc-events.taboola.com/.
+
+- Filter file improvements:
+ - A allow-autocompletion filter has been added which changes
+ autocomplete="off" to "on" on input fields to allow autocompletion.
+ Requested by Jamie Zawinski in #370.
+ Filter based on a submission by Aaron Linville.
+ - Added an imdb filter.
+ - Added a sourceforge filter that reduces the amount of ads
+ for proprietary software.
+ - Added a github filter that removes the annoying "Sign-Up"
+ banner and the Cookie disclaimer.
+ - Removed a duplicated pcrs command from the js-annoyances filter.
+ - The crude-parental filter now provides a short reason when blocking,
+ inserts a link to Privoxy's webinterface and adds a new line at
+ the end of the generated page.
+
+- Privoxy-Log-Parser:
+ - Highlight a few more messages.
+ - Add a handler for tagging messages.
+ - Properly deal with 'Certificate error' crunches
+ Previously the error description was highlighted as 'host'.
+ - Log truncated LOG_LEVEL_CLF messages more gracefully
+ and note that the statistics will be imprecise.
+ - Fixed perldoc typo.
+ - Bump version to 0.9.2.
+
+- Privoxy-Regression-Test:
+ - Use http://127.0.0.1:8118/ as default Privoxy address
+ unless http_proxy is set through the environment.
+ - Add a --privoxy-cgi-prefix option that specifies the prefix
+ to use when building URLs that are supposed to reach Privoxy's
+ CGI interface. If it's not set, http://p.p/ is used, which is
+ supposed to work with the default Privoxy configuration.
+ If Privoxy has been built with FEATURE_HTTPS_INSPECTION enabled,
+ and if https inspection is activated with the +https-inspection
+ action, this option can be used with "https://p.p/" provided the
+ system running Privoxy-Regression-Test has been configured to
+ trust the certificate used by Privoxy.
+ Note that there are currently two tests in the official
+ regression-tests.action file that are expected to fail
+ when using "https://p.p/" as privoxy-cgi-prefix.
+ - Skip the connection-established response in get_status_code()
+ when looking for the status code with a CGI prefix
+ that starts with https://. We care about the status code
+ sent by the impersonated web server.
+ - Use --proxy-header when using a CGI prefix with https://
+ and a "Host:" header.
+ - Allow '|' in tokens and values to allow tag patterns like
+ "TAG:^(application|text)/(x-)?javascript$".
+ - When get_cgi_page_or_else() fails, include the URL of the
+ requested page in the log message.
+ - Added a --check-bad-ssl option that can be used to verify that
+ Privoxy detects certificate problems when accessing the test
+ sites from badssl.com.
+ - Bumped version to 0.7.2
+
+- uagen:
+ - Update example output.
+ - Recommend the use of the https-inspection action in the documentation.
+ - Upgrade a couple of URLs to https://.
+ - Add ElectroBSD to the list of operating systems.
+ - Bumped generated Firefox version to 78 (ESR).
+ - Bumped version to 1.2.2.
+
+ - User documentation:
+ - Remove reference to 'How to Report Bugs Effectively'.
+ It was only rendered as text without URL in the README anyway
+ and there's no indication that users read it ...
+ - Let the dok-readme target fix the location embedded into the
+ README file. This used to be done by CVS but since the git migration
+ it has to be done through other means.
+ - Remove 'experimental' warning for client-specific-tag-related directives.
+ They seem to work reliably and there is no obvious reason
+ why we would change the syntax in the near future.
+ - Describe how to check if Privoxy has been built with
+ FEATURE_HTTPS_INSPECTION.
+ - Add a link to the trusted-cas-file documentation
+ that explains how the user can create the file herself.
+ - Don't explicitly mention the license for the code coming from
+ 'Anonymous Coders' and Junkbusters. It's obviously licensed under
+ the GNU GPL like the rest of Privoxy or we wouldn't be allowed to
+ distribute it.
+ - Update the +hide-user-agent example with uagen output.
+ - Slightly improve the wording of the ca-key-file documentation.
+ - Explicitly mention Windows 10 as supported so search engines and
+ users looking for it can find it.
+ - Import a bunch of contributors from the ChangeLog.
+ - Remove obsolete doc/gpl.html.
+ - Upgrade a couple of links to https://.
+ - Don't prefer the SourceForge patch tracker over the
+ privoxy-devel mailing list. While at it, link to the
+ SourceForge patch tracker.
+ - Mention http-inspection in the 'my browser warns me about
+ unauthenticated content' FAQ entry.
+ - Simplify the 'Is there is a license or fee?' FAQ entry.
+ - Add another +redirect{} example.
+ - Explicitly mention that interested sponsors should include
+ the link target in their first mail.
+ - Clarify that only Privoxy team members can object to new sponsors
+ and link to the list of current team members.
+ - Note that sponsor URLs may not contain keyword spam.
+ - Garbage collect doc/webserver/images which isn't referenced anymore.
+ - Update the method to reach the proxy settings in Firefox.
+ - Update proxy_setup.jpg description to refer to Firefox.
+ - Regenerate proxy_setup.jpg with a more recent Firefox (78.0).
+ - Regenerate files-in-use.jpg without obsolete standard.action
+ with modern colors and a slightly better quality.
+ - Update URL to the actionsfile tracker.
+ - Update a support request URL.
+ - Rephrase the 'Can Privoxy run as service' FAQ entry and
+ remove an obsolete paragraph.
+ - Let the 'Where can I get updated Actions Files?' entry link to
+ the gitweb version of default.action.master.
+ - Update a link to the default.action file.
+ - Update URLs for trackers and mailing lists.
+ - Replace CVS reference with git.
+ - Mention regression-tests.action in the config file.
+ - Explicitly mention in the config file that access to the
+ CA key should be limited to Privoxy.
+ - List more client-specific-tag examples for inspiration.
+ - Add additional headers to the client-header-order example.
+ - Note that actions aren't updated after rewrites.
+ - Explicitly mention that upgrading from http to https with
+ a client-header filter is not supported
+ - Note that protocol and host have to be added when rewriting
+ the destination host for https-inspected requests.
+ - Explicitly mention that the CA key is used to sign certificates.
+ - Put openssl command in 'command' tags.
+ - The man page has been moved from section 1 to man section 8.
+
+- Developer manual:
+ - Flesh out the build instructions for Debian.
+ - Remove the packaging instructions for RPM-based systems.
+ They don't work and we don't release RPM packages anymore anyway.
+ - Remove the packaging instructions for Solaris.
+ They don't work and we don't release Solaris packages anymore anyway.
+ - Update the suggested subject for the announce mails.
+ - Update upload instructions.
+ ftp://upload.sourceforge.net is no longer functional.
+ - Remove a couple of package-dependent upload instructions
+ that don't actually work.
+ - Remove 'cd current' that no longer works.
+ - Add regression-tests.action to the list of files that should be installed.
+ - Stop claiming that there are text versions of the manuals.
+ We stopped building them in 2008 (9ed36a3c5e6f12).
+ - Note that the 'webserver' target creates the link needed for the user-manual.
+ - Suggest to use the master branch as reference when creating
+ the ChangeLog so the steps work when the current branch differs
+ from master which is likely as the developer manual
+ suggests to use a local branch for development.
+ - Add the -s flag to the suggested 'git tag' command. We prefer signed tags.
+ - Mention that merges into 'master' should be avoided.
+ - Add git commands that should result in a merge-free history.
+ - Mention Privoxy-Regression-Test.
+ - Add a section id to reduce link churn.
+ - Recommend the dok-tidy target when building docs for the webserver.
+ - Add another plug for the privoxy-devel mailing list.
+ - Let the intro link the copyright section in the user manual instead
+ of giving an incomplete summary of the license status.
+ - Clarify that the webserver target uploads to the SourceForge webserver.
+ - Mark the documentation for the Mac OS X installers as out of date and
+ change the SCM name back to CVS.
+ - Fix the location of the installer modules for Mac OS X.
+ They are not actually available through git (yet).
+ - Don't speak of Privoxy version 3 in the past tense.
+ - Update the list of programs required for the release process.
+ - Update description of the webserver target which uses ssh, not scp.
+ - Remove obsolete reference to config.new.
+
+- Tests:
+ - Add another hide-referrer{conditional-block} test.
+ - Add another hide-referrer{conditional-forge} test.
+ - Fix a hide-referrer{conditional-forge} test
+ that expected an acceptable header to be forged.
+ - Fix a hide-referrer{conditional-block} test
+ that expected an acceptable Referer to be removed.
+ - Explain why the "Set Header = Host: whatever.example.org" test is
+ expected to fail when using a CGI prefix that starts with "https://".
+ - Explain why a connection-sharing test is known to fail
+ when using "https://p.p/" as CGI prefix.
+ - Add a link to Privoxy-Regression-Test to regression-tests.action
+ in case it isn't packaged.
+ - Add regression tests for pcre host patterns.
+ - Fixed a regression test that is executed when
+ FEATURE_GRACEFUL_TERMINATION is enabled.
+
+- Privoxy infrastructure:
+ - Import a Privoxy logo for the website.
+ - Update Tor onion service to HiddenServiceVersion 3.
+ - Display the "model" photos in a single row and remove placeholder images.
+ - Regenerate homepage with updated sponsor list.
+ - Use the '/sponsor' redirect for the link to the sponsor page.
+ - Git commit messages are sent to the Privoxy-commits mailing list.
-----------------------------------------------------------------
About Privoxy:
Privoxy is Free Software and licensed under the GNU GPLv2.
-Privoxy is an associated project of Software in the Public Interest (SPI).
+Our TODO list is rather long. Helping hands and donations are welcome:
-Helping hands and donations are welcome:
+ * https://www.privoxy.org/participate
- * http://www.privoxy.org/faq/general.html#PARTICIPATE
+ * https://www.privoxy.org/donate
- * http://www.privoxy.org/faq/general.html#DONATE
-
-At present, Privoxy is known to run on Windows(95, 98, ME, 2000,
-XP, Vista), GNU/Linux (Ubuntu, RedHat, SuSE, Debian, Fedora, Gentoo and
-others), Mac OSX, OS/2, AmigaOS, FreeBSD, NetBSD, OpenBSD, Solaris, and
-various other flavors of Unix.
+At present, Privoxy is known to run on Windows 95 and later versions
+(98, ME, 2000, XP, Vista, Windows 7, Windows 10 etc.), GNU/Linux
+(RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and others),
+Mac OS X (10.4 and upwards on PPC and Intel processors), Haiku,
+DragonFly, ElectroBSD, FreeBSD, NetBSD, OpenBSD, Solaris,
+and various other flavors of Unix.
In addition to the core features of ad blocking and cookie management,
Privoxy provides many supplemental features, that give the end-user
more control, more privacy and more freedom:
+ * Supports "Connection: keep-alive". Outgoing connections can be kept
+ alive independently from the client. Currently not available on all
+ platforms.
- * Supports "Connection: keep-alive". Outgoing connections can be kept
- alive independently from the client. Currently not available on all
- platforms.
+ * Supports IPv6, provided the operating system does so too,
+ and the configure script detects it.
- * Supports IPv6, provided the operating system does so too,
- and the configure script detects it.
+ * Supports tagging which allows to change the behaviour based on client
+ and server headers.
- * Supports tagging which allows to change the behaviour based on client
- and server headers.
+ * Supports https inspection which allows to filter https requests.
- * Can be run as an "intercepting" proxy, which obviates the need to
- configure browsers individually.
+ * Can be run as an "intercepting" proxy, which obviates the need to
+ configure browsers individually.
- * Sophisticated actions and filters for manipulating both server and
- client headers.
+ * Sophisticated actions and filters for manipulating both server and
+ client headers.
- * Can be chained with other proxies.
+ * Can be chained with other proxies.
- * Integrated browser based configuration and control utility at
- http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based
- tracing of rule and filter effects. Remote toggling.
+ * Integrated browser based configuration and control utility at
+ http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based
+ tracing of rule and filter effects. Remote toggling.
- * Web page filtering (text replacements, removes banners based on size,
- invisible <quote>web-bugs</quote> and HTML annoyances, etc.)
+ * Web page filtering (text replacements, removes banners based on size,
+ invisible "web-bugs" and HTML annoyances, etc.)
- * Modularized configuration that allows for standard settings and user
- settings to reside in separate files, so that installing updated actions
- files won't overwrite individual user settings.
+ * Modularized configuration that allows for standard settings and user
+ settings to reside in separate files, so that installing updated actions
+ files won't overwrite individual user settings.
- * Support for Perl Compatible Regular Expressions in the configuration
- files, and a more sophisticated and flexible configuration syntax.
+ * Support for Perl Compatible Regular Expressions in the configuration
+ files, and a more sophisticated and flexible configuration syntax.
- * GIF de-animation.
+ * GIF de-animation.
- * Bypass many click-tracking scripts (avoids script redirection).
+ * Bypass many click-tracking scripts (avoids script redirection).
- * User-customizable HTML templates for most proxy-generated pages (e.g.
- "blocked" page).
+ * User-customizable HTML templates for most proxy-generated pages (e.g.
+ "blocked" page).
- * Auto-detection and re-reading of config file changes.
-
- * Most features are controllable on a per-site or per-location basis.
+ * Auto-detection and re-reading of config file changes.
+ * Most features are controllable on a per-site or per-location basis.
-Download location:
- http://sourceforge.net/project/showfiles.php?group_id=11118
-
-Home Page:
- http://www.privoxy.org/
+Home Page:
+ https://www.privoxy.org/
- - Privoxy Developers <ijbswa-developers@lists.sourceforge.net>
+ - Privoxy Developers <privoxy-devel@lists.privoxy.org>