syd@dsinc.DSI.COM (Syd Weinstein) (08/03/90)
Context difs of the changes in the Elm monthly posting.
*** o.elm.monthly
--- elm.monthly
**************
*** 1,4
! Expires: 5 Aug 90 00:00:00 GMT
This is the monthly Elm Posting from the Elm Development Group and
your Elm Coordinator. This posting generated:
--- 1,4 -----
! Expires: 12 Sep 90 00:00:00 GMT
This is the monthly Elm Posting from the Elm Development Group and
your Elm Coordinator. Please send all questions and comments about
**************
*** 1,8
Expires: 5 Aug 90 00:00:00 GMT
This is the monthly Elm Posting from the Elm Development Group and
! your Elm Coordinator. This posting generated:
! Fri Jun 22 17:04:12 EDT 1990
Current release version: Elm 2.3 PL3
This version was released at patch level 0.
--- 1,10 -----
Expires: 12 Sep 90 00:00:00 GMT
This is the monthly Elm Posting from the Elm Development Group and
! your Elm Coordinator. Please send all questions and comments about
! this posting or Elm itself to elm@dsi.com (dsinc!elm). This posting
! generated:
! Thu Aug 2 12:52:24 EDT 1990
Current release version: Elm 2.3 PL5
This version was released at patch level 0.
**************
*** 4,10
your Elm Coordinator. This posting generated:
Fri Jun 22 17:04:12 EDT 1990
! Current release version: Elm 2.3 PL3
This version was released at patch level 0.
comp.sources.unix Posting-number: Volume 22, Issues 60-85
Archive-name: elm2.3/part01 thru elm2.3/part26
--- 6,12 -----
generated:
Thu Aug 2 12:52:24 EDT 1990
! Current release version: Elm 2.3 PL5
This version was released at patch level 0.
comp.sources.unix Posting-number: Volume 22, Issues 60-85
Archive-name: elm2.3/part01 thru elm2.3/part26
**************
*** 10,17
Archive-name: elm2.3/part01 thru elm2.3/part26
Patches are posted to comp.sources.bugs and comp.mail.elm
After they are stable, patches are sent to comp.sources.unix
! Patches 1 through 3 have been sent to comp.sources.unix.
! No patches have yet been posted to comp.sources.unix.
Patches are available from the archive server at DSI.COM:
send mail to archive-server@DSI.COM
send elm index
--- 12,19 -----
Archive-name: elm2.3/part01 thru elm2.3/part26
Patches are posted to comp.sources.bugs and comp.mail.elm
After they are stable, patches are sent to comp.sources.unix
! Patches 1 through 5 have been sent to comp.sources.unix.
! No patches have yet appeared in comp.sources.unix.
Patches are available from the archive server at DSI.COM:
send mail to archive-server@DSI.COM
send elm index
**************
*** 21,28
information from the archive server.
Planed next version: Elm 2.4
! Current Elm 2.4 status: Not even started
! Expected release date: 5/1/91
As of release 2.1, Elm is now being developed by a cooperative venture
of volunteers loosely being called the Elm Development Group. There are
--- 23,30 -----
information from the archive server.
Planed next version: Elm 2.4
! Current Elm 2.4 status: In development
! Expected release date: not before 5/1/91
As of release 2.1, Elm is now being developed by a cooperative venture
of volunteers loosely being called the Elm Development Group. There are
**************
*** 47,53
mail me asking for me to send you patches, I won't. Use the archive
server. The archive-server will not respond to users named root,
daemon, or postmaster to prevent loops. Please do not use those names
! for archive requests. Also do not send archive requests to elm@dsi.com.
The following sites have agreed to make Elm available via anonymous ftp.
--- 49,55 -----
mail me asking for me to send you patches, I won't. Use the archive
server. The archive-server will not respond to users named root,
daemon, or postmaster to prevent loops. Please do not use those names
! for archive requests. PLEASE do not send archive requests to elm@dsi.com.
The following sites have agreed to make Elm available via anonymous ftp.
**************
*** 72,78
at the same time we are working on the next release. Also starting with
release 2.2 a list of known problems will be published in this posting.
! Known bugs in Elm 2.3 PL0:
The following are from the Elm 2.4 "To.Do" list that are
considered bugs, not enhancements, that have not yet been done. Items
which are enhancements are not listed here. It is our intention to
--- 74,80 -----
at the same time we are working on the next release. Also starting with
release 2.2 a list of known problems will be published in this posting.
! Known bugs in Elm 2.3 PL5:
The following are from the Elm 2.4 "To.Do" list that are
considered bugs, not enhancements, that have not yet been done. Items
which are enhancements are not listed here. It is our intention to
**************
*** 115,121
GB04 The preprocessor testing in Configure does not work with gcc
as the compiler.
! GB09 [next item goes here]
2. Elm(1) bugs
--- 117,125 -----
GB04 The preprocessor testing in Configure does not work with gcc
as the compiler.
! GB09 All addresses need to support both an escape character and
! quoting the name portion to allow for illegal chars and
! blanks.
GB10 [next item goes here]
**************
*** 117,123
GB09 [next item goes here]
! 2. Elm(1) bugs
EB02 Encryption is not fully implemented in ELM. In elm(1) we
have the following problems:
--- 121,127 -----
quoting the name portion to allow for illegal chars and
blanks.
! GB10 [next item goes here]
2. Elm(1) bugs
**************
*** 119,124
2. Elm(1) bugs
EB02 Encryption is not fully implemented in ELM. In elm(1) we
have the following problems:
--- 123,130 -----
GB10 [next item goes here]
+ 2. Elm(1) bugs
+
EB02 Encryption is not fully implemented in ELM. In elm(1) we
have the following problems:
**************
*** 183,189
EB23 Complaint (probably occurs under certain configurations
only) that address optimization occurs regardless of whether
! its configured.
EB24 Complaint (probably occurs under certain configurations
only) that address optimization "over optimizes" - the last
--- 189,196 -----
EB23 Complaint (probably occurs under certain configurations
only) that address optimization occurs regardless of whether
! its configured. [unable to check out anymore under Elm 2.3,
! will be dropped from the list]
EB24 Complaint (probably occurs under certain configurations
only) that address optimization "over optimizes" - the last
**************
*** 188,193
EB24 Complaint (probably occurs under certain configurations
only) that address optimization "over optimizes" - the last
node in the address is claimed to be known when it isn't.
EB25 If elm is replying to a message and considers From: lines
valid and resolves pathaliases, if the reply path from the
--- 195,202 -----
EB24 Complaint (probably occurs under certain configurations
only) that address optimization "over optimizes" - the last
node in the address is claimed to be known when it isn't.
+ [unable to check out anymore under Elm 2.3, will be dropped
+ from the list]
EB25 If elm is replying to a message and considers From: lines
valid and resolves pathaliases, if the reply path from the
**************
*** 216,222
full name information, it sometimes places the user name in
()s as the comment in addition to the full name.
! EB40 [next item goes here]
3. Utilities bugs
--- 225,233 -----
full name information, it sometimes places the user name in
()s as the comment in addition to the full name.
! EB40 If reading an alternate folder and all messages are marked
! for deletion and a resync is performed, the folder is delet-
! ed and Elm exits saying it cannot open the folder.
EB41 [next item goes here]
**************
*** 218,224
EB40 [next item goes here]
! 3. Utilities bugs
UB02 Newmail(1) displays a null "From" when a message does not
contain a From: header line. It needs to be able to parse
--- 229,235 -----
for deletion and a resync is performed, the folder is delet-
ed and Elm exits saying it cannot open the folder.
! EB41 [next item goes here]
3. Utilities bugs
**************
*** 220,225
3. Utilities bugs
UB02 Newmail(1) displays a null "From" when a message does not
contain a From: header line. It needs to be able to parse
the return path and display the "last two words" of it, just
--- 231,238 -----
EB41 [next item goes here]
+ 3. Utilities bugs
+
UB02 Newmail(1) displays a null "From" when a message does not
contain a From: header line. It needs to be able to parse
the return path and display the "last two words" of it, just
**************
*** 242,248
fore doesn't list all the "To" header, for example, if
presented on more than one line.
! UB12 [next item goes here]
New Features/Changes in 2.3:
--- 255,267 -----
fore doesn't list all the "To" header, for example, if
presented on more than one line.
! UB12 X.400 now also uses the = in its addresses, newalias was
! changed from : to = due to X.400, but now even = is not
! good for a delimiter. Newalias needs to have an escape
! mechanism for its addresses. This needs to be coordinated
! with GBxx.
!
! UB13 [next item goes here]
New Features/Changes in 2.3:
--
=====================================================================
Sydney S. Weinstein, CDP, CCP Elm Coordinator
Datacomp Systems, Inc. Voice: (215) 947-9900
syd@DSI.COM or dsinc!syd FAX: (215) 938-0235