><P
> 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
+ <A
+HREF="../user-manual/config.html#LOGFILE"
+TARGET="_top"
+>logfile directive</A
+>
+ is being used and the following <A
+HREF="../user-manual/config.html#DEBUG"
+TARGET="_top"
+>debug options</A
+> are enabled:
+ <P
+CLASS="LITERALLAYOUT"
+>debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
+debug 2 # show each connection status<br>
+debug 4 # show I/O status<br>
+debug 8 # show header parsing<br>
+debug 128 # debug redirects<br>
+debug 256 # debug GIF de-animation<br>
+debug 512 # Common Log Format<br>
+debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
+debug 4096 # Startup banner and warnings.<br>
+debug 8192 # Non-fatal errors</P
+>
+ If you are having trouble with a filter, please additionally enable
+ <P
+CLASS="LITERALLAYOUT"
+>debug 64 # debug regular expression filters</P
+>
+ If you using Privoxy 3.0.17 or later and suspect that it interprets the
+ request or the response incorrectly, please enable
+ <P
+CLASS="LITERALLAYOUT"
+>debug 32768 # log all data read from the network</P
+>
+ 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.
</P
></LI
></UL
></P
><P
> 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.</P
+ 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.</P
><P
> 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.</P
+ 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.</P
><P
> The <A
HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-OTHER"
->6.4. Other</A
+NAME="MAILING-LISTS"
+>6.4. Mailing Lists</A
></H2
><P
->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, 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 <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DIV
></BODY
></HTML
->
\ No newline at end of file
+>
projects / privoxy.git / blobdiff