Media Share 9/MEDIASHARE_09.ISO/pcboard/uupcb100.zip/UUPCBOUT.NEW

Text File | 1993-04-07 | 15KB | 410 lines

                       UUPCBOUT.EXE History File

Version 1.00 - 4/8/93  -

Made the new email header added as part of 0.77 (Item #6 below) optional.
To activate it, enter DUMBMAILER=Y in UUPCB.INI.

Version 0.80 - 1/31/93 - Two changes:

1. Fixed broken mailing list function.  In Version 0.79 mailing list
   mailings would be ignored.

2. Added further enhancements to EMAIL.LOG:

It now looks like this:

───────────────────────────────────────────────────────────────────────
                      uuPCB EMAIL TRANSFER LOG
───────────────────────────────────────────────────────────────────────
DATE      IN/OUT  USER                        BYTES   Conf#     Msg #
───────────────────────────────────────────────────────────────────────
01-31-1993   N    ED HOPPER                    404        1       474
01-31-1993   O    ED HOPPER                  1,322        3       506
01-31-1993   I    ED HOPPER                    440       12       580
01-31-1993   O    ED HOPPER                    473       12       581

It will now record the Conference Number and Message Number exported or
imported.  In addition, the I and O entries under IN/OUT have been
joined by a "N" entry for "News".  In other words, if EMAIL.LOG is
active, it will record news articles sent out by means of the normal
news channels as a type "N".  Note, news mailed out to a moderator is
recorded as an "O".  In the above example, Conference 1 is a normal
newsgroup, Conference 3 is a moderated newsgroup (note the "O") and
conference 12 is email.

IMPORTANT: The HEADER for the report will not be updated if the
EMAIL.LOG is already in existence for a pre-0.80 version.  This is only
a cosmetic problem.  If you want the new headers with the "Conf#" and
"Msg#" column headers, delete the old log and UUPCBOUT 0.80 will
generate a new one with the new style header.


(Note: UUPCBIN will be updated in version 0.91 to record the conf# and
Msg#).

Version 0.79 - 1/10/93 - Pointer problems persisted from 0.78.  If
CNAMES contained an invalid or blank entry, UUPCBOUT would have problems
generating a pointer file.  This is now fixed.

Added three new items:

        1. UUPCBOUT will now abort when ESCAPE is pressed.

        2. UUPCBOUT exits with ErrorLevel 2 if Mail or Mail & News were
           exported, it exits with ErrorLevel 1 if only news was exported.
           This will allow you to initiate a call to your host when you have
           email, but to wait if you only have news.

        3. Added visual displays during UUPCB.PTR generation so that
           sysops can track what is going on.

Version 0.78 - 12/30/92  Fixed pointer file problems.  A minor internal
change to UUPCBOUT caused BAD FILE NAME errors when a new UUPCB.PTR file
is generated.  In addition, other, similar errors were generated
including corrupted pointer files.  Now fixed, no other changes.

Version 0.77ß - 12/19/92 - Many major enhancements:

1. Signature lines:  This is a 1-4 line usenet "tagline".  It is appended
to each outgoing news article and email message.

2. Mailing list support.  One message will go to numerous recipients of
a previously defined list of users.

3. /M switch for email only.  Run UUPCBOUT /M and it will do email only,
perfect for keeping your email connections as fast as possible.

4. Exits with errorlevel 1 if mail or news was exported.

5. Supported the following additional header keywords in outbound
messages:

References:
Followup-To:
Summary:
Keywords:

6. Minor fix in outgoing email headers to insure that they process
properly with certain "dumb" mailers.

7. Added error trapping on outgoing email addresses.  This will let
people quote email return addresses without editing them (since no one
edits them anyway!).

Here is how to set these things up:

Signature Lines:  The keywords SIG1 thourgh SIG4 define the tagline in
your uuPCB.INI file.  *MAKE SURE* that your tagline does NOT contain
any high order ascii characters (This includes line drawing characters).

Here's a sample:

Sig1=+------------------------------------------------------------------------+
Sig2=| Ed Hopper's BBS    404-446-9462 (USR HST) 404-446-9465 (HST DS)        |
Sig3=| Berkeley Lake (Atlanta), Georgia   - Home of uuPCB Usenet for PC  Board|
Sig4=+------------------------------------------------------------------------+


2. Mailing List support.  Place the following values in UUPCB.INI:

LISTDIR={subdirectory}
for example
LISTDIR=D:\UUPCB\LISTS

Each mailing list is represented by a file in this directory.  Each file
should have a 1 to 8 character filename with *NO EXTENSION*.  Let's say
you wanted to start an Elvis fan club mailing list.  In your LISTDIR,
you would have a file called "ELVIS".  This is a simple, flat ascii file
with one email address per line.  It would look like this:

[e-mail]
[e-mail]
[e-mail]

and so on.

To enter a mailing list message, enter the following header *INSTEAD OF*
the uuPCB TO: header:

LIST: elvis

DO NOT USE "TO: elvis"!

You can have as many mailing lists as you want and each one can be as
long as you want.

Of course, you may not want everyone having the authority to send email to
a mailing list.   To control access, create a file called "MAILLIST.OK"
in the LISTDIR.  Add entries for each list and for each autorized person.
These should consist of the name of the list, a semicolon (;) and the PC
Board name of the authorized sender.  Use "all" to open up a list to all
users.

For example:

elvis;priscilla presley
elvis;tom parker
startrek;bill kirk
boredom;all

In the above example, everyone can send to the "boredom" list, Bill Kirk
can send them to the Star Trek list and Priscilla Preseley and Tom
Parker can send to the Elvis list.

SPECIAL NOTE FOR SYSOPS:

If you are to be an authorized user, enter YOUR NAME, not "SYSOP" as an
authorized user in MAILLIST.OK.  This should match the SYSOP= line from
UUPCB.INI.

3. The "/M" switch.  By entering "UUPCBOUT /M", uuPCB will only process
the email conference.  This is designed for those sites that want to
exchange email on a tighter schedule then the schedule for news.

4. Errorlevel 1.  UUPCBOUT now exists with ERRORLEVEL 1 if news or email
was exported.  This will allow you to determine if a UUCICO call is
required.

5.  UUPCBOUT will now support the following keywords when embedded in PC
Board message text:

References:
Followup-To:
Summary:
Keywords:

References: refers to the message-ID of the message you are replying to.
For example:
References: [e-mail]

Followup-To: This directs replies to a different newsgroup than the one
in which the article is posted.

Summary: This is a one-line summary of a news article.  It allows the
poster to add his "spin" to an article without changing the subject.

For example:

Subject: Elvis was kidpnapped by Rigelian aliens
Summary: He was not! They were Venusians!

Keywords: Another method that allows you to add some additional info to
the top of your news article.  As it implies, these are one-word entries
that provide additional info about your posting.

6. Some unix systems insist on having the line:

From ed.hopper Wed Dec 16 21:21:00 1992 remote from ehbbs

as the first line of email messages.  This is now provided.

7.  It has been very common for users to quote entire From: or Reply-To:
lines in their messages for the TO: entry.  uuPCB now detects such
entries and derives the correct email address.  For example, in the past
if an email was sent to:

TO: [e-mail] (Ed Hopper)

most UNIX systems would fail due to the (Ed Hopper) at the end of the
address.

Now, uuPCB will extract the email address and use that instead.

------------------------------------------------------------------------
Version 0.76ß - 4/4/92 - New version to insure compatibility with the
additional fields in the UUPCB.DBF required by UUPCBIN Version 0.80ß.
See UUPCBIN.NEW in the UUPIN80.ZIP File for more info.

Version 0.75ß - 2/29/92

Fixed broken bang domain function.  (See below)

=============================================================================
Version 0.74ß - 2/23/92

IMPORTANT: Please note the TZOFFSET variable for UUPCB.INI is now REQUIRED!
           See below  (Item #2) for more info.

Item #1 - Message Keywords

There has been a lot of discussion about exactly how to handle public
messages posted on your BBS in newsgroups.  While any message that has
been left with ECHO=Y and public is exported,  there has been a need for
some other features.  Version 0.74 adds some additional features to
assist in email and news article postings.

Users can now specify SUBJECT, NEWSGROUP and DISTRIBUTION entries in the
text of their news articles and can specify SUBJECT in email messages.

(Remember, with uuPCB email refers to private, user to user messages.
"News articles" is the name given to public messages in public
conferences.)

To do so, users should place a keyword in the top of their messages
followed by their desired entry.  For example:

         To: ALL                       Subj: DUMMY
        (------------------------------------------------------------------)
|---->1: SUBJECT: What is the best price for HBO via TVRO?
| |-->2: NEWSGROUP: rec.video.satellite, rec.video.catv
| ||->3: DISTRIBUTION: tx
| ||  4: I'm wondering what's the best price for HBO on either satellite or
| ||  5: cable-TV?
| ||  6:
| ||  7: Ed Hopper
| ||  8: [e-mail]
| ||  Press (Esc) to Exit  (Ctrl-Z) for Help  (Ins/Ctrl-V) Mode: Insert
| ||
| ||- The DISTRIBUTION: keyword sets the Distribution: field in the news
| |   article.  In this case, this news article is restricted to the state
| |   of Texas.
| |
| |-  The NEWSGROUP: keyword sets the Newsgroup: field for the news article.
|     Note:  This OVERRIDES the entry for the conference.  This is necessary
|     when one replies to a news article which specifies "Followup-To:"
|     and a different newsgroup.  This can also be used to allow users
|     to "cross-post" the same message to multiple groups.  Note how two
|     groups are specified in the example.
|
|---- The SUBJECT: keyword is probably the one with the most common
      application.  By specifying the SUBJECT here, rather than in the
      PC Board field, you can have a wider subject line (at least 60
      characters) than PC Board allows.  You can also have upper and
      lower case.

ITEM #2 - Multiple TO: line bug

The Problem: If a line that begins with "TO:" is found farther down in
the text, UUPCBOUT would use that instead of the ORIGINAL "TO:" line.
Fixed.

Note that uuPCB doesn't currently support the "CC:" function.  This can
be done by using the "SC" option in PC Board, then editing the
subsequent messages to change the "TO:" line.  We're looking at a "CC:"
function in a later release.

ITEM #3 - Fixed EMail date format to comply with RFC-822
Another change here is to make uuPCB email messages comply with the
RFC-822 standard.  The main problem was in the date format.  Previously,
the date field in uuPCB email messages was the same as the date field in
uuPCB USENET news articles.  Unfortunately, while it would make sense
for both applications to use the same format,  they don't.

Here's the old EMail format:

Date: 13 Feb 92 18:21:00 GMT

The new format, as required by RFC-822 is:

Date: Thu, 13 Feb 92 18:21:00 -0600

The last item (-0600) is the offset from GMT.  This will necessitate the
following addition to UUPCB.INI:

TZOFFSET=-0600

Note that -0600 is the offset for CST.

Other Timezones are:

EST/EDT : -0500
MST/MDT : -0700
PST/PDT : -0800

This item MUST BE ADDED TO UUPCB.INI if you wish to run UUPCBOUT version
0.74 or later!

ITEM #4 - Status Display

Added a display when processing mail.

===============================================================================

Version 0.73 - 1/26/92

This is a quicky to cure some problems encountered with French and other
languages.  It adds the parameter "NOSTRIP" to UUPCB.INI.  When you include
the line "NOSTRIP=Y" in UUPCB.INI, it will NOT strip HIGH ASCII characters
from outbound messages.  DO NOT INCLUDE THIS LINE unless your messages are
in a language other than English.

==============================================================================

Version 0.72 - 1/3/92

Several sites were reporting problems sending email.  There was a bug in
the code in which the MAILHOST parameter was not being honored.  Only if
a host was specified in the "email" newsgroup in DBFSETUP was mail
exported.  This is now fixed and the entry in DBFSETUP no longer
requires a HOST entry.  My test system had an entry so I wasn't seeing
the problem here.  Thanks to Brad Chesbro and Steve Williams for the
input.

==============================================================================

Version 0.71 - 1/1/92

Only one change here, this is to support situations where your system does
not have a domain name, but your feed site does.  In that case, one of
two addressing options allow people to reach you.

BACKGROUND:  In many cases,  if your feed site has a registered domain,
your system can be easily added to that domain.  In other words if you
connected to a machine that was part of the "hopper.com" domain and your
machine was named "grass" it could be called "grass.hopper.com".

In some situations, however, adding your machine to the domain is not
possible.  Therefore, until you can get your own domain address setup,
you will have to have a compound mailing address.  A compound address
looks like this:

Option 1:
[e-mail]

or

Option 2:
grass![e-mail]

In other words, your address will tell other systems "turn this mail
over to hopper.com" and ask it to mail it to the system "grass".  This
address presumes that hopper.com knows how to get to grass.

Option 1:

[e-mail]

i.e.:
[e-mail]

To enable this type of return address on your mail and news, do the following:

In UUPCB.INI:

HOST=yoursite
DOMAIN=feedsite.domain
SUBDOMAIN=Y

Option 2:
(Note, this option is commonly used, but official frowned upon by the
net.gods).

yoursite![e-mail]

i.e.:
ehbbs![e-mail]

To enable this type of return address on your mail and news, do the following:

In UUPCB.INI:

HOST=yoursite
DOMAIN=feedsite.domain
BANGDOMAIN=Y

(Note: In UNIX parlance, the "!" is referred to as a "bang".)

ASK YOUR FEEDSITE which option is required for email to you.