| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 484.1 | excuses, excuses ... but SHOULD be fixed now... | SHALOT::LAMPSON | If you read this, you're too close! | Tue Apr 14 1992 16:12 | 13 |
| It wasn't fixed in V2.4 because it required an "architectural"
change. Namely, that the attendee name field in the attendee file
was too small and changing it would require too many changes and
not enough time to assure product quality. After all, it was even
too risky to remove the old UI in V2.4 as the V2.3 documentation
said would happen.
I haven't tested it, but the needed "architectural" changes were
added in V3.0. There is now an OA$DATA:ATTENDEE_OVERFLOW.DAT file
for long attendee names. Are you saying that this is not working
in V3.0?
_Mike
|
| 484.2 | Are you using MTS? | IOSG::PARTONJ | I was sure I pressed RETURN... | Tue Apr 14 1992 19:28 | 8 |
| Steve,
We're not by any chance talking about MTS addressing being
involved, are we? V3.0 TM will handle long addresses but cannot handle
the case when a responding attendee's mail address has been
'Area-routerised' - and is release-noted as such. Sigh...
Jonathan.
|
| 484.3 | a problem found - but does it work anyway? | SHALOT::LAMPSON | If you read this, you're too close! | Tue Apr 14 1992 21:59 | 12 |
| I just tried this on a V3.0 (BL120B - but the SSB kit should be
the same in this area) system and see what the problem might be.
When you send a meeting request to a long attendee name and then
you read the event, the attendee name is cut off on the display.
However, the full address is in the OA$DATA:ATTENDEE_OVERFLOW.DAT
file. There just doesn't seem to be a way to see the whole
address. In addition, I cannot verify if TM works correctly when
the attendee response comes back as Message Router on my test
machine is not configured to send remote mail to anywhere useful.
_Mike
|
| 484.4 | It's functional | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Wed Apr 15 1992 00:40 | 11 |
| I've done quite a bit of testing with the long addresses. The
long addressing now works, no failed delivery notices are
generated. The mail messages always appear to get to the remote
user. That's the part that didn't work in previous versions.
As Jonathon indicated, the response coming back from an ALL-IN-1
user to the scheduler can still generate a "error occurred writing
to the attendee file" message. This is documented in the release
notes.
Dave Zaniewski
|
| 484.5 | Script example | IOSG::PARTONJ | I was sure I pressed RETURN... | Wed Apr 15 1992 11:49 | 17 |
| Mike,
Re -.3, the following would do it:
FOR CAL$ATT_OVERFLOW with .ATTENDEE_KEY <=> "PARTON" AND -
.ATTENDEE_NAME <=> "XXXXX" DO -
GET #TEXT = .ATTENDEE_NAME\\-
.TEXT 24,1,#TEXT\\-
.PAUSE 1
...there's nothing like this in the base product's scripts, since this
file is exclusively manipulated from the code-level.
Regards,
Jonathan.
|
| 484.6 | I'm confused | SHALOT::LAMPSON | If you read this, you're too close! | Wed Apr 15 1992 17:28 | 20 |
| I'm somewhat confused. My memory (however faulty it might be)
seems to be that sending mail to long attendee names worked in
V2.3 and V2.4 when creating an event. It is just that the path
to the user was lost so that things like Mail to Attendees,
rescheduling and canceling did not work.
So, the "fix" of having an overflow file was so that the event
and its attendees could be properly manipulated once it was
scheduled.
Also, just before my test system crashed, I was poking around the
ATTENDEE file to see what the pointer record to the overflow file
looked like. I noticed that the text in the attendee field (part
of the key) was the first 25 characters of my long attendee name
followed by a ~ character and a 4 digit uniquifier. However,
since I typed my attendee list in lower case, the field is in
lower case! Ouch! I'm amazed I got this far considering that
ALL-IN-1 doesn't work with lower case key fields.
_Mike
|
| 484.7 | lowercase is a problem | IOSG::PARTONJ | I was sure I pressed RETURN... | Thu Apr 16 1992 15:47 | 13 |
| Mike,
It looks like you're right: lowercasing is a problem in as much as
the event is scheduled and the attendee can reply to the event (return
address now in uppercase) but the scheduler will encounter the
'error writing to attendee file' when reading the reply. I will
endeavour to ensure this receives attention in the near future. The
workarond in the meantime is to modify form SCHDMA and set the FMS
attribute on scrolled region ATENDE to UPPERCASE.
Apologies,
Jonathan.
|