X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=86c0e33e00ff059f678422c3df6ed22861c9e569;hb=e22a8cad1bac2c28925823b91fa7099a411390e6;hp=3f9bce1c4860c999ade5937bad341e29d10ae8f5;hpb=74a10cc746f6c7fcd460d90202833f684a31d5b4;p=privoxy.git
diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml
index 3f9bce1c..86c0e33e 100644
--- a/doc/source/contacting.sgml
+++ b/doc/source/contacting.sgml
@@ -3,9 +3,9 @@
Purpose : Entity included in other project documents.
- $Id: contacting.sgml,v 2.30 2011/11/19 14:44:01 fabiankeil Exp $
+ $Id: contacting.sgml,v 2.46 2017/01/23 13:03:06 fabiankeil Exp $
- Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2011 Privoxy Developers https://www.privoxy.org/
See LICENSE.
======================================================================
@@ -30,112 +30,15 @@
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
- provide you with the best support:
-
-
-Get Support
-
- For casual users, our
- support forum at SourceForge
- is probably best suited:
- http://sourceforge.net/tracker/?group_id=11118&atid=211118
-
-
-
- All users are of course welcome to discuss their issues on the users
- 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.
+ provide you with the best support.
+Please provide sufficient information
- 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.
+ A lot of support requests don't contain enough information and can't
+ be solved without a lot of back and forth which causes unnecessary
+ delays. Reading this section should help to prevent that.
-
-
- Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
- addresses have to be accepted manually by a moderator. This may cause a
- delay of several days and if you use a subject that doesn't clearly
- mention Privoxy or one of its features, your message may be accidentally
- discarded as spam.
-
-
-
- If you aren't subscribed, you should therefore spend a few seconds
- to come up with a proper subject. Additionally you should make it clear
- that you want to get CC'd. Otherwise some responses will be directed to
- the mailing list only, and you won't see them.
-
-
-
-
-Reporting Problems
-
-Problems
for our purposes, come in two forms:
-
-
-
-
-
- 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
- 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
-
- http://sourceforge.net/tracker/?group_id=11118&atid=460288,
- the Actions File Tracker.
-
-
-
- New, improved default.action files may occasionally be made
- available based on your feedback. These will be announced on the ijbswa-announce
- list and available from our the files section of
- our project page.
-
-
-
-
-Reporting Bugs
-
- 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
- original report that might help to solve the issue.
-
-
Before contacting us to report a problem, please try to verify that it is a
Privoxy problem, and not a browser or site problem
@@ -155,7 +58,7 @@
If you aren't using the latest Privoxy version, the problem may have been found
and fixed in the meantime. We would appreciate if you could take the time
- to upgrade
+ to upgrade
to the latest version and verify that the problem still exists.
@@ -167,19 +70,15 @@
- The exact Privoxy version you are using
- (if you got the source from CVS, please also provide the source code revisions
- as shown in http://config.privoxy.org/show-version).
+ The exact Privoxy version you are using.
The operating system and versions you run
- Privoxy on, (e.g. Windows
- XP SP2), if you are using a Unix flavor,
- sending the output of uname -a
should do,
- in case of GNU/Linux, please also name the distribution.
+ Privoxy on, e.g. Windows
+ XP SP2.
@@ -207,7 +106,7 @@
- Whether you are using Privoxy in tandem with
+ Whether you are using Privoxy together with
another proxy such as Tor. If so, please
temporary disable the other proxy to see if the symptoms change.
@@ -238,14 +137,16 @@ 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 8192 # Non-fatal errors
+debug 65536 # Log applying actions
+
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
+ If you suspect that Privoxy interprets the request or the response
+ incorrectly, please enable
debug 32768 # log all data read from the network
+
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
@@ -289,18 +190,110 @@ debug 8192 # Non-fatal errors
- The appendix
+ The appendix
of the Privoxy User Manual also has helpful information
on understanding actions, and action debugging.
+
+Get Support
+
+ All users are welcome to discuss their issues on the users
+ mailing list, where the developers also hang around.
+
+
+
+ Please don't send 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
+ delay of several days and if you use a subject that doesn't clearly
+ mention Privoxy or one of its features, your message may be accidentally
+ discarded as spam.
+
+
+
+ If you aren't subscribed, you should therefore spend a few seconds
+ to come up with a proper subject. Additionally you should make it clear
+ that you want to get CC'd. Otherwise some responses will be directed to
+ the mailing list only, and you won't see them.
+
+
+
+
+Reporting Problems
+
+Problems
for our purposes, come in two forms:
+
+
+
+
+
+ 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
+ Privoxy, such as that might cause a crash.
+ Documentation issues, for example spelling errors and unclear descriptions,
+ are bugs, too.
+
+
+
+
+
+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
+
+ https://sourceforge.net/tracker/?group_id=11118&atid=460288,
+ the Actions File Tracker.
+
+
+
+
+
+Reporting Bugs
+
+
+ Before reporting bugs, 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
+ original report that might help to solve the issue.
+
-Request New Features
+Reporting security problems
+
+ If you discovered a security problem or merely suspect that a bug might
+ be a security issue, please mail Fabian Keil <fk@fabiankeil.de>
+ (OpenPGP fingerprint: 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C).
+
- You are welcome to submit ideas on new features or other proposals
- for improvement through our feature request tracker at
- http://sourceforge.net/tracker/?atid=361118&group_id=11118.
+ Usually you should get a response within a day, otherwise it's
+ likely that either your mail or the response didn't make it.
+ If that happens, please mail to the developer list to request a
+ status update.
@@ -313,6 +306,20 @@ 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.
+https://lists.privoxy.org/mailman/listinfo.
+The lists hosted on privoxy.org have been created in 2016, the previously-used
+lists hosted at SourceForge are deprecated but the archives may still be useful:
+https://sourceforge.net/mail/?group_id=11118.
+
+SourceForge support trackers
+
+ The
+ SourceForge support trackers
+ may be used as well, but have various technical problems that are unlikely to
+ be fixed anytime soon. If you don't get a timely response, please try the
+ mailing list as well.
+
+
+