Subj : RE: questions on outgoing e-mail message storage, routing and processi
To   : All
From : CARLTON SMITH
Date : Thu Jan 31 2019 07:10 pm

Date: Fri, 09 Aug 2002 19:59:37 -0400
From: CARLTON SMITH
To: HECTOR SANTOS
Subject: RE: questions on outgoing e-mail message storage, routing and
processin
Newsgroups: win.server.wish.list
Message-ID: <[email protected]>
References:  <[email protected]>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 81

I had an idea about this issue if not previous writen, How about just an
indexed header for just those (sysop access) ? That is somewhat how Forte
handles multiple folders. The sysop or whoever can just scan the headers and
read what he needs to.
->
-> On Feb 20, 2001 05:30pm, DANIEL C. MILLER wrote to ALL:
->
->  DCM> I need a few confirmations about storage of e-
->  DCM> mail only messages in wc6 vs. wc5.
->
->  DCM> 1. Outgoing messages for the e-mail conference
->  DCM> are all stored together in one database for all
->  DCM> users, but incoming e-mails are stored in
->  DCM> individual files for each user?
->
-> This was the original wc6 designed. However, with the open testing
-> we did, we found many design problems and reverted back the 1 database
-> system.   This is one of the delays we have: Trying to improve
-> this by potential heavy I/O.  We might revert back to the distributed
-> design but we want to make sure "EVERYTHING" works first, everything that
-> surrounds email.   It is a complicated reason.  Just for the techies,
-> one of the problems was a compatibility issue with the client SDK
-> functions and the idea of conference 0 being a user email conference.
-> One example of the problem was a SYSOP trying to read the email
-> conference.  In wc5, the SDK functionality for this was extremely simple.
-> Generic Logic like this found in many of the mail reading logics in
-> wildcat:
->
->        start loop:
->           Get First Email in Conference 0
->                 display/list/pack, etc.
->           Get Next Email in Conference 0
->        loop
->
-> controlled how mail is retrieved and/or received.
->
-> The Login Security manager handled and determined what email was
-> returned from the above loop.  So if User X logged in, User X got only
-> his mail.  But if the sysop logged in, he basically got all the mail.
->
-> Well, with a distributed email system, this drastically changed
-> what is a very fundamental logic in many of the programs in Wildcat.
-> It required that for a SYSOP, it became a search for ALL user mail
-> bins with lots of file I/O.
->
-> So we went back until we get everything else done.  In the end,
-> it will be improved.
->
->  DCM> 2. If you send a message via e-mail to another
->  DCM> user within the same wc6 system the message first
->  DCM> goes into the central outgoing database, and then
->  DCM> goes into the recipient's individual database?
->
-> The bottom line it will be behave like it does now.  The only
-> thing we are trying to improve is the LOADING issues for the
-> larger email systems.
->
->  DCM> 3. If you send a message via e-mail to an
->  DCM> Internet address the message first goes into the
->  DCM> central outgoing database, then is sent to the
->  DCM> recipient's mail server (possibly through one or
->  DCM> more SMTP relays), and finally it goes ?WHERE?
->
-> same answer as above
->
->  DCM> 4. What happens in the special case when you send
->  DCM> to another user in the same system, but using
->  DCM> Internet addressing? Does wc6 "know" this is
->  DCM> taking place or does it just send to itself
->  DCM> (again, possibly through one or more SMTP relays)
->  DCM> with no special processing?
->
-> same answer as above
->
->  DCM> 5. In wc6, how does a user keep a copy of their
->  DCM> sent e-mail, preferably automatically under
->  DCM> control of a user option?
->
-> same answer as above


--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

You are viewing proxied material from vert.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.