| 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 |
My customer is running ALL-IN-1 V2.4, and may have discovered a problem
with address lookups on the Message Header screen.
In PROFILE.DAT there is an entry for local account POC.
In NETWORK.DAT there is the corresponding entry for the local user
POC, and an off-node user AU.POC
When AU, AU., AU.P, and AU.PO is entered on the Message Header, AU.POC
is correctly selected. When AU.POC is entered and terminated with
GOLD-L, AU.POC is also correctly selected. When AU.POC is entered and
terminated with a CR, local user POC is incorrectly selected!!!!
Any thoughts? On the surface, it looks like ALL-IN-1 is ignoring
what's to the left of the period, and looking up what's to the right of
the period in PROFILE.
Note: I was able to do a <FORM NETWORK and create bogus entries for
users that are in PROFILE, in the form <bogus stuff>.<PROFILE id>.
When I entered <bogus stuff>.<PROFILE id> terminated by RETURN, their
PROFILE address was selected, and not the bogus NETWORK address that I
created.
Thanks in advance...
David
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2078.1 | Already reported | AIMTEC::WICKS_A | A year behind in more ways than one | Wed Jan 13 1993 22:19 | 18 |
Note 820 in the old version of this conference and STARS
indicate that this is a known problem with ',' and '-' as well.
I won't post the entire article here except to say that it includes all of
the following phrases "a known problem", "reported to Engineering",
and "no available workaround" and was written by Alan Crooks based
on information provided by a Mail Developer at the time (late 1990)
... and where is the cheque you promised in 820.3 Alan?
Nothing has changed and the code still behaves or misbehaves the same
way two-and-a-bit years later.
Regards,
Andrew.D.Wicks
| |||||
| 2078.7 | A bit more (excuse?) | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Fri Jan 15 1993 09:18 | 27 |
Unforunately, this problem, trivial though it may look on the outside,
would require a complete re-design and re-write of the mail address
recoginition code to fix. Even then, it isn't clear that it could
reliably be fixed without breaking something else.
It arises because the lookup code first looks up the whole string
(AU.POC). If it fails, it re-tries (as you spotted) with the part to
the right of any punctuation - this is to allow the user to enter
"Dave Shove" when only "Shove" is in the profile.
This works fine as long as there's only one lookup (Profile) involved.
Where it goes wrong is in its interaction with looking up in multiple
directories (Profile, Network, DDS ...)
It isn't even obvious (if you think about it) exactly what it should do
in this case. Clearly what you see is silly, but fixing that might
produce other even sillier side-effects or incompatibilities. For
example, it could display a list of choices (POC and AU.POC) - but that
would potentially upset users who are used to it getting what for them
is the "right" one first time.
As I said, a full solution to this may be impossible, and would
certainly involve a lot of work - and as Eileen said, there's a limit
to how much we can do.
Not ,uch help I know,
Dave.
| |||||