+ <listitem>
+ <para>
+ Whether you are using <application>Privoxy</application> together 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>
+ <para>
+ Whether you are using a personal firewall product. If so, does
+ <application>Privoxy</application> work without it?
+ </para>
+ </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). 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
+ (all of them):
+ </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 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
+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>
+ <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
+ sure which of the debug directives are relevant, please just enable all of them
+ and let us worry about it.
+ </para>
+ <para>
+ 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>
+
+</itemizedlist>
+
+<para>
+ You don't have to tell us your actual name when filing a problem
+ 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. 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>
+ The <ulink url="https://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.
+</para>