# config file for htnews. version 0.6.7
# for more informations, refer to the README!

#---------------------------------------------
# htnews needs to know, who it is
# option is required!
SENDERsmtp 
#---------------------------------------------


#---------------------------------------------
# who will get error messages
# if blank, the _DEFAULTMAIL specified in htnews.cc 
# will get them, most likely root@localhost
ADMIN 
#---------------------------------------------


#---------------------------------------------
# who will get delivery notifications
# if blank, the originator will get it. 
# If set to /dev/null, no reponse will be sent.
TOsmtp
#---------------------------------------------


#---------------------------------------------
# someone else want to get delivery notifications?
# if blank, no one will get a message
CCsmtp
#---------------------------------------------


#---------------------------------------------
# a file with email adresses of allowed users
# if blank, everybody can use htnews
Allow_From
#---------------------------------------------


#---------------------------------------------
# the authentication code to use
# if blank, no code will be needed
AUTH_CODE 
#---------------------------------------------


#---------------------------------------------
# which template-file to use
# option is required!
TEMPLATE 
#---------------------------------------------


#---------------------------------------------
# where must the output-file go
# option is required!
OUTPUT 
#---------------------------------------------


#---------------------------------------------
# where to store the old news items?
# option is required!
STORE 
#---------------------------------------------


#---------------------------------------------
# Should htnews use the html-part of those
# multiparttext/html mails?
UseHTML YES
#--------------------------------------------- 


#---------------------------------------------
# htnews can "translate \n to <br> and \t to 8 x &nbsp;
# if you want. Set this parameter to "YES" if so.
CRLF NO
#---------------------------------------------


#---------------------------------------------
# Definitions of formatting the item
# something to add before inserting new item?
ITEM_HEAD 

# something to append before inserting new item?
ITEM_FOOT 
#---------------------------------------------


#---------------------------------------------
# Definitions of item fields

# order to show fields
Field1 Date
Field2 From
Field3 Subject
Field4 Text

# Create a mailto link?
Mailto YES

# You may insert html-code before and after every field
Date_HEAD <b>
Date_FOOT </b>

Subject_HEAD <i>
Subject_FOOT </i>

From_HEAD
From_FOOT 

Text_HEAD 
Text_FOOT 
#----------------------------------------------


#----------------------------------------------
# You can protect your site against email adress "sniffer"-like 
# software, that spamers uses. An emailadress will be displayed 
# like this: "user @ foo.bar", so one have to edit in his mailer,
# if he wants to send an email to this adress.
SPAMPROTECT YES
#----------------------------------------------


#----------------------------------------------
# Want to archive old news?
# If blank or set to "NO", all following items will be ignored.
ARCHIV NO

# Where to write the archived output?
Archiv_Output

# Template for archived news, required, if "ARCHIVE" = "YES"
Archiv_Template

# Where should we store old news items?
Archiv_Store 

# How many itmes should be shown on the front page?
Archiv_MAXITEMS 
#----------------------------------------------


#----------------------------------------------
# Define template and output, if you run htnews as a cronjob for
# archieving the old news to a monthly file
Cron_TEMPL

# Where these files should be stored to.
Cron_OUTPATH

# Where should the archiv history be saved to. (a list of Month's)
Cron_Hist

# HTML Code for the link to the monthly page
Cron_HEAD
Cron_FOOT

# Want formatting for the title of a monthly page?
# note, that you need a "<!--title-->" tag in the template!
Archiv_Title_Head
Archiv_Title_Foot
#----------------------------------------------


#----------------------------------------------
# Want a "Detail Link for an item?
LookDetail YES

# The Template to be used for the detail page
Detail_TEMPL

# The path to the output directory containing the detailpages,
# it should be the same which allready contans the other
# output files
Detail_PATH

# How the link should be named, i.e. "click here for more informations..."
# If the value here is "Subject", then the Subject of a message itself
# will be the link to the detail page!
Detail_LINK read more...

# some code for the link?
Detail_HEAD 
Detail_FOOT 
#----------------------------------------------

#----------------------------------------------
# Any questions? Drop me a line: tom@daemon.de
#----------------------------------------------