| I think the problem is that we only put addresses on that we can decode
from the VMSsnail message. Since the callable interface (in spite of
Ian H's pleadings) only returns what the user types, we often can't
work out DLs or nicknames (i.e. locally defined logicals.) I'm sure you
knew that already, but I expect that when we can't work out the
address, we just ignore it. Presumably your message had no
comprehensible addresses at all.
Of course if you use MRGATE, and the option is turned on, you get the
friendly attachment with the original (as typed by the VMSmail user)
and equally useless to MRGATE address list, but at least you can use
your brain to work out who the users might be.
I did argue that we ought to be able to guess some of the addressees by
parsing the MRGATE attachment, but I couldn't convince anyone to write
the code....
Graham
|
| Hi Graham,
Yes, understood - and I realise that MRGATE would do the trick. (Perhaps if we
ever have instant senders and fetchers installed on Forty2 I'll switch to
MRGATE!).
The message this time had apparently one TO addressee (not me), and 2 CCs -
the sender and someone else. Now we know that VMSmail adds ", sender-name" to
the CC list (if set by the sender), and V Import can therefore identify the
users separated by the comma. It seems to be that if the sender types:
TO: user1
CC: user2 user3
that I will see (after V RN),
TO: user1
CC: user3, sender
But I haven't done any testing to prove it. While V Import is separating the
addresees in the To or CC list it should treat space as a separator, as well
as comma.
Andy,
IPR? I'd love to, but (blush) I don't know how! And I thought I could check to
see if it was known first.
grahame
|