Environment
Novell GroupWise 7
Novell GroupWise 32 bit Client
GroupWise Client in Online Mode
Situation
A user selects File | Save Draft to save a draft mail message. The
message appears to be saved since no error message is displayed but
the message never shows up in the folder the user selected to save
to.
When the user tries to close the mail window he is prompted to"Save changes to this item?". Even when saving the draft message again the user will be prompted to save changes next time he tries to close the window. The user will not be able to close the mail window besides by selecting not to save changes.
When the user tries to close the mail window he is prompted to"Save changes to this item?". Even when saving the draft message again the user will be prompted to save changes next time he tries to close the window. The user will not be able to close the mail window besides by selecting not to save changes.
Resolution
The problem is that either the CC: or the BC: field contain an
invalid address. The invalid address, e.g, a typo, may not even be
in the visible part of the CC: or BC: field. GroupWise does not
save the message because it wants the user to correct the invalid
address first but does not make it apparent, e.g. by selecting the
address field or returning an error code, that there is a problem.
In the GroupWise 6.5 client the focus jumped to the address field
containing the invalid address and gave an error message, pointing
out the problem.
The problem only occurs in Online mode, when the client is in Caching mode the draft message is saved despite the invalid address(es).
A similar problem existed in GroupWise 6, see KB 10070088.
This issue has been reported to developemnt and is currently scheduled to be fixed in the next minor release of GroupWise after version 7.
The problem only occurs in Online mode, when the client is in Caching mode the draft message is saved despite the invalid address(es).
A similar problem existed in GroupWise 6, see KB 10070088.
This issue has been reported to developemnt and is currently scheduled to be fixed in the next minor release of GroupWise after version 7.