1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>FORMAT of EPURMESS.INI</title>
</head>
<body background="/back_fbb.jpg">
<h1 align="Center"> EPURMESS.INI </h1>
<p> </p>
<pre>
<big><b>EPURMESS.INI (\FBB).</b></big>
This file is also in the main FBB-directory. This is the file that controls
the lifetime of messages. Each night EPURMESS will be activated at the time
specified in <a href="fmtinit.htm">INIT.SRV</a>. Normally you will not need to change this, but if you<br>did any changes during installation, you must also change the same pathnames <br>here. That goes for all lines that include a pathname.<br><br> Next, you decide if you want to save "killed" messages in the OLDMAIL-<br>directory. If you do, write a 1 first, if you want to save old personal<br>messages, and another 1 if you want to save old bulletins.<br><br> # Personal Bulletins (0=kill 1=archive in oldmail)<br> 0 0<br> #<br><br> Next we have the actual parametres (in days) for the lifetimes of bulletins<br>and personal messages. Let me just explain the letters in use here:<br> P=Personal message<br> B=Bulletin<br> N=Not read<br> Y=Had been read<br> F=Forwarded (forwarded to all BBSs that should receive this msg)<br> X=Expired (still readable, but will not be forwarded to other BBSs)<br> K=Killed (readable only by sysop)<br> A=Archived (same as killed, but will be deleted at once, or moved to<br> OLDMAIL)<br><br> I think this is self-explanatory:<br><br> # Parametres in days:<br> #<br> # PARAMETRES FOR PERSONAL MESSAGES:<br> #<br> # PN -> PX (days after message is written)<br> 30<br> #<br> # PY -> PX (days after changed to Y)<br> 7<br> #<br> # PF -> PK (days after changed to F)<br> 7<br> #<br> # PX -> PK (days after changed to X)<br> 0<br> #<br> # PK -> PA (days after changed to K)<br> 0<br> #<br> # PARAMETRES FOR BULLETINS<br> #<br> # BN -> BX (days after the message is written)<br> 7<br> #<br> # B$ -> BX (days after the message is written)<br> 7<br> #<br> # BY -> BX (days after changed to Y)<br> 7<br> #<br> # BX -> BK (days after changed to X)<br> 14<br> #<br> # BF -> BX (days after message is written)<br> 14<br> #<br> # BK -> BA (days after changed to K)<br> 0<br> #<br>#<br># Automatic generated return-messages for non-forwarded messages.<br># Each line may be max 255 characters long. Disable with only an 0.<br>#<br># Timeout for valid forward-path (number of days + text, end with $W)<br>21 This message could not be forwarded, due to bad link.$W<br>#<br># Unknown routing or wrong H-address (number of days + text, end with $W)<br>2 This message could not be forwarded, due to bad callsign or bad route.$W<br>#<br># Max number of lines in a returned message:<br>10<br>#<br>------<br>#<br># At the end of the file, you can have special lifetimes for special messages.<br># In the example below, messages that are TO LA6CU will be 365 days old,<br># messages FROM system will be 0 days, messages @LA will be 365 days. I have an<br># # in front of them, this means they are disabled right now.<br># List of lifetime-tests<br>#<br># To/from/via Callsign Days<br>@ VEST 365<br>@ LA 365<br>> LA6CU 365<br>< system 0<br>#<br># End of this file.<br>#<br><br><br>
<font color="#800000">This page was last updated 17-Apr-99</font>
</pre>
</body>
</html>
|
