| Hi,
I'm not sure if you've figured this out already, but here's how to
reproduce the problem at will:
1. Create a conference.
2. Add the ALL-IN-1 System Manager as a member - (MANAGER).
3. Mail Conference Members.
4. Hey presto - when you confirm you wish to send the mail an ACCVIO!!
Cheers,
Russell. (IOSG Support)
|
| I have found a few problems with GPC MM on a customer system:
The VMS and ALL-IN-1 username are the same and the mail address in the conf are
all the same format - node::vms_user. If the GPC member name matches the other
two and MM is used, the mail goes to ALL-IN-1. If the GPC member name is
different, the mail for that user goes to VMS mail.
We also found that MM sends mail to all the members except the user doing the MM
function. Is this intended?
Dave
|
| I have a trace log from the customer and it appears that GOC is designed to skip
the sender when doing an MCM - here are pieces of the trace log, the first with
a user that gets the mail and the second with the sender not getting it.
![SYMBOL] Symbol: #OAN_ADDRESS, Value: OBOA::DMSTCLAIR
![SYMBOL] Symbol: #OAN_CHECK_USER, Value: OBOA::LCWILSON
![SCRIPT] IF Operation starting
![SCRIPT] .IF condition #OAN_ADDRESS EQS #OAN_CHECK_USER is FALSE
![SCRIPT] Null ELSE clause detected
![SCRIPT] OAN$MAIL_MEMBERS Line 29: OA$FAO NOTES$_MCM_SENDING_MAIL, "OA$DISPLAY"
! , #OAN_MEMBER
![FUNC] Function: OA$FAO, Cmd line: NOTES$_MCM_SENDING_MAIL, "OA$DISPLAY", #OA
! N_MEMBER
![A1LOG] Entry: %OA-I-LOGFUN, Function: OA$FAO NOTES$_MCM_SENDING_MAIL
! , "OA$DISPLAY", #OAN_MEMBER
![SYMBOL] Symbol: NOTES$_MCM_SENDING_MAIL, Value: Addressing message to member !
! AS
![SYMBOL] Symbol: "OA$DISPLAY", Value: OA$DISPLAY
![SYMBOL] Symbol: #OAN_MEMBER, Value: dmstclair
!
![SYMBOL] Symbol: #OAN_ADDRESS, Value: OBOA::LCWILSON
![SYMBOL] Symbol: #OAN_CHECK_USER, Value: OBOA::LCWILSON
![SCRIPT] IF Operation starting
![SCRIPT] .IF condition #OAN_ADDRESS EQS #OAN_CHECK_USER is TRUE
![SCRIPT] THEN Operation starting
![SCRIPT] OAN$MAIL_MEMBERS Line 28: .GOTO LOOP_FOR_AN_ADDRESS
![SCRIPT] OAN$MAIL_MEMBERS Line 23: NEXT_LIST "OA$TEMP:OAN_MCM_MEMBERS.TMP"
![FUNC] Function: NEXT_LIST, Cmd line: "OA$TEMP:OAN_MCM_MEMBERS.TMP"
![A1LOG] Entry: %OA-I-LOGFUN, Function: NEXT_LIST "OA$TEMP:OAN_MCM_MEMBER
! S.TMP"
![SYMBOL] Symbol: "OA$TEMP:OAN_MCM_MEMBERS.TMP", Value: OA$TEMP:OAN_MCM_MEMBERS.
! TMP
![SCRIPT] OAN$MAIL_MEMBERS Line 24: .IF $NEXT_LIST_ITEM EQS "" THEN .GOTO CLOSE_
! MESSAGE
![SYMBOL] Symbol: $NEXT_LIST_ITEM, Value: terry OBOA::DM
But why do I get mail when I send it from GPC under ALL-IN-1 V3.0?
|
| Hi,
I've had a look at the MCM script, and there is code in there to try
and omit the sender from the addressee list. Here are some questions
for you:
1. Are you saying that in some circumstances the sender does in fact
get put on the addressee list?
2. I didn't understand .8 (my fault not yours). Can you expand by
giving examples where the behaviour differs. For the example can you
give:
ALL-IN-1 user name
VMS account name
Conference Member Name
Mail Address (as shown on index of conference members)
Mail address actually put on mail message
Mail address which you think should be put on the message
Cheers
Stuart
|
| This is the info for when LCWILSON was doing an MCM from GPC:
VMS User ALL-IN-1 User GPC Member Mail Mail?
dmstclair dmstclair donna oboa::dmstclair VMS mail
lcwilson lcwilson lcwilson oboa::lcwilson no mail
trainee2 trainee2 trainee2 oboa::trainee2 ALL-IN-1 mail
(we also found that changing GPC member name 'donna' to 'dmstclair' made her
receive that mail through ALL-IN-1)
The message in the OUTBOX had these two address on it:
to: donna (dmstclair@oboa@mrgate)
to: lynn wilson (trainee2)
From VAX Notes, all three users had VMS accounts as their mail address and mail
went to all three users.
From ALL-IN-1 EM a message was sent to the following users:
to: donna (dmstclair)
to: trainee2 (trainee2)
to: dmstclair (dmstclair)
to: lcwilson (lcwilson)
Sorry for the delay in getting this info to you,
Dave
|