PC Pro 1998 December/DPPCPRO1298.ISO/Extras/Imail/LISTSRV.TXT

Text File | 1997-04-16 | 10.2 KB | 304 lines

1.  Add support for a user defined string to be added at the
beginning of the subject line of every message sent to the list
if that string doesn't already exist within the subject line.
  Example where "[imail]" is the defined string:
    Subject: [imail] How do you receive mail?
    Subject: Re: [imail] How do you receive mail?
    Subject: [imail] Re: How do you add multiple addresses?

Enabled in the advanced tab... when you check the box the edit
box becomes active so you can enter the subject modification info..

Also a new option for digests set in the digest tab.. a subject
line to use for digest postings..


2.  Add support for user defined "header" and "trailer" messages
to every message sent to the list.  The idea is to be able to
add a trailer (or header) that might explain how to unsubscribe
from the list or advertisment.

Enabled in the advanced tab.. when you check either of these
boxes the edit button becomes enabled so you can edit the header/trailers..

Also a new option for the digest settings in the digest tab..
headers and trailers for the digest postings..

3.  Add an option to allow a list to be open or private for
subscriptions.  If private, the list would not accept subscriptions.

This new option makes the list private so the owner/admin has to
add new users either by editing the file or through the web interface...

NOTE: unsubscribes are always enabled as it would be unethical to
      not allow people to get off lists..


4.  Disallow List command: new

This makes the list command not work on lists so users cannot get
a list of your subscribes for unknown purpose...

5.  Add an option to disable "LIST" command per list where one
list could return a list of subscribed users while another list
would not.

This makes the list command not work on lists so users cannot get
a list of your subscribees for unknown purpose...


5.  Add a command line option that would allow a list to accept a
raw message and would subscribe the user specified in the
Reply-To: (or From: if Reply-To: header was not present) to the
list.  The message body would be ignored.
>   Suggested command line would look like:
>listsrv HOSTNAME LISTNAME -subscribe FILENAME
>    where HOSTNAME is the name of the virtual host
>    where LISTNAME is the name of the list
>    where "-subscribe FILENAME" would specify a raw single message filename.  if the
>FILENAME is a ".tmp" file, the file is removed after parsing.

The command is

     listsrv -add domainname listname

also added one for remove

     listsrv -remove domainname listname

also added one for removing based on unknown user or unknown host messages

     listsrv -ruhost domainname listname

NOTE: no message are sent to the person unsubscribe as a result of
      the ruhost command because presumeably the address is bouncing
      anyway and that is why you are removing it.. also this scans
      the file for the works "unknown host" or "unknown users"
      instead of using the from/replyto

you can setup program aliases for any of these new commands
i.e.

     [e-mail] = | listsrv -add kahn.drcoffsite.com bindnt


Remember to mention you have to be able to forward a message
unmodified (ie with the headers unchanged) in order for this
to work or you will end up removing/adding yourself to the list(S)..

Also related to this an appropriate message is sent to the person
being added subscribing just like previously..

Previously there was no message sent to a list owner when someone
unsubscribed (there still isnt) but when you unsubscribe or remove
someone using one of the above commands a messages is now sent to
the owner.. otherwise you cannot verify if the command worked
(especially when you are offsite)...

Also information about these commands are logged just like
subscribe/unsubscribe commands via the logerror call ...

Also related to this is that added support for the works "remove"
and "signoff" as well as the old standby unsubscribe (this was
added to the unsubscribe command)...

OTHER NEW COMMANDS:

The list owner can send a message to [e-mail] with
a message of the form:
unsubscribe listname [e-mail]

This will unsubscribe the user from the given list.. and send a
message to the person and the list-owner... note this doesn't
work for any other users as it is a security violation and would
allowing someone to remove all users from your list.. but it does
work from the list owner only....

Unsubscribe now removes users from both the users.lst and digest.lst
file...


6.  Add a digest mode that is list/user setable where all messages
sent to the list are "archived" in a mailbox and processed
once per user-defined-period and mailed to users that desire
a digest as a single message.
    The scheduler in the SMTP server will invoke the listsrv.exe
