[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

748.0. "Auto Forward to Remote users" by SUBWAY::ROTHMAN (Dr. Daystrom did NOT design Alpha!) Fri May 22 1992 22:33

    I need help with the following Auto-Forward problem...
    
    User A sends mail to User B who is AF to User C
    
    When User A and User B are on the same node User B's name appears in
    the message header 
    
    When User A and User B are on different nodes User C's name appears in
    place of User B...
    I have been told that this is supposed to happen and that All-IN-1 was
    designed this way...
    My customer does not desire this feature...
    In the past my customer had spoken to someone at Atlanta who faxed a
    piece of paper describing a work-around....
    
    Unfortunately, that paper is nowhere to be found!  I called Atlanta but
    no one knows what I am talking about.
    
    I seem to remember it may have been a STARS article.  
    The work-around went something like this...
    	Create a script with the code to address User C 
    	Modify User B's profil to have this script as a Mail DEstination
    
    Thanks for any help

T.R Title User Personal
Name Date Lines

748.1 Autoforward Article with workaround AIMTEC::LAMBERSON_M Fri May 22 1992 23:01 102

T.R	Title	User	Personal Name	Date	Lines
748.1	Autoforward Article with workaround	AIMTEC::LAMBERSON_M		`Fri May 22 1992 23:01`	102
	The following article may be what you are looking for. Mail Auto-forwarded Reflects Forwarding Address As Recipient COPYRIGHT (c) 1991, 1992 by Digital Equipment Corporation. ALL RIGHTS RESERVED. No distribution except as provided under contract. PRODUCT: ALL-IN-1 V2.3, V2.4 SOURCE: Customer Support Center/Atlanta USA PROBLEM: User1 on nodeA sends an electronic mail message in ALL-IN-1 to to two addressees, one local and one remote. User2 on nodeA is a local address and User3 on nodeC is a remote address. The local addressee, User2, has their mail autoforwarded to another local user, UserX, on nodeA. When the mail message gets to the original remote addressee, User3 on nodeC, the header reflects the autoforwarded local user, UserX, as an addressee of the message on the TO: field rather than the original local addressee, User2. Ex: User1 addresses an EM message as follows: TO: USER2 TO: USER3@a1@nodeC USER2 has set autoforward to USERx. When USER3 receives the messages it is addressed as follows: TO: USERx TO: USER3@a1@nodeC This is not the desired behaviour when a user autoforwards mail. This setup is used when a Manager would like to auto-forward all mail sent to him to go to a secretary. But, (s)he would not like the other recipients of the mail to see the secretary as the addressee rather than himself. SOLUTION: This is not a problem but instead is the intended design of the auto-forward mechanism in ALL-IN-1 Mail. When a user auto-forwards mail in ALL-IN-1, mail sent to that user, reflects the address of the user that the mail is forwarded to as the addressee who actually received the mail. Rather, than use the autoforward mechanism to forward the users mail to another user, you could implement a special mail destination. This would allow you to forward mail to another user using VMSmail and the forwarded user address would not be reflected in the ALL-IN-1 message. For details on creating a unique routing mechanism by creating a mail destination, similar to VMSMAIL, refer to the ALL-IN-1 Application Programming guide, pg 17-10. One example, could be as follows: Copy the OA$LIB:SPECIAL.COM procedure to OA$LIB:TESTFOR.COM to create a new mail destination TESTFOR. Edit the copy OA$LIB:TESTFOR.COM as follows: Find the lines that read: $ REALLY_SEND: $ ASSIGN/USER NLA0: SYS$OUTPUT $ ASSIGN/USER NLA0: SYS$ERROR $ SET DEFAULT 'HOME_DIR $ MAIL/SUBJ="''SUBJ'" 'FILE' 'TO' $ IF $STATUS THEN GOTO DONE $ Change these to read as follows: $ REALLY_SEND: $ ASSIGN/USER NLA0: SYS$OUTPUT $ ASSIGN/USER NLA0: SYS$ERROR $ SET DEFAULT 'HOME_DIR $ MAIL/SUBJ="''SUBJ'" 'FILE' MRGATE::"A1::UserX" $ IF $STATUS THEN GOTO DONE $ NOTE: You have changed the mail address from the variable symbol, to a specific user address. The result is that whenever mail is sent to a user that has the TESTFOR designated as his mail destination, the mail will instead go to the user address specified in this file. But, in this case, VMSmail is used to send the mail to forward the mail to the user in ALL-IN-1 through MRGATE. To forward an ALL-IN-1 users mail to a specific user using this mechanism, have the user change his mail destination in his user profile to indicate the new destination (ie in this example, TESTFOR).

    The following article may be what you are looking for.
    
Mail Auto-forwarded Reflects Forwarding Address As Recipient


COPYRIGHT (c) 1991, 1992 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

PRODUCT: ALL-IN-1 V2.3, V2.4

SOURCE: Customer Support Center/Atlanta USA


PROBLEM:

User1 on nodeA sends an electronic mail message in ALL-IN-1 to 
to two addressees, one local and one remote. User2 on nodeA is
a local address and User3 on nodeC is a remote address. 
The local addressee, User2, has their mail autoforwarded to 
another local user, UserX, on nodeA.

When the mail message gets to the original remote addressee,
User3 on nodeC, the header reflects the autoforwarded local
user, UserX, as an addressee of the message on the TO: field
rather than the original local addressee, User2.

Ex:

  User1 addresses an EM message as follows:

         TO: USER2
         TO: USER3@a1@nodeC
 USER2 has set autoforward to USERx.  

 When USER3 receives the messages it is addressed as follows:

         TO: USERx
         TO: USER3@a1@nodeC

This is not the desired behaviour when a user autoforwards mail.
This setup is used when a Manager would like to auto-forward all
mail sent to him to go to a secretary.  But, (s)he would not like 
the other recipients of the mail to see the secretary as the 
addressee rather than himself.

SOLUTION:

This is not a problem but instead is the intended design
of the auto-forward mechanism in ALL-IN-1 Mail.

When a user auto-forwards mail in ALL-IN-1, mail sent to that
user, reflects the address of the user that the mail is forwarded 
to as the addressee who actually received the mail.

Rather, than use the autoforward mechanism to forward the users
mail to another user, you could implement a special mail
destination.  This would allow you to forward mail to another
user using VMSmail and the forwarded user address would not be
reflected in the ALL-IN-1 message.  For details on creating a
unique routing mechanism by creating a mail destination, similar 
to VMSMAIL, refer to the ALL-IN-1 Application Programming guide,
pg 17-10.

One example, could be as follows:

Copy the OA$LIB:SPECIAL.COM procedure to OA$LIB:TESTFOR.COM 
to create a new mail destination TESTFOR.

Edit the copy OA$LIB:TESTFOR.COM as follows:

Find the lines that read:

$ REALLY_SEND:
$       ASSIGN/USER NLA0: SYS$OUTPUT
$       ASSIGN/USER NLA0: SYS$ERROR
$       SET DEFAULT 'HOME_DIR
$       MAIL/SUBJ="''SUBJ'" 'FILE' 'TO'
$       IF $STATUS THEN GOTO DONE
$

Change these to read as follows:

$ REALLY_SEND:
$       ASSIGN/USER NLA0: SYS$OUTPUT
$       ASSIGN/USER NLA0: SYS$ERROR
$       SET DEFAULT 'HOME_DIR
$       MAIL/SUBJ="''SUBJ'" 'FILE' MRGATE::"A1::UserX"
$       IF $STATUS THEN GOTO DONE
$

NOTE: You have changed the mail address from the variable symbol,
to a specific user address.  The result is that whenever mail is
sent to a user that has the TESTFOR designated as his mail destination,
the mail will instead go to the user address specified in this file.
But, in this case, VMSmail is used to send the mail to forward the
mail to the user in ALL-IN-1 through MRGATE.


To forward an ALL-IN-1 users mail to a specific user using this mechanism, 
have the user change his mail destination in his user profile to indicate
the new destination (ie in this example, TESTFOR).