X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=640ea7d50b9914e232a318c6cf7c93599be41bf4;hp=294715d9cf8c6c6791fe9ad6c236f7f65ab88034;hb=125db0e9a702bf21a54d10f0555fc0665b786f96;hpb=ec4a051cd6a42c47dd9cf2fec9a1ab179649c6d5

diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml
index 294715d9..640ea7d5 100644
--- a/doc/source/contacting.sgml
+++ b/doc/source/contacting.sgml
@@ -1,11 +1,9 @@
 <!--
- File        :  $Source: /cvsroot/ijbswa/current/doc/source/contacting.sgml,v $
+ File        :  doc/source/contacting.sgml
 
  Purpose     :  Entity included in other project documents.
 
- $Id: contacting.sgml,v 2.42 2016/04/09 10:23:54 fabiankeil Exp $
-
- Copyright (C) 2001-2011 Privoxy Developers https://www.privoxy.org/
+ Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
  See LICENSE.
 
  ======================================================================
@@ -65,7 +63,6 @@
   Please be sure to provide the following information when reporting problems
   or requesting support:
 </para>
-<para>
  <itemizedlist>
 
   <listitem>
@@ -128,24 +125,29 @@
     is being used and the following <ulink
     url="../user-manual/config.html#DEBUG">debug options</ulink> are enabled
     (all of them):
-    <literallayout>debug     1 # Log the destination for each request Privoxy let through. See also debug 1024.
+   </para>
+    <literallayout>debug     1 # Log the destination for each request Privoxy let through.
+            #   See also debug 1024.
 debug     2 # show each connection status
-debug     4 # show I/O status
+debug     4 # show tagging-related messages
 debug     8 # show header parsing
 debug   128 # debug redirects
 debug   256 # debug GIF de-animation
 debug   512 # Common Log Format
-debug  1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
+debug  1024 # Log the destination for requests Privoxy didn't let through,
+            #   and the reason why.
 debug  4096 # Startup banner and warnings.
-debug  8192 # Non-fatal errors</literallayout>
-   </para>
+debug  8192 # Non-fatal errors
+debug 65536 # Log applying actions</literallayout>
    <para>
     If you are having trouble with a filter, please additionally enable
+   </para>
     <literallayout>debug    64 # debug regular expression filters</literallayout>
-    If you are using Privoxy 3.0.17 or later and suspect that it interprets the
-    request or the response incorrectly, please enable
-    <literallayout>debug 32768 # log all data read from the network</literallayout>
+   <para>
+    If you suspect that Privoxy interprets the request or the response
+    incorrectly, please enable
    </para>
+    <literallayout>debug 32768 # log all data read from the network</literallayout>
    <para>
     It's easy for us to ignore log messages that aren't relevant but missing
     log messages may make it impossible to investigate a problem. If you aren't
@@ -160,7 +162,6 @@ debug  8192 # Non-fatal errors</literallayout>
   </listitem>
 
 </itemizedlist>
-</para>
 
 <para>
  You don't have to tell us your actual name when filing a problem
@@ -184,7 +185,7 @@ debug  8192 # Non-fatal errors</literallayout>
 
 <para>
  If you are new to reporting problems, you might be interested in
-  <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
+  <ulink url="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
   >How to Report Bugs Effectively</ulink>.
 </para>
 
@@ -197,7 +198,7 @@ debug  8192 # Non-fatal errors</literallayout>
 <sect2 id="contact-support"><title>Get Support</title>
 <para>
  All users are welcome to discuss their issues on the <ulink
- url="https://lists.sourceforge.net/lists/listinfo/ijbswa-users">users
+ url="https://lists.privoxy.org/mailman/listinfo/privoxy-users">users
  mailing list</ulink>, where the developers also hang around.
 </para>
 
@@ -262,8 +263,8 @@ debug  8192 # Non-fatal errors</literallayout>
  Please send feedback on ads that slipped through, innocent images that were
  blocked, sites that don't work properly, and other configuration related problem of
  <filename>default.action</filename> file, to
- <ulink url="https://sourceforge.net/tracker/?group_id=11118&amp;atid=460288">
- https://sourceforge.net/tracker/?group_id=11118&amp;atid=460288</ulink>,
+ <ulink url="https://sourceforge.net/p/ijbswa/actionsfile-feedback/"
+ >https://sourceforge.net/p/ijbswa/actionsfile-feedback/</ulink>,
  the Actions File Tracker.
 </para>
 
@@ -275,7 +276,7 @@ debug  8192 # Non-fatal errors</literallayout>
 <para>
   Before reporting bugs, please make sure that the bug has <emphasis>not already been submitted</emphasis>
   and observe the additional hints at the top of the <ulink
-  url="https://sourceforge.net/tracker/?func=add&amp;group_id=11118&amp;atid=111118">submit
+  url="https://sourceforge.net/p/ijbswa/bugs/">submit
   form</ulink>. If already submitted, please feel free to add any info to the
   original report that might help to solve the issue.
 </para>
@@ -305,18 +306,20 @@ users list. Technically interested users and people who wish to contribute to
 the project are always welcome on the developers list.
 You can find an overview of all <application>Privoxy</application>-related mailing lists,
 including list archives, at:
-<ulink url="https://sourceforge.net/mail/?group_id=11118">https://sourceforge.net/mail/?group_id=11118</ulink>.
+<ulink url="https://lists.privoxy.org/mailman/listinfo">https://lists.privoxy.org/mailman/listinfo</ulink>.
+The lists hosted on privoxy.org have been created in 2016, the previously-used
+lists hosted at SourceForge are deprecated but the archives may still be useful:
+<ulink url="https://sourceforge.net/p/ijbswa/mailman/">https://sourceforge.net/p/ijbswa/mailman/</ulink>.
 </para>
 </sect2>
 
 <sect2 id="sf-trackers"><title>SourceForge support trackers</title>
 <para>
  The
- <ulink url="https://sourceforge.net/tracker/?group_id=11118&#38;atid=211118">SourceForge support trackers</ulink>
+ <ulink url="https://sourceforge.net/p/ijbswa/support-requests/">SourceForge support trackers</ulink>
  may be used as well, but have various technical problems that are unlikely to
  be fixed anytime soon. If you don't get a timely response, please try the
- mailing list as well. While it's hosted at SourceForge as well, it usually
- works as expected.
+ mailing list as well.
 </para>
 
 </sect2>