@database 002feeb8-0
@master DH1:Wirenet/Thor/Rexx/HeaderManager.guide
@$VER: 1.15
@author "Neil Bothwick"
@(c) "1997"
@remark Created with Heddley v1.1 (c) Edd Dumbill 1994

@node "Main" "HeaderManager.guide"

            @{b}HeaderManager.thor v1.15@{ub}

            (c) Neil Bothwick, 1996-7


       @{" Introduction " link "Introduction" 0}

       @{" Installation " link "Installation" 0}

       @{" Adding a Header " link "Add Header" 0}

       @{" Editing a header " link "Edit Header" 0}

       @{" Deleting a header " link "Delete Header" 0}

       @{" Acknowledgements " link "Thanks" 0}

       @{" Distribution " link "Distribution" 0}

       @{" History " link "History" 0}
@endnode

@node "Introduction" "Introduction"

            @{b}@{u}Introduction@{ub}@{uu}

Thor has many powerful features, but the handling of @{" message headers " link "Headers" 0} in the
current version is limited. Although you can define your own headers in the
.header file, these can only be used for all messages.

If you wish to add specific headers to a message, such as Cc: or Followup-To:,
you have to type them directly into the top of the message. This means you
cannot use the User Database to add addresses, and if you mistype the header
it will appear in the message body, together with all subsequent headers.

HeaderManager provides you with the ability to add, edit and delete headers,
using the User Database and Conference List to insert the information.
@endnode

@node "Installation" "Installation"

            @{b}Installation@{ub}

1)  Copy HeaderManager.thor to <ThorPath>/rexx

2)  Copy this guide to <ThorPath>/Docs

3)  Select Add Script from the Arexx menu in Thor to add this to a
    Function Key and the Menu


<ThorPath> is the directory containing Thor itself.
@endnode

@node "Add Header" "Adding a Header"

            @{b}Adding a new Header@{ub}

Select Add new header from the menu. You will be presented with a list of the
@{" headers " link "Headers" 0} available. Select the one you want.

If a newsgroup name is required, select one or more from the list.

If an email address is required you can either type in the full address, or
type in part or all of the persons name to search the User Database for the
address.
@endnode

@node "Edit Header" "Editing a header"

            @{b}Editing a new Header@{ub}

Select the header from the menu and Edit from the Edit/Delete requester that
comes up.

You may then edit the header in the same way as adding a new one.
@endnode

@node "Delete Header" "Deleting a header"

            @{b}Deleting a new Header@{ub}

Select the header from the menu.

When the Edit/Delete requester comes up, select Delete.
@endnode

@node "Headers" "Headers"

            @{b}@{u}Headers Available@{ub}@{uu}

HeaderManager.thor currently supports the following headers

@{b}Cc:@{ub}
    This requires an email address, to which a duplicate copy of the mail
    will be sent. It stands for Carbon Copy, as with paper messages.

@{b}Bcc:@{ub}
    This is the same as Cc: except the line is not included in the copy
    sent to the main recipient, so he/she doesn't know ou've copied it
    elsewhere. Bcc stands for Blind carbon copy.

@{b}Followup-To:@{ub}
    This is used in news to divert the replies to another newsgroup. If
    you set it to EMail, then replies will automatically be mailed to you
    instead of posted to the group. Particularly useful in advertising
    groups.

@{b}Reply-To:@{ub}
    This means an email reply will default to this address, instead of
    the sending address.

@{b}Custom@{ub}
    Custom headers usually start with X- and anything after this is valid.
    There must be no spaces between the X- and the : that denotes the end
    of the header name. Don't overuse this.


Some headers are only relevant to mail or news. If you try to add an
inappropriate header, such as Follwoup-To: in a mail message, Header Manager
will warn you.
@endnode

@node "Thanks" "Acknowledgements"

            @{b}@{u}Acknowledgements@{ub}@{uu}

Thanks to:

    The Thor team for developing the Amiga's best news and mail
    software.

    Bill Hawes for developing arexx, one of the Amiga's greatest and
    most underrated strengths.

    Shaun Downend <shaund@amiganut.demon.co.uk> for testing this, and
    to Shaun and Paul Copsey for jointly proving a need for it ;-)

    Dietmar Eilart for GoldED and Edd Dumbill for Hedley.
@endnode

@node "Distribution" "Distribution "

            @{b}@{u}Distribution@{ub}@{uu}

HeaderManager.thor is freely distributable, but remains (c) Neil Bothwick,
1996.

It may not be included in any commercial distribution without prior consent.
Such consent is already given to include it on the Aminet CDs.

It may be included on magazine cover disks or CDs, provided notification is
sent beforehand. A copy of the magazine and disk would be most welcome.

Please sent bug reports, suggestions and large amounts of cash to me at
neil@wirenet.u-net.com.
@endnode

@node "History" "History"

            @{b}Release History@{ub}

1.16 (30.12.98)
    Added 256 character limit for header lengths

1.12 (5.1.97)
    Added support for the Forward events type of Thor 2.4

1.11 (15.09.96)
    Changed Bcc: header to bcc: to avoid a bug in Thor 2.3/2.31

1.10 (14.08.96)
    Fixed a small bug that caused a bogus header to be created if you
    selected Add New Header and then Cancel

1.0  (05.08.96)
    First release version
@endnode