Permalink
Browse files

Initial public release.

  • Loading branch information...
Julien-Elie committed May 8, 2007
1 parent 021d421 commit 8c3e751398ccaabbfc45a1f3db65d77a284ef2f0
Showing with 556 additions and 0 deletions.
  1. +89 −0 signcontrol.conf
  2. +467 −0 signcontrol.py
View
@@ -0,0 +1,89 @@
# This is the configuration file for "signcontrol.py".
# You need to edit the following variables to fit your needs.
#
# Last version: <http://www.trigofacile.com/divers/usenet/clefs/signcontrol.htm>.
# Please also read: <http://www.eyrie.org/~eagle/faqs/usenet-hier.html>.
# The path to the GPG executable (GnuPG <http://www.gnupg.org/> must be installed).
# It is usually "C:\Progra~1\GNU\GnuPG\gpg.exe" or "/usr/bin/gpg".
#PROGRAM_GPG = "/usr/bin/gpg"
PROGRAM_GPG = "C:\Progra~1\GNU\GnuPG\gpg.exe"
# The ID of your PGP key. Note that if you do not already have a key, it can
# be generated later by this signcontrol.py script.
# It is usually your e-mail.
ID = "control-hierarchy@my.news.server.com"
# The e-mail from which you send your control articles.
MAIL = "control-hierarchy@my.news.server.com"
# The host which appears in the Message-ID of articles generated.
HOST = "my.news.server.com"
# An existing group of your hierarchy (where checkgroups control articles
# will be fed). If an administrative group exists, put it.
ADMIN_GROUP = "my.hierarchy.admin"
# The name which appears in the From: header.
# You should only use ASCII characters. Otherwise, you have
# to MIME-encode it (for instance: "=?ISO-8859-15?Q?Julien_=C9LIE?=").
NAME = "Control"
# The scope of your hierarchy according to USEPRO.
# For instance: "fr" (for fr.*), "de !de.alt" (for de.* excepting de.alt.*)
# or "de.alt" (for de.alt.*).
CHECKGROUPS_SCOPE = "my.hierarchy"
# The URL where your public key is.
# If you do not have any, leave "ftp://ftp.isc.org/pub/pgpcontrol/README".
URL = "ftp://ftp.isc.org/pub/pgpcontrol/README"
# The message which will be written in a newgroup control article for
# a moderated newsgroup. All occurrences of "$GROUP$" will be replaced
# by the name of the newsgroup.
# If you want to use the quote ", you have to escape it as follows: \".
# The default text is:
# NEWGROUP_MESSAGE_MODERATED =
# "The moderated newsgroup $GROUP$ has just been created.
# Please add this group to your news server."
NEWGROUP_MESSAGE_MODERATED =
"The moderated newsgroup $GROUP$ has just been created.
Please add this group to your news server."
# The message which will be written in a newgroup control article for
# an unmoderated newsgroup. All occurrences of "$GROUP$" will be replaced
# by the name of the newsgroup.
# If you want to use the quote ", you have to escape it as follows: \".
# The default text is:
# NEWGROUP_MESSAGE_UNMODERATED =
# "The unmoderated newsgroup $GROUP$ has just been created.
# Please add this group to your news server."
NEWGROUP_MESSAGE_UNMODERATED =
"The unmoderated newsgroup $GROUP$ has just been created.
Please add this group to your news server."
# The message which will be written in a rmgroup control article.
# All occurrences of "$GROUP$" will be replaced by the name of the newsgroup.
# If you want to use the quote ", you have to escape it as follows: \".
# The default text is:
# RMGROUP_MESSAGE =
# "The newsgroup $GROUP$ is now defunct.
# Please remove this group from your news server."
RMGROUP_MESSAGE =
"The newsgroup $GROUP$ is now defunct.
Please remove this group from your news server."
# Whether your hierarchy is public or private. If it is private
# (that is to say if it is intended to remain in a local server
# with private access and if it is not fed to other Usenet news servers),
# the value should be True, so that checkgroups control articles
# are not fed to news.admin.hierarchies.
# Possible values: True or False (default: False).
PRIVATE_HIERARCHY = False
# The file which contains the current checkgroups.
CHECKGROUPS_FILE = "checkgroups.txt"
# The encoding of the article generated by your system.
# The default value is 'ISO-8859-1'.
ENCODING = "ISO-8859-1"
Oops, something went wrong.

0 comments on commit 8c3e751

Please sign in to comment.