#94: Add a config directive to let Privoxy prefer either IPv4 (or IPv6) addresses

[privoxy.git] / doc / source / contacting.sgml

diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml
index 2aa5470..ac4008c 100644 (file)
--- a/doc/source/contacting.sgml
+++ b/doc/source/contacting.sgml
@@ -3,9 +3,9 @@
 
  Purpose     :  Entity included in other project documents.
                 
 
  Purpose     :  Entity included in other project documents.
                 

- $Id: contacting.sgml,v 2.13 2008/01/17 01:49:51 hal9 Exp $
+ $Id: contacting.sgml,v 2.23 2010/11/13 13:04:56 fabiankeil Exp $

 
 

- Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2010 Privoxy Developers http://www.privoxy.org/

  See LICENSE.
 
  ======================================================================
  See LICENSE.
 
  ======================================================================


@@ -52,6 +52,15 @@
  developers, either use the mailing lists or the support trackers.
 </para>
 
  developers, either use the mailing lists or the support trackers.
 </para>
 

+<para>
+ If you have to contact a Privoxy developer directly for other reasons,
+ please send a real mail and do not bother with SourceForge's messaging
+ system. Answers to SourceForge messages are usually bounced by SourceForge's
+ mail server in which case the developer wasted time writing a response you
+ don't get. From your point of view it will look like your message has
+ been completely ignored, so this is frustrating for all parties involved.
+</para>
+

 <para>
  Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
  addresses have to be accepted manually by a moderator. This may cause a
 <para>
  Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
  addresses have to be accepted manually by a moderator. This may cause a


@@ -214,7 +223,28 @@ Please be sure to provide the following information:
    <para>
     Any other pertinent information to help identify the problem such as config
     or log file excerpts (yes, you should have log file entries for each
    <para>
     Any other pertinent information to help identify the problem such as config
     or log file excerpts (yes, you should have log file entries for each

-    action taken).
+    action taken). To get a meaningful logfile, please make sure that the
+    <ulink url="../user-manual/config.html#LOGFILE">logfile directive</ulink>
+    is being used and the following <ulink
+    url="../user-manual/config.html#DEBUG">debug options</ulink> are enabled:
+    <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     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  4096 # Startup banner and warnings.
+debug  8192 # Non-fatal errors</literallayout>
+    If you are having trouble with a filter, please additionally enable
+    <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>
+    Note that Privoxy log files may contain sensitive information so please don't
+    submit any logfiles you didn't read first. You can mask sensitive information
+    as long as it's clear that you removed something.

    </para>
   </listitem> 
 
    </para>
   </listitem> 
 


@@ -223,16 +253,22 @@ Please be sure to provide the following information:
 
 <para>
  You don't have to tell us your actual name when filing a problem
 
 <para>
  You don't have to tell us your actual name when filing a problem

- report, but please use a nickname so we can differentiate between
- your messages and the ones entered by other "anonymous" users that
+ report, but if you don't, please use a nickname so we can differentiate
+ between your messages and the ones entered by other "anonymous" users that

  may respond to your request if they have the same problem or already
  may respond to your request if they have the same problem or already

- found a solution.
+ found a solution. Note that due to spam the trackers may not always
+ allow to post without being logged into SourceForge. If that's the
+ case, you are still free to create a login that isn't directly linked
+ to your name, though.

 </para>
 
 <para>
  Please also check the status of your request a few days after submitting
  it, as we may request additional information. If you use a SF id,
  you should automatically get a mail when someone responds to your request.
 </para>
 
 <para>
  Please also check the status of your request a few days after submitting
  it, as we may request additional information. If you use a SF id,
  you should automatically get a mail when someone responds to your request.

+ Please don't bother to add an email address when using the tracker.
+ If you prefer to communicate through email, just use one of the mailing
+ lists directly.

 </para>
 
 <para>
 </para>
 
 <para>


@@ -251,10 +287,13 @@ Please be sure to provide the following information:
 </para>
 </sect2>
 
 </para>
 </sect2>
 

-<sect2 id="contact-other"><title>Other</title>
+<sect2 id="mailing-lists"><title>Mailing Lists</title>

 <para>
 <para>

-For any other issues, feel free to use the mailing lists. Technically interested users
-and people who wish to contribute to the project are also welcome on the developers list!
+If you prefer to communicate through email, instead of using a web interface,
+feel free to use one of the mailing lists.
+To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
+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="http://sourceforge.net/mail/?group_id=11118">http://sourceforge.net/mail/?group_id=11118</ulink>.
 You can find an overview of all <application>Privoxy</application>-related mailing lists,
 including list archives, at:
 <ulink url="http://sourceforge.net/mail/?group_id=11118">http://sourceforge.net/mail/?group_id=11118</ulink>.