File : $Source: /cvsroot/ijbswa/current/doc/source/contacting.sgml,v $
Purpose : Entity included in other project documents.
-
- $Id: contacting.sgml,v 2.10 2006/11/14 01:57:46 hal9 Exp $
- Copyright (C) 2001 - 2007 Privoxy Developers http://www.privoxy.org/
+ $Id: contacting.sgml,v 2.28 2011/10/23 11:22:54 fabiankeil Exp $
+
+ Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/
See LICENSE.
======================================================================
<para>
We value your feedback. In fact, we rely on it to improve
<application>Privoxy</application> and its configuration.
- However, please note the following hints, so we can
+ However, please note the following hints, so we can
provide you with the best support:
</para>
<sect2 id="contact-support"><title>Get Support</title>
<para>
- For casual users, our
+ For casual users, our
<ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">support forum at SourceForge</ulink>
is probably best suited:
<ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">http://sourceforge.net/tracker/?group_id=11118&atid=211118</ulink>
mailing list</ulink>, where the developers also hang around.
</para>
+<para>
+ Please don't sent private support requests to individual Privoxy
+ 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
<listitem>
<para>
- Configuration issues, such as ads that slip through, or sites that
- don't function properly due to one <application>Privoxy</application>
+ Configuration issues, such as ads that slip through, or sites that
+ don't function properly due to one <application>Privoxy</application>
<quote>action</quote> or another being turned <quote>on</quote>.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
- <quote>Bugs</quote> in the programming code that makes up
+ <quote>Bugs</quote> in the programming code that makes up
<application>Privoxy</application>, such as that might cause a crash.
</para>
- </listitem>
+ </listitem>
</itemizedlist>
<sect3 id="contact-ads"><title>Reporting Ads or Other Configuration Problems</title>
<para>
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
+ blocked, sites that don't work properly, and other configuration related problem of
+ <filename>default.action</filename> file, to
<ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=460288">
http://sourceforge.net/tracker/?group_id=11118&atid=460288</ulink>,
the Actions File Tracker.
-</para>
+</para>
<para>
New, improved <filename>default.action</filename> files may occasionally be made
<sect3 id="contact-bugs"><title>Reporting Bugs</title>
<para>
- Please report all bugs through our bug tracker:
- <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">http://sourceforge.net/tracker/?group_id=11118&atid=111118</ulink>.
+ Please report all bugs through our bug tracker:
+ <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">http://sourceforge.net/tracker/?group_id=11118&atid=111118</ulink>.
</para>
<para>
Before doing so, 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="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118">submit
- form</ulink>. If already submitted, please feel free to add any info to the
+ form</ulink>. If already submitted, please feel free to add any info to the
original report that might help to solve the issue.
</para>
that your bug still exists.
</para>
<para>
-Please be sure to provide the following information:
+ Please be sure to provide the following information:
</para>
<para>
<itemizedlist>
(if you got the source from CVS, please also provide the source code revisions
as shown in <ulink url="http://config.privoxy.org/show-version">http://config.privoxy.org/show-version</ulink>).
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
sending the output of <quote>uname -a</quote> should do,
in case of GNU/Linux, please also name the distribution.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
- The name, platform, and version of the <application>browser</application>
+ The name, platform, and version of the <application>browser</application>
you were using (e.g. <application>Internet Explorer v5.5</application> for Mac).
</para>
</listitem>
<listitem>
<para>
The URL where the problem occurred, or some way for us to duplicate the
- problem (e.g. <literal>http://somesite.example.com/?somethingelse=123</literal>).
+ problem (e.g. <literal>http://somesite.example.com/?somethingelse=123</literal>).
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
by the <application>Privoxy</application> developers via SourceForge,
or if you got your copy somewhere else.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
- Whether you are using <application>Privoxy</application> in tandem with
+ Whether you are using <application>Privoxy</application> in tandem with
another proxy such as <application>Tor</application>. If so, please
temporary disable the other proxy to see if the symptoms change.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
- Whether you are using a personal firewall product. If so, does
+ Whether you are using a personal firewall product. If so, does
<application>Privoxy</application> work without it?
</para>
- </listitem>
+ </listitem>
<listitem>
<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>
+ </listitem>
</itemizedlist>
</para>
<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
- 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.
+ 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>
+ If you are new to reporting problems, you might be interested in
+ <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
+ >How to Report Bugs Effectively</ulink>.
+</para>
+
+<para>
+ If you are new to reporting problems, you might be interested in
+ <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
+ >How to Report Bugs Effectively</ulink>.
</para>
<para>
The <ulink url="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT">appendix
- of the Privoxy User Manual</ulink> also has helpful information
- on understanding <literal>actions</literal>, and <literal>action</literal> debugging.
+ of the Privoxy User Manual</ulink> also has helpful information
+ on understanding <literal>actions</literal>, and <literal>action</literal> debugging.
</para>
</sect3>
</sect2>
</para>
</sect2>
-<sect2 id="contact-other"><title>Other</title>
+<sect2 id="mailing-lists"><title>Mailing Lists</title>
<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>.
projects / privoxy.git / blobdiff