Conference iosg::all-in-1_v30

    I fear that removing the FUN attribute is not easily done in that it is
    not added to the document by a form or script.  The CALENDAR SCHEDULE
    MEETING function does EVERYTHING from obtaining the meeting information
    up to sending the actual mail message.  Adding the FUN attribute is
    done in the middle (okay, toward the end) of this.  All of this is done
    in BLISS.

    There have a number of requests on the part of customers to separate
    the processing of the CALENDAR SCHEDULE MEETING function to act more
    like the MAIL CREATE.  This would allow the user and/or programmer to
    control when the meeting request actually is sent as well as performing
    the 'mutilation' you describe.

    I realize that the customer would not appreciate it but you might want
    to ask if they'd accept having a second mail message for the events
    which would then be forwardable.  You could add a CALENDAR
    MAIL_TO_ATTENDEED as a part of the TMAPMEC script for those meetings
    which require the desired forwardablity.  Or, you could check for users
    known to be 'forwarders' (easy to do for the local users by checking
    the MAIL_FORWARD field in the profile).

    Good luck,
    don

    
    It is my undrstanding that one reason the mail message is NOT forwarded
    to the autoforward user, is that when this message is read the meeting
    is also entered into the user calendar.  If the message is forwarded
    there is a problem in that the meeting would then be added to the wrong
    calendar (ie not the user that was scheduled but the user (s)he has
    forwarded mail to). If this occurs, then that user would likely not be
    able to access the meeting, as (s)he is not the attendee or the scheduler
    of the meeting.  This may not be exactly what occurs, but it is
    generally why these messages are not forwarded.
    
    
    Hope this is helpful,
    
    Faith
    

and when the recipient replies to the request, the reply arrives back at the 
originator's Calendar from someone who wasn't invited!

grahame

	Faith is correct.  Most of the mail functions that exist today deal very
specifically with one or more of the data structures for a particular ALL-IN-1
user.  In the case of the CALREMOTE function, that would be the calendar of a
specific user, as well as their File Cabinet (since scheduling meetings and
replying to them all involve sending mail back and forth).

	The same applies to archiving functions.  Should ALL-IN-1 not intercept
those mail functions, but simply allow them to be autoforwarded, documents being
restored from archive, for example, would end up in the wrong user's File 
Cabinet.

	In trying to understand why you might want meeting notices forwarded to
someone else, it would seem that this "someone else" should have access to the
other user's calendar -- and perhaps mail as well.  That is, if you wish to
autoforward meeting requests, I ass/u/me that you would also grant the
"forwardee" the ability to respond to those meeting requests.  Now, you've got
another problem, since you would need some way to insure that the "forwardee"
has Set Owner access to the original user's calendar.

	As you can tell, between mail access, calendar access, and general data
access, you can end up in quite a bind if you simply allow auto-forwarding of
all mail.  A better solution would be to determine precisely what it is you want
to do (i.e., not "auto-forward all mail", but something like "allow other users
to be able to respond to meeting requests for a user"), and look at other ways
to do that.  Some of it already exists in V2.4 (e.g., Set Owner); some of it
exists in V3.0 (e.g., Set Mail User); and some of it exists in other customized
solutions that we could provide to your customer.

	F

    Hi:
    
    What I was trying to do was find a means of autoforwarding a users mail
    to their ALL-IN-1 MAIL account on a PC LAN.  Since we do not have a
    decent calendaring solution for the PATHWORKS-TEAMLINKS environment, we
    were forced to use ALL-IN-1 IOS for the calendar function (and only for
    the calendar function).  I'll be the first person to agree that this is
    an awkard and difficult solution, but it is the only configuration that
    we could come up with that would provide this function in French.  When
    DEC decides what our LAN direction for calendaring is going to be and
    subsquently provides language variations support...
    
    Thanks for your responses.
    
    P.S.
    
    Paper mail has provided a work-around of sorts for this problem, but I
    am eagerly looking forward to a LAN product for calendaring that has
    links to ALL-IN-1 MAIL.
    
    
    

    Hello,
    
    	I have exactly the same requirement as in .-1.
    
    	As long as we do not have corporate wide TM solution for TeamLinks, 
    ALL-IN-1 Mail users , we will have to depend on IOS TM.  Thus 
    autoforwarding of meeting notices to ALL-IN-1 Mail users will be 
    required.  It is not an elegant solution but we have no choice.
    
    Thanks & Rgds,
    Cecilia