Previous October 16, 1996
Return to CSuite Workshop Index
The new box can be reached at http://soltst.cs.dal.ca/ and needs to undergo a lot of beating before release, so all members of the team are asked to take some time to check it out. User registration is via the usual route Services/Registration/ or by logging in as guest. Of course, once the registration is completed, then we should e-mail Landon@chebucto.ns.ca to have the new test account activated, in lieue of sending a cheque ;-)
We want to test all functions, so need to acquire necessary permissions and interfaces from Landon to access some administrative areas. This may involve the invention of needed interfaces to manage these functions.
David Murdoch (djm@chebucto.ns.ca) will serve as Head of Testing. David Benoit (benoit@chebucto.ns.ca) has some documentation on testing that he will provide.
James and Andrew are documenting the install procedure. It is planned to incorporate more live functions, and file editing interfaces, rather than the current instructions to "go do ..."
All participants are requested to make notes and forward them to csuite-test@chebucto.ns.ca [Change - Ed.]
Please note: For administrative purposes, a separate list has been set up to facilitate testing feedback, called csuite-test@chebucto.ns.ca (subscription via Majordomo.) This will help to keep csuite-dev for its original purpose, discussion of development issues for Chebucto Suite.
Concerns were raised about the variables ADDRESS and CURRENCY, and whether they were still required.
Return to Topic List
Client:
. connect to the server to notify login, and tell server to send
any pending messages.
Server:
. recieve a connection from the client, and return to the client
if mail is to be sent.
. If there is mail to be sent, lock the user's mail file, and send the
mail (this can either be sent to the client to add, or done at the
system level)
. Once the mail is sent, remove the user from the database, and for
each message that was sent to the user, decrease the pending count
on that message.
. If the pending count on a message reaches 0, delete the message
from the mail directory.
. Expiries will be checked before notification is sent to the client,
to make sure that if all the mail that is to be sent to the user has
expired, the client will recieve notice that there is no mail.
. a mailer daemon will be running on: bulkmail.chebucto.ns.ca
. any bulkmail will be sent through this daemon. EG:
ccn-tech@bulkmail.chebucto.ns.ca
would send mail to the members of ccn-tech through the bulkmailer.
. bulkmail recieves a connection from the mailer daemon.
. a request will be made to send a new message.
. for each recipient:
. lookup the mail that is pending for the user
. remove the record from the database
. insert the new message ID
. put the user information back into the database
. the text of the message will then be put in the bulkmail directory
with the lowest message id that is available.
Additions:
. use identd as an authentication method
. have some sort of deferred creating of a mail message
. size limit
. keep list of addresses that message is sent to and a complete list
of the people that it was originally sent to.
. when the message is sent to a user, add them to the list of
recipients
. delete message number from list kept for the user after it is sent
Specials:
. gdbm file for forwarded addresses. This is updated using 'go forward'
. dynamic mailing lists (eg: all-users):
. have a separate gdbm file for each dynamic list
. same structure as the others except, for each user, store
what messages they have recieved
. when requesting bulkmail, server will know what dynamic lists
are active, and lookup the user in each one of those lists.
. have a default expiry date, be able to have a limit.
. when mail is sent to be processed, before adding, check if user is
logged in. If they are, send it immediately.
File Formats:
. bulkmail directory will consist of:
For regular messages:
. {msg_id}.msg - text of message (full headers included)
. {msg_id}.to - addresses of all potential recipients
. {msg_id}.sent - addresses of sucessfull recipents
. db.bulkmail - mail database will regular messages
For dynamic messages:
. {msg_id}.msg - text of message (full headers included)
. {msg_id}.sent - addresses of sucessful recipents
. db.{list-name} - database file (described above)
. db.msgIdIndex - number of messages unsent for each msg.
Return to Topic List
Return to Topic List
Ed Dyer, as a CCN Editor, will take over the IP Committee liason role.
IP committee concerns lay around the "Group Editing" function, ftp access and installation of documents for IP sites, and installation by extracting zip files.
A desired function is to be able to explicitly assign/reassign the IPE1 role, in view of its function as chief editor and ip-priv mail-list owner. Possible delegation of Group Editing to the IPE1 is understood to be requested, but concerns are raised as to the appropriateness of that option. Concerns were raised as to difficulties in accessing the IPDB, and Tony reported that he normally had to enter his password 3 times before he gained access.
Return to Topic List
The various graphics browser emulations were suggested, but David Trueman opined that a better route would be a SLIP or PPP service with access limited to the local host, by running it through the proxy server, thus providing effective testing for Editors, with no implications for our internet service. The service would be available for editors only. At this point the project would appear to be low in our priority list.
Return to Topic List
Return to Topic List
Previous Workshop October 16, 1996
Return to CSuite Workshop Index
Submitted by Ed
Dyer aa146@chebucto.ns.ca
Workshop Coordinator David J Murdoch
djm@chebucto.ns.ca