[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
|
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
2518.0. "v3.0 bug in mail Detach" by GANTRY::HULL (Digital Services Delivery - Motown) Fri Apr 02 1993 13:30
My customer found the following Mail DETach bug in V3.0:
Mail msg A is a READ msg
Mail msg B is an OUTBOX msg (a reply to A) with A attached
Mail msg C is a new created msg.
User receives msg A, and replies to it (msg B), and attaches the original
msg A to it.
He then creates msg C to forward all this info to another party. But he
wants the A/B msgs in true chronological order, so he Attaches A to C, then
B to C. But B already has A on it, so he tries to use DETach msg, and
chooses the 3rd item (the 2nd occurance of A). DETach says it is now
detached. However, the system has actually detached the FIRST occurance of
A, not the 2nd one. I watched this happen.
So the bug is somewhere in the DETach code.
When I tested this with 3 created msgs in sequence, DET worked correctly.
So somehow the fact that the msgs are READ and/or SENT affects this bug.
-Al
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2518.1 | Known, I think | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Fri Apr 02 1993 17:42 | 7 |
| There are some problems with DETach, and I think this is one of the
known ones.
There are plans to fix these, but I don't know when you'll see
anything.
D.
|
| 2518.2 | Sure is known... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Apr 05 1993 11:23 | 5 |
| I reported this *personally*, so I *know* it's a known bug! Of course I
had a lot of trouble convincing the FC team that it was a bug and not a
feature :-)
Graham
|