with a new command line switch to cause the listsrv.exe to
process the digest on every poll.  Or an additional program
could be written to process the digest if desired.
    Transmitted digests should have all headers except Date:,
From:, Reply-To:, and Subject: stripped out. Attachments, and
non-text sections should also be removed.

Options to enable\disable digest mode are on the advanced tab.
Once enabled two additional tabs appear digest and digest
scheduling.. discussed below..

There are two new commands that you can send to listserver to
support this

   set mode digest listname
   set mode standard listname

You must be on the list first to use these commands...
Appropriate message is sent to the person for either success
or failure and info is logged to the logs if enabled...


The new command line to have the listserver check for any lists
that need sending the digest posting is

   listsrv -q x

Related to this is a new smtp32 command to make sure that the
postings end up in the digest mailbox even if forwarding is
on.. it is smtp32 -noforward

--------------------------------------------------------
The following is a discussion of info based on the tabs..

general
------------


name: as previous
directory as previous

title as previous
owner as previous
local administrator: as previous

help/subscribe/users/address buttons: as previous


advanced
----------------
replyu to list vs sender: as previous
Enable digest mode: new
enable subject modification: new
enable header: new
enable trailer: new

edit buttons are for editing the related trailer/header/subject files..

max mesasge size: as previous
number of recipients: as previous

security
-----------------

allow postings by radio buttons: as previous

allow list unsubscribes based on subject line: new

this allows a subject line of the form:
unsubscribe
or
remove
or
signoff

recommendation turn this on but don't advertise that the
listserver supports it or you will get people misspelling
unsubscribe and it then going out on the list since
these messages are sent to the list address...

Disallow Subscriptions (ie private list): new

this new option makes the list private so the owner/admin
has to add new users either by editing the file or through
the web interface...

Disallow List comamnd: new

this makes the list command not work on lists so users
cannot get a list of your subscribees for unknown purpose...

related to this the help command on the listserver still
works but the help/list command for a given list will not
work if the list is in subscribers or moderated mode unless
the person sending it is already on the list...


Digest
------------

Digest mailbox:

this is a edit field for the name of the mailbox where
postings get stored before the digest mailing is sent out...

a copy of all postings will be sent to
[e-mail]

after a posting is sent to the digest list.. this mailbox is
emptied and a copy is made of the form: digestmailboxMMDD.mbx
where mm =month and dd =day in this way the list owner/moderator
can see the mailbox through the web interface and delete/add
messages before the digest posting is sent... he/she can also
get at old posted digests by the MMDD format


subject line for digest postings:

this is the subject line that is used on digest postings

Include headers/trailers when posting to digest mailbox:

this is by default off.. and if on.. the normal headers/trailers
for all postings will be included in the copy put in the digest
mailbox.. otherwise not.. recommend not doing this as the digest
posting has its own headers trailers.. and this just makes the
posting larger..

strip non-text attachements before posting:

as described ... strips non-text attachments from the copies
in the digest mailbox when the posting is sent..

Enable message spearators: self explanatory
enable digest headers: self explan.
enabel digest trailers: self explan.

Digest adrresses button: lets you edit the digest.lst file...



Digest Scheduling
---------------------

periodicity:
daily, weekly, bi-weekly, monthly, user defined, size exceeds, manual

for user-defined and size exceeds the edit box next to this item
becomes enabled so you can enter the days (for user defined) or
the kbytes (for size exceed) this controls how often the digest
posting is sent.. and how it is rescheduled for the next posting...

last processing date/time: a information only field

next processing date/time:

6 combo boxes to allow you to enter the next time the digest
will be processed (initially 1 week from list creation at 3:00 am)

month day year
hour minute am/pm


process send new: a button to allow the digest processing to
send a posting now and reschedule according to the above periodicity...

not for manual periodicity the posting is never sent
automatically but you must use this button to send it...


THATS IT .. or all that I can remember ... there were other
under the surface changes to fix bugs with queue names.. and
other stuff.. that is not relevent to the user manual... also
the smtp32 processes are now started up without appearing
on the desktop to improve performance...

testing is going ok and I haven't found anymore problems in
the past week or so...