3k Associates
DeskLink/3000
New features and enhancements in the new version of DeskLink/3000:
(B.06, as of 97/10/20)
----------------------------------------------------------------------
PRESERVING FILENAMES ON ATTACHMENTS
You can now enable DeskLink/HPOpenDesk to preserve the filenames on
files attached to mail messages (i.e. pc style names - myfile.xls; etc.).
To do this, you need a couple things:
1) DeskLink version B.06 with a datecode of October 1997 or later
2) OpenDesk patch OD3017 (from HP)
3) OpenDesk patch OD3022 (from HP)
4) Set the DESKUSEFILENAMES jcw to 1 in the DeskLink job stream
5) Add a !SETJCW FSCCHECKUSERLABEL 1 into the SUPRVISR (HPDesk job)
6) Add a !SETJCW FSCADDUSERLABEL 1 into the TRUCK0.MAILJOB.HPOFFICE job
Once all these are in place, files attached to messages from HPDesk
clients sent to other mail systems will keep the original filename of the
attached file as a label on the outbound message. HPDesk (non-client) users
can also name message attachments by specifying a dos-format filename when
prompted for a "subject" for the attached file in HPDesk. (For example,
"myfile.xls","runme.exe","salesq1.doc".)
Also, messages coming into HPDesk (both clients and terminal users) will
see the original names of files attached to messages.
----------------------------------------------------------------------
ENHANCED DESKLINKVERIFY ADDRESS SEARCHES
If the DESKLINKVERIFY JCW is set to '2' in the DeskLink job, DeskLink
will now use a MUCH QUICKER keyed/chained method to search for HPDesk
mailbox names. (The older method strictly did a serial read of the entire
HPDesk GLOBAL database address list.) Sites with large numbers of HPDesk
users will see VERY LARGE performance improvements in the SMTPSERV process
(which did this verification on each inbound message recipient).
----------------------------------------------------------------------
ERRORLOG FILE OF REFUSED MAIL
Any delivery attempt that fails because the recipient name is invalid,
or the domain is in the refuse (spam) file, causes a message to be written
to the ERRORLOG.NETMAIL.HPOFFICE (for DeskLink users) or ERRORLOG.NETMAIL.
THREEK (for NetMail users) file. The record includes the date/time of the
message, the host it came from, the sender of the message, and a message
describing the problem. Messages are appended to the file (which we
recommend building as a circular file) for a continuous log that can be
printed at any time.
To build this file, log on as MGR.HPOFFICE and
:BUILD errorlog.netmail;rec=-256,,f,ascii;disc=10000;cir
----------------------------------------------------------------------
FULL SUPPORT FOR 8-bit CHARACTER SETS
DeskLink now supports 8-bit character set text in messages. French/
Spanish/Italian/other languages which use the ISO-8859-1 character sets
will now be automatically converted to/from the local HP-Roman8 character
set used on HP terminals and emulators.
----------------------------------------------------------------------
CONFIGURABLE INCLUDED-HEADERS
Sites can now configure which headers they want included in HPDesk
messages (if the "include headers in message" option is set in netmaint).
Included headers are listed in the file "deskhead.data.threek", which
can be easily edited.
----------------------------------------------------------------------
DESKLINKVERIFY JCW
If the DESKLINKVERIFY JCW is set in the DeskLink job, then the
recipient on every incoming message is checked against HPDesk's global
database; invalid recipients are refused (the messages get returned
to the sender instead of ending up in HPDesk's general delivery
mailbox).
----------------------------------------------------------------------
ALIASES.DATA.THREEK
If there is an ALIASES.DATA.THREEK, then any incoming messages to
addresses in the list will be delivered to the redirected addresses
specified in the file.
ALIASES.DATA.THREEK is an ascii file, built with any editor (with
NO line numbers), 72 or 80 bytes wide, containing:
oldaddress@somehost.domain.org:newaddress@anotherhost.domain.org
One entry per line, with as many entries as you like in the file.
----------------------------------------------------------------------
Native Mode Files
As of the B.04 release, all server processes and NetMail/3000's user
interface (netmail.sys.threek) are native mode programs.
----------------------------------------------------------------------
SPAM Refusal file
NetMail/3000, DeskLink, and PopServer/3000 all now can automatically
refuse to accept incoming e-mail from known e-mail "spammers" (or any
other address you specify for that matter). E-mail addresses within the
file "refuse.data.threek", when encountered in incoming mail, cause that
message to be refused (and bounced back to the sender).
----------------------------------------------------------------------
New features and enhancements in the new version of NetMail/3000:
(B.02, as of 95/06/23)
----------------------------------------------------------------------
Enhanced Security
NetMail/3000 now processes an "excludes.data.threek" file for source
IP (Internet) addresses. The new control file allows administrators to
include or exclude any range of IP addresses; excluded addresses will
not be allowed to connect to any (netmail provided) services, and if/
when they try, messages are sent to the console reporting the attempt.
----------------------------------------------------------------------
Enhanced DNS (nameserver) Support
NetMail/3000 (and DeskLink) now will automatically use the same DNS
configuration file that MPE/iX does (reslvcnf.net.sys). By simply leaving
the DNS nameserver field blank (in the global config screen) NetMail/3000
and DeskLink will both use MPE/iX's config file if present.
----------------------------------------------------------------------
New Gopher Server
We now support an optional gopher server product, which is run under
the same background job as NetMail/3000 or DeskLink.
----------------------------------------------------------------------
New Mail Logging and Statistics
NetMail/3000 now keeps a log of all incoming and outgoing messages
that pass through the system. To/From/Subject/#bytes/date&time received/
message-id/and host-received-from are recorded. Also, if a computer name
appears as a KNOWN HOST entry in the database, statistics for the number
of messages and total bytes passing to and from that system are recorded.