place (e.g. the file was probably already uploaded to disk).

of configured upload requirements) and exceed the "max files" settings per dir.
Also, directory operators now always have upload permissions.

of configured upload requirements) and exceed the "max files" settings per dir.

external program listing, sorting, emailing of passwords).

to JavaScript years ago) and only confuse new sysops. They'll still be in the
CVS attic if you really want them, but they're not going to be updated or
supported (use the .js version instead).

Allow for the socket policy service to have a custom section name (for
example [Socket-Policy] instead of the previously required [FlashPolicy])

This only works if the default port of 843 is used.  For non-standard ports,
the section must still be named [FlashPolicy]

Also, fix the callsign command to return the LAST match in the FCC database,
not the first.

 37 - P0T NOoDLE (Amiga)
 38 - mO'sOul (Amiga)
 39 - MicroKnight (Amiga)
 40 - Topaz (Amiga)

As a reminder, to select a font, send the sequence "\e[0;40 D" where \e is
ESC and that space IS THERE.

previous commit is actually just the API (oops)

some minor updates

throw exception on missing host or port

names (need newest load/sbbsdefs.js!).
Added more validity checking against supplied "real name" (e.g. must contain
space, cannot begin with space, etc.).
Removed extraneous <p> and </p> tags in new password display (these were
being displayed as plain text).

prompt and the sub is not in the user's new-scan configuration.

Create and include in packet TOREADER.EXT if QWKEsupport is enabled
(MultiMail keys of this file for QWKE support, so without, no QWKE features are
enabled in MultiMail).
Parse TODOOR.EXT if included in REP packets (for adding/dropping subs or
setting/resetting pointers).
Parse To:, From:, and Subject: QWKE kludge lines and use if/when appropriate
(e.g. to defeat QWK 25-char header field limits).
Create To:, From:, and Subject: QWKE kludge lines in QWK/REP packets when
QWKE support is enabled and those fields exceed QWK limits (25 chars).
Also, legacy SyncQNET kludge lines (@VIA, @TZ, etc.) may now exist in the
top of the message body in any order.
Note: current versions of MultiMail do not support "To" fields > 25 chars, even
in QWKE mode (though I have a patch pending) and do not (yet) support
Synchronet HEADERS.DAT file (rendering QWKE kludges unnecessary).
These are major changes in the QWK/REP creation/parsing code, so testing
(especially with QWKE-compliant offline readers) and bug reports are welcome!

That is, if any of the following text.dat entries are set to a blank/emtpy
string (by editing ctrl/text.dat or via run-time script modification), the
question will not be asked of the user allowing greater sysop-customization
of hard-coded processes (e.g. new user application):
ClearUploadQueueQ
ClearDownloadQueueQ
HangUpAfterXferQ
ChatWithGuruInsteadQ
ForwardMailQ
DownloadBatchQ
LogOffQ
DeleteErrorLogQ
ClearErrCounter
DeleteGuruLogQ
AutoTerminalQ
AnsiTerminalQ
ColorTerminalQ
ExAsciiTerminalQ
CallingFromNorthAmericaQ
ReadYourMailNowQ
NScanAllGrpsQ
SScanAllGrpsQ
NewPasswordQ
ContinueQ
EnterYourPhoneNumber
UserInfoCorrectQ
UseExternalEditorQ
DownloadAttachedFileQ
AddSubToNewScanQ (new)
RemoveFromNewScanQ
DisplaySubjectsOnlyQ
Post
SearchExtendedQ
ViewSysInfoFileQ
ViewLogonMsgQ
WithLineNumbersQ

prompt and the sub is not in the user's new-scan configuration.

this is no longer a v2-only field).

field value to be replaced.

which returns a pointer directly to the key value (no copy).
Most of the iniGet* functions now perform no unnecessary copying of key values.

with OS X doesn't cover the "extended ASCII" from CP437 correctly, so it looks
terrible.

Still want to test this with a handful of X11 based systems to see how well
it deals with CN instead of TNR.

HTML 4.01 Strict valid.

Updated help text/codes.
Eliminated unused "swap" option.