Where to get support - DansGuardian mailing list
Information
Latest News
What is DansGuardian?
Smoothwall
Screen Shots
Search this Site
How I did it
How to Remove it

Download
DansGuardian
Blacklists
Squid

Support
Contact
Mailing List
Wiki
Docs & HOWTO
Known Bugs

Buying
Copyright
Support
Pricing
Buying with PayPal
Gifts/Merchandise

Links
Squid
DG SourceForge
DG Freshmeat
Rate DG
Mirrors


Smoothwall; trusted in organizations worldwide

In Association with Amazon.com

DansGuardian wins 'Highly Commended' award

Monitored by Pingdom
There are two mailing lists: You are able to post to the Support list but only a few people are able to post to the Announce list. When there is a new version of DansGuardian or other important announcement it will get posted to both lists so there is no need to subscribe to both. The volume of messaged on the Announce list is low.

You can get these lists are an RSS feed too! See:
http://groups.yahoo.com/group/dansguardian/rss - Support List
http://groups.yahoo.com/group/DansguardianAnnounce/rss - Announce List

You can subscribe using the links above or the forms below:

Want support? - subscribe to DansGuardian mailing list

Keep informed of developments first - subscribe to DansGuardianAnnounce mailing list

To Unsubscribe

Send a mail from the email address you want to unsubscribe from to: dansguardian-unsubscribe@yahoogroups.com or DansguardianAnnounce-unsubscribe@yahoogroups.com depending on which list you want to unsubscribe from.

Mailing List Rules and Guidelines

Last updated Tue 30th December 2003.

  • Post in plain text only
  • Always put your reply text after the text you are quoting. Remember that the purpose of quoted text is to provide a context for your reply - if your reply comes first, forcing the reader to look further down the message for what you are replying to, the purpose of quoting (to make things easier for the reader) has been defeated.
  • Trim the quoted text so that there is sufficient context for your reply, but not masses of extraneous text that do not have anything to do with what you want to say.
  • Never quote signatures.
  • It is generally a good idea to use a standard > character for quoting as some news readers can then automatically highlight quoted text.
  • Include a proper attribution line before a quote. An attribution line looks like:
    On <uk.foo> in <m-1234@oenone.demon.co.uk> on Fri, 11 Sep 1998 15:15:51 +0100, "Alex D. Baxter" <alex-faq@oenone.demon.co.uk> wrote:
    Most news readers include an attribution line by default when you quote a message. The content of the attribution line varies; it should contain at least the name/e-mail address of the person you are quoting.
  • If you are quoting a message that itself contains quotes, do not remove the quoting characters or attribution lines from the sections that you are quoting.
Remember these guidelines have been around long before you even sent a single email. They are a simple logical set of rules that makes email better for everyone. You would not go to another culture and expect them to change to your foreign culture would you?

Mailing List Rules and Guidelines - Posting in Plain Text

Originally from http://www.usenet.org.uk/ukpost.html.

Why post in plain text?

Currently there are several email clients which are able to send in formats other than plain text, such as HTML; some can send emails in a dual format with a plain text part and then the text in another format. While this means that articles look attractive when read with a compatible email program, remember that not everybody is using the same email program as you. Many users will not be able to or even want to read emails in HTML. Mailing list postings in HTML or combined format articles are much longer than plain text articles and so are taking up extra bandwidth for the same content.

For these reasons, posting in HTML or any format other than plain text is banned on these mailing lists. Following are step-by-step instructions for configuring a common mail client (Outlook) to post in plain text only.

  1. Choose 'Tools->Options' from the menu.
  2. Choose the 'Send' tab.
  3. Choose the 'Plain Text' radio button under 'Mail Sending Format'.
  4. Click the OK button.

Mailing List Rules and Guidelines - Proper Quoting

Originally from http://www.uwasa.fi/~ts/http/quote.html.

Besides the actual content, of course, proper formatting of your email can significantly enhance the effectiveness and credibility of your postings. Let's consider the issue of proper quoting of the postings you are responding to. I am sure that you have seen text quoted innumerable times in the following manner:

> This is quoted text

The number one rule of quoting is quote judiciously. Quote only what is essential to make it possible for the reader to understand what your posting or email message is about. As a rule avoid quoting an entire message (signatures and all). It is not judicious to quote, say, a hundred lines of discussion just to input a single line of one's own. Proper quoting is a skill. If you are going to quote, devote some time to working the quote appropriately. Don't be lazy in this respect.

A further tip adapted from Mark Rogers. Leave a blank line after the quoted text before you insert your own because else your text and the quoted text will difficult to distinguish from each other.


Where is the best place to put quoted text? Above or below my comments?

   From an unknown origin:
     A: Top posters.
     Q: What is the most annoying thing on the Internet?
 
Above! Some more recent standard email programs have assumed a very problematic feature. They include the message which you are responding to below your message. Don't allow that to happen. The proper order is
 
      > Quote 1 (properly pruned)

      Your response 1

      > Quote 2 (properly pruned)

      Your response 2

In other words

  • Put each, appropriately trimmed item that you choose to quote before each of your own comments, respectively.
     
  • Remove any remaining "postquoting". Let me emphasize. Do not leave the entire earlier posting, which you have been responding to, at the end of your own posting.
Some (often obscure) mailing lists and Microsoft's own newsgroups (hardly surprising!) may show and have developed different preferences and practices as to the order and extent of quoting. This definitely is not what to go by in general. Also, one of the arguments that has been posed in favour of the excessive quoting is that threads may be broken and full quoting is therefore imperative to be able to follow what is going on. No, that is what the archive is for. Besides, in well-planned quoting it is amply sufficient to give the essence. Concise and at the same time informative quoting indeed is a skill to be practiced.

Of course it is fair to ask why

      > Quote 1 (properly pruned)
      Your response 1
      > Quote 2 (properly pruned)
      Your response 2

is better than

      Your entire response

      > All old quoted

Email and Usenet news are typically used for modern, often almost real-time exchanges which can closely resemble a verbal discussion rather than a correspondence by snailmail where the time between the letters is days or weeks. In a good discussion one interacts, rather than keeps up separate monologues. Thus it is very natural to quote a point, respond, quote the second point, respond and so forth.

Adapted from an advisory posting by Bob Gootee: Answering above the the original message is called top posting. Sometimes also called the Jeopardy style. Email and mailing lists are Q & A not A & Q. (The name obviously comes from the game of Jeopardy, where the competitor is given the answer before the question.)

A similar point from a posting by Tuomas Venhola: If you start with your answer, it is a bit like telling the punch-line before giving the background.

As for the Microsoft's public newsgroups even there the official policy warns against quoting below your answer and against excessive quoting!

Mailing List Rules and Guidelines - On Topic

The mailing list is for discussion of DansGuardian and related programming, installation, compilation and configuration. It is not, for example, for how to use your particular OS or proxy. Some discussion of squid configuration is on topic but problems not relating to use with DansGuardian is not on topic. Feature requests and pretty much anything DansGuardian related is on topic. You can even discuss use of DansGuardian on firewalls.

Page last modified: 31 July 2005 21:55:54
Smoothwall -- Welcome to a new totally secure way of working.© 2001-2014 Daniel Barron RISC OS Spinner