- <p>
- 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.
- </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. 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>
- If you are new to reporting problems, you might be interested in <a
- href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
- target="_top">How to Report Bugs Effectively</a>.
- </p>
- <p>
- The <a href=
- "https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
- target="_top">appendix of the Privoxy User Manual</a> also has
- helpful information on understanding <tt class=
- "LITERAL">actions</tt>, and <tt class="LITERAL">action</tt>
- debugging.
- </p>
- </div>
- <div class="SECT2">
- <h2 class="SECT2">
- <a name="CONTACT-SUPPORT">11.2. Get Support</a>
- </h2>
- <p>
- All users are welcome to discuss their issues on the <a href=
- "https://lists.privoxy.org/mailman/listinfo/privoxy-users" target=
- "_top">users mailing list</a>, where the developers also hang
- around.
- </p>
- <p>
- Please don't send private support requests to individual Privoxy
- developers, either use the mailing lists or the support trackers.
- </p>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
- </div>
- <div class="SECT2">
- <h2 class="SECT2">
- <a name="REPORTING">11.3. Reporting Problems</a>
- </h2>
- <p>
- <span class="QUOTE">"Problems"</span> for our purposes, come in two
- forms:
- </p>
- <ul>
- <li>
- <p>
- Configuration issues, such as ads that slip through, or sites
- that don't function properly due to one <span class=
- "APPLICATION">Privoxy</span> <span class=
- "QUOTE">"action"</span> or another being turned <span class=
- "QUOTE">"on"</span>.
- </p>
- </li>
- <li>
- <p>
- <span class="QUOTE">"Bugs"</span> in the programming code that
- makes up <span class="APPLICATION">Privoxy</span>, such as that
- might cause a crash. Documentation issues, for example spelling
- errors and unclear descriptions, are bugs, too.
- </p>
- </li>
- </ul>
- <div class="SECT3">
- <h3 class="SECT3">
- <a name="CONTACT-ADS">11.3.1. Reporting Ads or Other
- Configuration Problems</a>
- </h3>
- <p>
- 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 <tt class=
- "FILENAME">default.action</tt> file, to <a href=
- "https://sourceforge.net/tracker/?group_id=11118&atid=460288"
- target=
- "_top">https://sourceforge.net/tracker/?group_id=11118&atid=460288</a>,
- the Actions File Tracker.
- </p>
- </div>
- <div class="SECT3">
- <h3 class="SECT3">
- <a name="CONTACT-BUGS">11.3.2. Reporting Bugs</a>
- </h3>
- <p>
- Before reporting bugs, please make sure that the bug has <span
- class="emphasis"><i class="EMPHASIS">not already been
- submitted</i></span> and observe the additional hints at the top
- of the <a href=
- "https://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
- target="_top">submit form</a>. If already submitted, please feel
- free to add any info to the original report that might help to
- solve the issue.
- </p>
- </div>
- </div>
- <div class="SECT2">
- <h2 class="SECT2">
- <a name="SECURITY-CONTACT">11.4. Reporting security problems</a>
- </h2>
- <p>
- 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).
- </p>
- <p>
- 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.
- </p>
- </div>
- <div class="SECT2">
- <h2 class="SECT2">
- <a name="MAILING-LISTS">11.5. Mailing Lists</a>
- </h2>
- <p>
- 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 <span class=
- "APPLICATION">Privoxy</span>-related mailing lists, including list
- archives, at: <a href="https://lists.privoxy.org/mailman/listinfo"
- target="_top">https://lists.privoxy.org/mailman/listinfo</a>. 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: <a href=
- "https://sourceforge.net/mail/?group_id=11118" target=
- "_top">https://sourceforge.net/mail/?group_id=11118</a>.
- </p>
+ debug 4096 # Startup banner and warnings.<br>
+ debug 8192 # Non-fatal errors<br>
+ debug 65536 # Log applying actions</p>
+ <p>If you are having trouble with a filter, please additionally enable</p>
+ <p class="LITERALLAYOUT">
+ debug 64 # debug regular expression filters</p>
+ <p>If you suspect that Privoxy interprets the request or the response incorrectly, please enable</p>
+ <p class="LITERALLAYOUT">
+ debug 32768 # log all data read from the network</p>
+ <p>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.</p>
+ <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>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.</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.
+ 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="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT" target="_top">appendix of the
+ Privoxy User Manual</a> also has helpful information on understanding <tt class="LITERAL">actions</tt>, and
+ <tt class="LITERAL">action</tt> debugging.</p>
+ </div>
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="CONTACT-SUPPORT" id="CONTACT-SUPPORT">11.2. Get Support</a></h2>
+ <p>All users are welcome to discuss their issues on the <a href=
+ "https://lists.privoxy.org/mailman/listinfo/privoxy-users" target="_top">users mailing list</a>, where the
+ developers also hang around.</p>
+ <p>Please don't send private support requests to individual Privoxy developers, either use the mailing lists or
+ the support trackers.</p>
+ <p>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.</p>
+ <p>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.</p>
+ <p>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.</p>
+ </div>
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="REPORTING" id="REPORTING">11.3. Reporting Problems</a></h2>
+ <p><span class="QUOTE">"Problems"</span> for our purposes, come in two forms:</p>
+ <ul>
+ <li>
+ <p>Configuration issues, such as ads that slip through, or sites that don't function properly due to one
+ <span class="APPLICATION">Privoxy</span> <span class="QUOTE">"action"</span> or another being turned
+ <span class="QUOTE">"on"</span>.</p>
+ </li>
+ <li>
+ <p><span class="QUOTE">"Bugs"</span> in the programming code that makes up <span class=
+ "APPLICATION">Privoxy</span>, such as that might cause a crash. Documentation issues, for example spelling
+ errors and unclear descriptions, are bugs, too.</p>
+ </li>
+ </ul>
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="CONTACT-ADS" id="CONTACT-ADS">11.3.1. Reporting Ads or Other Configuration
+ Problems</a></h3>
+ <p>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 <tt class="FILENAME">default.action</tt> file, to <a href=
+ "https://sourceforge.net/p/ijbswa/actionsfile-feedback/" target=
+ "_top">https://sourceforge.net/p/ijbswa/actionsfile-feedback/</a>, the Actions File Tracker.</p>