From 8fdd9ba132c25b88ec8579a45608d2090c0923f9 Mon Sep 17 00:00:00 2001 From: teastep Date: Thu, 1 Feb 2007 18:14:40 +0000 Subject: [PATCH] Prune the support doc git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5341 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- docs/support.xml | 60 +++++++++++------------------------------------- 1 file changed, 13 insertions(+), 47 deletions(-) diff --git a/docs/support.xml b/docs/support.xml index 506ff7cee..725dbbe4d 100644 --- a/docs/support.xml +++ b/docs/support.xml @@ -333,9 +333,7 @@ State:Stopped (Thu Mar 30 14:08:11 PDT 2006) Do you see any Shorewall messages (/sbin/shorewall show log) 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). + message(s) in your post. @@ -360,60 +358,28 @@ State:Stopped (Thu Mar 30 14:08:11 PDT 2006) -
- When using the mailing list, please post in plain text - - 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 for continuous abuse because it has been my - policy to allow HTML in list posts!! - - 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 These e-mail admin's need to get a - (expletive deleted) life instead of trying to rid the planet of HTML based - e-mail. 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. -
-
Where to Send your Problem Report or to Ask for Help - IF YOU HAVEN'T READ THE PROBLEM REPORTING GUIDELINES ABOVE, PLEASE - READ THEM NOW — IF YOU DON'T SUPPLY THE INFORMATION WE NEED, IT WILL JUST - DELAY A SOLUTION TO YOUR PROBLEM. + If you haven't read the Problem Reporting Guidelines above, please + read them now — If you don't supply the information that we need, it will + just delay a solution to your problem. If you run the current development release and your question involves a feature that is only available in the development release (see the Shorewall - Release Model page) -- please post your question or problem to the - Shorewall - Development Mailing List. IMPORTANT: You must subscribe to the list before - you will be able to post to it (see link below). + Release Model page) then please post your question or problem to + the Shorewall + Development Mailing List. - 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 - Shorewall users - mailing list. Do not expect to get free MNF support on the - list. - - Otherwise, please post your question or problem to the Otherwise, please post your question or problem report to the Shorewall users mailing - list. IMPORTANT: You must - subscribe to the list before you will be able to post to it (see link - below). + list. - Please read the list usage - instructions (found on the information page for each list) - before posting. + IMPORTANT: You must subscribe to + the mailing lists before you will be able to post to them (see links + below). For quick questions, there is also a #shorewall channel at irc.freenode.net.