1 | |
---|
2 | ; $Id: ReleaseTool.tmp 1602 2011-08-05 10:59:35Z jbs $ |
---|
3 | |
---|
4 | ; Change log: |
---|
5 | ; 11-07-23 JBS Initial version (replaces obsolete ReleaseTool.CFG |
---|
6 | ; in the repository.) |
---|
7 | ; 11-88-05 JBS - Added comp.os.os2.announce and submit@os2voice.org |
---|
8 | ; to proposed list of addressees |
---|
9 | ; - Updated the documentation |
---|
10 | |
---|
11 | ; This file is a sample of a file used by ReleaseTool to provide |
---|
12 | ; various configuration data to ReleaseTool.cmd (RT). |
---|
13 | |
---|
14 | ; The actual file used by RT is named ReleaseTool.cfg. This file |
---|
15 | ; can be editted and saved with that file name. |
---|
16 | |
---|
17 | ; This file contains extensive comments explaining the possible |
---|
18 | ; configurations that can be made. |
---|
19 | |
---|
20 | ; SYNTAX: ReleaseTool expects each line to be one of four types: |
---|
21 | ; 1) Blank/empty lines (which are ignored) |
---|
22 | |
---|
23 | ; 2) Comment lines. All text following a semicolon, ";", will be ignored. |
---|
24 | ; Any line whose first non-blank is a semicolon, like this line, is |
---|
25 | ; a comment line and will be ignored by ReleaseTool. |
---|
26 | |
---|
27 | ; Section and data lines (below) can have end-of-line comments like |
---|
28 | ; C++'s // comments EXCEPT that only the LAST semicolon on a data line |
---|
29 | ; is considered the start of a comment. Any other semicolons on a data |
---|
30 | ; line are considered part of the key_value. |
---|
31 | |
---|
32 | ; 3) Section lines. Section lines are of the form: |
---|
33 | ; [section-name] |
---|
34 | ; Section lines mark the start of a new set of data. The section |
---|
35 | ; name (within the brackets) defines which type of data follows. |
---|
36 | |
---|
37 | ; Details for each section recognized by RT follow. |
---|
38 | |
---|
39 | ; 4) Data lines. These lines provide the actual data to ReleaseTool. |
---|
40 | ; The format of these lines is: |
---|
41 | ; key-name = key-value |
---|
42 | |
---|
43 | ; Leading and trailing whitespace are ignored. |
---|
44 | |
---|
45 | ; Key-name's are case-insensitive. Key-values are case sensitive. |
---|
46 | |
---|
47 | ; Within a section, data lines can be in any order except that DIRECTORY lines, |
---|
48 | ; if any, must precede the FILE lines to which they apply. |
---|
49 | |
---|
50 | ; Details for each data line recognized by RT follow. |
---|
51 | |
---|
52 | |
---|
53 | ; SECTIONS : RT currently supports section names: FTP, NNTP and SMTP. |
---|
54 | ; FTP |
---|
55 | ; FTP sections are used to define data for uploading one or more files. |
---|
56 | ; If the internal REXX FTP code is used (instead of COMMAND's), then |
---|
57 | ; an FTP section will be required for each FTP server. |
---|
58 | ; NNTP |
---|
59 | ; NNTP sections are used to define data for uploading messages to one |
---|
60 | ; or more newsgroups on a single newsgroup server. Since the |
---|
61 | ; eComstation newsgroups are available only at news.ecomstation.com |
---|
62 | ; and since news.ecomstation.com does not offer other newsgroups |
---|
63 | ; (comp.os.os2.*, for example), more than one NNTP section will |
---|
64 | ; ususally be required. |
---|
65 | ; SMTP |
---|
66 | ; SMTP sections are used to define data for sending email messages |
---|
67 | ; through a single email server. Use multiple SMTP sections if: |
---|
68 | ; - You need to use different "From" addresses (perhaps because you |
---|
69 | ; are registered to different lists under different ids |
---|
70 | ; - You want diffferent lists of "To" addressees. Perhaps you |
---|
71 | ; want to send individually addressed emails to particular |
---|
72 | ; individfuals/lists. |
---|
73 | ; NOTE: Only the first SMTP section is used to send... |
---|
74 | ; - The email requesting commtted work (Task #1) |
---|
75 | ; - The email to Netlabs requesting that the uploaded file be moved (Task #18) |
---|
76 | ; For these two tasks the addressees, "To", are hard-coded in RT. (IOW, the "To" |
---|
77 | ; setting in the CFG file is not used for these two tasks. |
---|
78 | |
---|
79 | ; All SMTP sections are used when sending announcement emails. So the "To" setting |
---|
80 | ; for each section should be a list of addressees who should get an announcemnt using |
---|
81 | ; the settings for that section. |
---|
82 | |
---|
83 | ; DATA LINES |
---|
84 | |
---|
85 | ; The following table lists the key-names recognized by ReleaseTool, the |
---|
86 | ; sections to which they apply, a code (explained below) and a short description: |
---|
87 | |
---|
88 | ; Key-name Sections Codes Description |
---|
89 | |
---|
90 | ; DESCRIPTION FTP,NNTP,SMTP N N Text used by ReleaseTool to identify to the user the |
---|
91 | ; section currently "in use" while RT runs. |
---|
92 | ; COMMAND FTP,NNTP,SMTP N N An external command to run to perform the task. |
---|
93 | ; (See COMMAND notes below!) |
---|
94 | ; HOST FTP,NNTP,SMTP Y N The host name of the FTP/NNTP/SMTP server |
---|
95 | ; PORT FTP,NNTP,SMTP N N Port number. If not set, standard defaults are used. |
---|
96 | ; USERID FTP,NNTP,SMTP Y N The userid used to log in |
---|
97 | ; PASSWORD FTP,NNTP,SMTP Y N The password used to log in. |
---|
98 | ; TO NNTP,SMTP Y N NNTP: Comma-separated list of newsgroups |
---|
99 | ; SMTP: Comma-separated list of addressees (email address(es)) |
---|
100 | ; FROM NNTP,SMTP Y N "From" email address |
---|
101 | ; SIGNATURE NNTP,SMTP N Y Zero or more lines of "signature" |
---|
102 | ; UTCOFFSET SMTP N N Offset from UTC/GMT (e.g. for EST, UTCOFFSET is -0500 |
---|
103 | ; (05 hours, 00 minutes before UTC) |
---|
104 | ; DIRECTORY FTP N Y If a change directory command is needed before uploading |
---|
105 | ; a file, then this key-value should be provided. If more |
---|
106 | ; than one file is to be uploaded and they are to be uploaded |
---|
107 | ; into different directories, precede each set of FILE lines |
---|
108 | ; by an appropriate Directory line. |
---|
109 | ; FILE FTP N Y The local name of a file to be uploaded. This should include |
---|
110 | ; path info if the file is not in the same directory as RT. |
---|
111 | |
---|
112 | ; Codes: |
---|
113 | ; First code : This data can be set in the CFG file and optionally reset while RT runs. |
---|
114 | ; Second code : Multiple lines of this data can be set within each section. |
---|
115 | |
---|
116 | ; "Special" key-values: |
---|
117 | ; PASSWORD |
---|
118 | ; [Hobbes-email] : RT automatically replaces this with the email address from the Hobbes text file. |
---|
119 | ; FILE |
---|
120 | ; [Release-Zip] : RT automatically replaces this with FM/2 release zip filename. |
---|
121 | ; [Hobbes-text] : RT automatically replaces this with Hobbes text filename. |
---|
122 | ; [Release-Zip] and [Hobbes-text] can also be used as part of a COMMAND key_value |
---|
123 | |
---|
124 | ; COMMAND notes: |
---|
125 | ; - If no COMMAND is provided, RT will use internal code to perform the task. |
---|
126 | ; - If a COMMAND is provided, all other keys for that section are optional. |
---|
127 | ; - If multiple external commands are needed to perform a task, then either |
---|
128 | ; - roll them into a CMD file and use COMMAND = call <cmdfile> <parameters> |
---|
129 | ; - use "&&" to separate multiple commands run from a single command line. For example: |
---|
130 | ; COMMAND = copy a b && copy c d |
---|
131 | ; - COMMAND key values may include certain "macros". The syntax for these |
---|
132 | ; macros is: ##macroname##. The macros recognized by RT are: |
---|
133 | ; HOST, PORT, USERID, PASSWORD, TO, FROM, SUBJECT, UTCOFFSET and MESSAGE_BODY_FILE |
---|
134 | ; With the exception of MESSAGE_BODY_FILE, the value for the macro comes from |
---|
135 | ; the correspondingly-named key. MESSAGE_BODY_FILE, on the other hand, is replaced |
---|
136 | ; with the name of a temporary file which is built by RT and holds all the text |
---|
137 | ; of the message to be sent. |
---|
138 | ; - NOTE: Not all keys currently have corresponding macros! |
---|
139 | ; - NOTE: RT recognizes these macros only when they are relevant. For example, |
---|
140 | ; TO is not relevant to FTP transfers so ##TO## would be ignored in an FTP COMMAND. |
---|
141 | ; - NOTE: If macros are used, make sure the corresponding keys have values, via the CFG file |
---|
142 | ; or during execution of RT. RT does not check that each macro has a setting. |
---|
143 | ; - NOTE: If macros are used, keep in mind that their values will become part of a |
---|
144 | ; commandline command. So certain characters may cause problems: " > < / - ^ & | |
---|
145 | |
---|
146 | ; PASSWORD note: Instead of recording passwords in this file, you may prefer to provide them as RT runs. |
---|
147 | |
---|
148 | ; TO/FROM note: Accepted email address formats: |
---|
149 | ; "Full name" <user@domain.net> |
---|
150 | ; <user@domain.net> |
---|
151 | ; user@domain.net |
---|
152 | ; If you plan to use the ##TO## or ##FROM## macros, then probably the third form would be the wisest choice |
---|
153 | ; because the other two forms have characters which can cause problems when used on a command line. |
---|
154 | |
---|
155 | ; FROM note: For newsgroups you may want to use a disguised/false email address to avoid spam. |
---|
156 | |
---|
157 | |
---|
158 | ;[FTP] |
---|
159 | ;Description = Netlabs |
---|
160 | ;Host = 127.0.0.1 |
---|
161 | ;Userid = jsmallt9 |
---|
162 | ;Password = table9 |
---|
163 | ;Directory = /incoming/fm2 |
---|
164 | ;File = [Release-zip] |
---|
165 | |
---|
166 | [FTP] |
---|
167 | Description = Netlabs |
---|
168 | Host = ftp.netlabs.org |
---|
169 | Userid = anonymous |
---|
170 | Password = jsmall@os2world.net |
---|
171 | Directory = /incoming/fm2 |
---|
172 | File = [Release-zip] |
---|
173 | |
---|
174 | [FTP] |
---|
175 | Description = Hobbes |
---|
176 | Host = hobbes.nmsu.edu |
---|
177 | Userid = anonymous |
---|
178 | Password = jsmall@os2world.net |
---|
179 | Directory = /pub/incoming |
---|
180 | ;File = [Hobbes-text] |
---|
181 | File = [Release-zip] |
---|
182 | |
---|
183 | ;[NNTP] |
---|
184 | ;Description = Newsgroup announcement(s) via eComstation news server |
---|
185 | ;Host = news.ecomstation.nl |
---|
186 | ;Userid = |
---|
187 | ;Password = |
---|
188 | ;To = ecomstation.apps |
---|
189 | ;From = zjsmallz@os2world.net |
---|
190 | ;Signature = John Small |
---|
191 | ;Signature = FM/2 Development Team |
---|
192 | ;Signature = (Remove z's for address) |
---|
193 | |
---|
194 | [NNTP] |
---|
195 | Description = Newsgroup announcement(s) via non-eComstation (i.e. "other") news server |
---|
196 | Host = news.eternal-september.org ; ISP's or free news server |
---|
197 | Userid = |
---|
198 | Password = |
---|
199 | ;To = comp.os.os2.apps,comp.os.os2.utilities,comp.os.os2.announce |
---|
200 | To = alt.test.test |
---|
201 | From = "John Small" <zjsmallz@os2world.net> |
---|
202 | Signature = John Small |
---|
203 | Signature = FM/2 Development Team |
---|
204 | Signature = (Remove z's for address) |
---|
205 | |
---|
206 | [SMTP] |
---|
207 | ;Command = G:\pmmail\bin\pmmsend -a G:\PMMail\Accounts\ygk_us0.act -t "##USERTD##" -s "##SUBJECT##" -m ##MESSAGE_BODY_FILE## |
---|
208 | ;Command = call d:\utils\internet\rexxmail\rexxmail /NewMessageSend "##USERTD## ?subject=##SUBJECT## &body=##MESSAGE_BODY_FILE##" /Address=##FROM## /SMTPServer=##SERVER## /SMTPUSER=##USERID## /SMTPPASSWORD=##PASSWORD## /TimeZone=##UTCOFFSET## |
---|
209 | Host = mail.jaread.net |
---|
210 | Port = 587 |
---|
211 | Userid = |
---|
212 | Password = |
---|
213 | ;To = FM/2 Developers <fm2-dev@netlabs.org>,FM/2 Users <fm2-user@netlabs.org>,submit@os2voice.org ; <== Add other users/lists (separated by commas) as appropriate |
---|
214 | To = "John Small" <jsmall@os2world.net>,"John Small2" <jsmall@jaread.net> ; <== Add other users/lists (separated by commas) as appropriate |
---|
215 | From = "FM/2 Development Team" <jsmall@os2world.net> |
---|
216 | Signature = FM/2 Development Team |
---|
217 | UTCOffset = -0500 |
---|