1 
 2 09/21/87  executive_mail
 3 Known errors in the current release of executive_mail.
 4 #         Associated TR's
 5 Description
 6 
 7 138
 8 If you read mail in another person's mailbox and try to reply to that
 9 mail, and if the reply-to person was not the sender of the mail, the
10 name of the recipient of the mail (the person whose mailbox you're
11 reading) will be placed in the cc:  field automatically.
12 
13 emacs_rmail has the same problem.  This is caused by calling
14 mlsys_utils_ $create_reply_message with the
15 reply_option.flag.include_recipients set to true.  If this is not set
16 to true, no-one in the cc field will be included in the reply.
17 
18 135  phx20728
19 When a user supplies a search string for selecting messages, the entire
20 message is searched including portions that are not displayed on the
21 screen.  Only those portions which are displayed should be searched so
22 as to avoid confusion.
23 
24 This problem occurs because xmail uses mlsys_utils_$search_message to
25 perform the search.  This program will search whatever portion of the
26 message the caller requests (envelope, header, redistribution_list,
27 body), but xmail's version of a header is drawn from portions of
28 several of these structures which must be searched in their entirety to
29 cover the visible-to-xmail fields.  Therefore, non-visible fields are
30 matched.  The alternative is to not use this facility, but to write a
31 whole separate parser to examine what xmail knows about.
32 
33 One possible alternative to scrapping the mlsys_util program might be
34 to provide a means for xmail to display the entire header so that users
35 could determine why messages were selected.
36 
37 113
38 Xmail creates a segment name for a deferred reply by changing the first
39 70 bits of the message_id into a unique character string.  This has
40 lead to problems when dealing with foreign mail, as the mechanism to
41 generate message IDs will only guarantee a unique ID with local mail
42 and within a process for foreign mail.  In a small amount of cases,
43 xmail will try to use a deferred reply for a different message.  A
44 possible solution is to generate the segment name by changing the bits
45 of the date_time_created field into a unique character string.
46 
47 112  phx19445
48 It is possible to be placed into the lisp environment during xmail if
49 the break key is hit at exactly the right time when the editor is first
50 setting up.  The window of time is extremely small and the problem is
51 difficult to reproduce.  It is caused by the small window between lisp
52 and emacs initialization where the emacs quit handler is invoked but
53 not all things are initialized.  This is a system limitation for xmail
54 at this time.
55 
56 96  phx17755
57 Xmail does not consider the case where the user may not be at the same
58 authorization as the access class of the .mlsys dir.
59 
60 38  phx12077
61 Executive_mail cannot run while the audit system is on.  This should be
62 documented as a limitation.
63 
64 29  phx12778
65 An error message, "Fatal error ...  Error while processing in lower
66 ring ..." pops up at odd (rare) times.  The last time it happened, the
67 user had deleted all of his incoming mail and was trying to exit via
68 F4.  This error always happens when the user is trying to exit.
69 
70 10
71 Error logging should keep track of more useful information.