X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=ceb305799aaa8e86669bbba4ce72762e571c8c72;hb=dc157ddd29a5d6a43111b1be33f2c53b597f5786;hp=f86c29f78cab977913c43c52eeed969ae3e96a4b;hpb=249ba07cbd558908f4a012931c8bc4814c2186d1;p=privoxy.git
diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml
index f86c29f7..ceb30579 100644
--- a/doc/source/contacting.sgml
+++ b/doc/source/contacting.sgml
@@ -2,10 +2,10 @@
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.29 2011/11/06 11:35:26 fabiankeil Exp $
+
+ Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/
See LICENSE.
======================================================================
@@ -29,13 +29,13 @@
We value your feedback. In fact, we rely on it to improve
Privoxy 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:
Get Support
- For casual users, our
+ For casual users, our
support forum at SourceForge
is probably best suited:
http://sourceforge.net/tracker/?group_id=11118&atid=211118
@@ -47,6 +47,20 @@
mailing list, where the developers also hang around.
+
+ Please don't sent private support requests to individual Privoxy
+ developers, either use the mailing lists or the support trackers.
+
+
+
+ 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.
+
+
Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
addresses have to be accepted manually by a moderator. This may cause a
@@ -72,30 +86,30 @@
- Configuration issues, such as ads that slip through, or sites that
- don't function properly due to one Privoxy
+ Configuration issues, such as ads that slip through, or sites that
+ don't function properly due to one Privoxy
action
or another being turned on
.
-
+
- Bugs
in the programming code that makes up
+ Bugs
in the programming code that makes up
Privoxy, such as that might cause a crash.
-
+
Reporting Ads or Other Configuration Problems
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
- default.action file, to
+ blocked, sites that don't work properly, and other configuration related problem of
+ default.action file, to
http://sourceforge.net/tracker/?group_id=11118&atid=460288,
the Actions File Tracker.
-
+
New, improved default.action files may occasionally be made
@@ -110,15 +124,15 @@
Reporting Bugs
- Please report all bugs through our bug tracker:
- http://sourceforge.net/tracker/?group_id=11118&atid=111118.
+ Please report all bugs through our bug tracker:
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118.
Before doing so, please make sure that the bug has not already been submitted
and observe the additional hints at the top of the submit
- form. If already submitted, please feel free to add any info to the
+ form. If already submitted, please feel free to add any info to the
original report that might help to solve the issue.
@@ -145,7 +159,7 @@
that your bug still exists.
-Please be sure to provide the following information:
+ Please be sure to provide the following information:
@@ -156,7 +170,7 @@ Please be sure to provide the following information:
(if you got the source from CVS, please also provide the source code revisions
as shown in http://config.privoxy.org/show-version).
-
+
@@ -166,11 +180,11 @@ Please be sure to provide the following information:
sending the output of uname -a
should do,
in case of GNU/Linux, please also name the distribution.
-
+
- The name, platform, and version of the browser
+ The name, platform, and version of the browser
you were using (e.g. Internet Explorer v5.5 for Mac).
@@ -178,9 +192,9 @@ Please be sure to provide the following information:
The URL where the problem occurred, or some way for us to duplicate the
- problem (e.g. http://somesite.example.com/?somethingelse=123).
+ problem (e.g. http://somesite.example.com/?somethingelse=123).
-
+
@@ -188,52 +202,85 @@ Please be sure to provide the following information:
by the Privoxy developers via SourceForge,
or if you got your copy somewhere else.
-
+
- Whether you are using Privoxy in tandem with
+ Whether you are using Privoxy in tandem with
another proxy such as Tor. If so, please
temporary disable the other proxy to see if the symptoms change.
-
+
- Whether you are using a personal firewall product. If so, does
+ Whether you are using a personal firewall product. If so, does
Privoxy work without it?
-
+
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
+ logfile directive
+ is being used and the following debug options are enabled:
+ 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
+ If you are having trouble with a filter, please additionally enable
+ debug 64 # debug regular expression filters
+ If you are using Privoxy 3.0.17 or later and suspect that it interprets the
+ request or the response incorrectly, please enable
+ debug 32768 # log all data read from the network
+ 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.
-
+
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.
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.
+
+
+
+ If you are new to reporting problems, you might be interested in
+ How to Report Bugs Effectively.
The appendix
- of the Privoxy User Manual also has helpful information
- on understanding actions, and action debugging.
+ of the Privoxy User Manual also has helpful information
+ on understanding actions, and action debugging.
@@ -246,10 +293,13 @@ Please be sure to provide the following information:
-Other
+Mailing Lists
-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 Privoxy-related mailing lists,
including list archives, at:
http://sourceforge.net/mail/?group_id=11118.