extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-03-27 07:39:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Prune the support doc

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5341 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-02-01 18:14:40 +00:00
parent 35ae29d576
commit 8fdd9ba132
1 changed files with 13 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

60
docs/support.xml
View File

@ -333,9 +333,7 @@ State:Stopped (Thu Mar 30 14:08:11 PDT 2006)</programlisting>
<para>Do you see any <quote>Shorewall</quote> messages
(<quote><command>/sbin/shorewall show log</command></quote>) when you
exercise the function that is giving you problems? If so, include the
message(s) in your post along with a copy of your
/etc/shorewall/interfaces file (and /etc/shorewall/hosts file if you
have entries in that file).</para>
message(s) in your post.</para>
</listitem>
<listitem>
@ -360,60 +358,28 @@ State:Stopped (Thu Mar 30 14:08:11 PDT 2006)</programlisting>
</itemizedlist>
</section>
<section>
<title>When using the mailing list, please post in plain text</title>
<para>A growing number of MTAs serving list subscribers are rejecting all
HTML traffic. At least one MTA has gone so far as to blacklist
shorewall.net <quote>for continuous abuse</quote> because it has been my
policy to allow HTML in list posts!!</para>
<para>I think that blocking all HTML is a Draconian way to control spam
and that the ultimate losers here are not the spammers but the list
subscribers whose MTAs are bouncing all shorewall.net mail. As one list
subscriber wrote to me privately <quote>These e-mail admin's need to get a
(expletive deleted) life instead of trying to rid the planet of HTML based
e-mail</quote>. Nevertheless, to allow subscribers to receive list posts
as must as possible, I have now configured the list server at
shorewall.net to convert all HTML to plain text. Sometimes the conversion
process fails in which case, the post sent to the list is empty. Even when
conversion succeeds, the converted post is difficult to read so all of us
will appreciate it if you just post in plain text to begin with.</para>
</section>
<section>
<title>Where to Send your Problem Report or to Ask for Help</title>
<para><emphasis role="bold">IF YOU HAVEN'T READ THE <link
linkend="Guidelines">PROBLEM REPORTING GUIDELINES</link> ABOVE, PLEASE
READ THEM NOW — IF YOU DON'T SUPPLY THE INFORMATION WE NEED, IT WILL JUST
DELAY A SOLUTION TO YOUR PROBLEM.</emphasis></para>
<para><emphasis role="bold">If you haven't read the <link
linkend="Guidelines">Problem Reporting Guidelines</link> above, please
read them now — If you don't supply the information that we need, it will
just delay a solution to your problem.</emphasis></para>
<para><emphasis role="bold">If you run the current development release and
your question involves a feature that is only available in the development
release</emphasis> (see the <ulink url="ReleaseModel.html">Shorewall
Release Model page</ulink>) -- please post your question or problem to the
<ulink url="mailto:shorewall-devel@lists.sourceforge.net">Shorewall
Development Mailing List</ulink>. <emphasis
role="bold">IMPORTANT</emphasis>: You must subscribe to the list before
you will be able to post to it (see link below).</para>
Release Model page</ulink>) then please post your question or problem to
the <ulink url="mailto:shorewall-devel@lists.sourceforge.net">Shorewall
Development Mailing List</ulink>. </para>
<para><emphasis role="bold">If you run Shorewall under MandrivaSoft Multi
Network Firewall (MNF) and you have not purchased an MNF license from
MandrivaSoft then you can post non MNF-specific Shorewall questions to the
<ulink url="mailto:shorewall-users@lists.sourceforge.net">Shorewall users
mailing list</ulink>. Do not expect to get free MNF support on the
list</emphasis>.</para>
<para>Otherwise, please post your question or problem to the <ulink
<para>Otherwise, please post your question or problem report to the <ulink
url="mailto:shorewall-users@lists.sourceforge.net">Shorewall users mailing
list</ulink>. <emphasis role="bold">IMPORTANT</emphasis>: You must
subscribe to the list before you will be able to post to it (see link
below).</para>
list</ulink>.</para>
<para>Please <emphasis role="bold">read the list usage
instructions</emphasis> (found on the information page for each list)
before posting.</para>
<para><emphasis role="bold">IMPORTANT</emphasis>: You must subscribe to
the mailing lists before you will be able to post to them (see links
below).</para>
<para>For <emphasis role="bold">quick questions</emphasis>, there is also
a #shorewall channel at irc.freenode.net.</para>