[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

526.0. "Auto-forward and PROFS private or restricted mail bypass Auto-forward" by GIDDAY::SETHI (Man from Downunder) Tue Apr 21 1992 06:05

    G'day,
    
    A customer has Version 2.3 of ALL-IN-1 and Version 5.4-2 VMS.
    
    The customer has a PROFS gateway installed and wants to prevent messages
    being Autoforwarded if the Mail sent has the "RESTRICTED" or "PRIVATE" 
    field set the PROFS system sets the fields.
    
    I have basically told him how the AUTO-FORDWARD machanism works and
    what field is set in the users profile (PROFIL.MAIL_FORWARD [OA$USER]
    and the others 2 to 4).
    
    What happens in the "Black Box" before the mail is delivered ?
    
    My guess is :-)
    
    1. Mail sent to user who has AUTO-FORWARD set
    2. Mail sub-function "black box" checks the recipient's PROFILE to see
       if the MAIL_FORWARD field(s)
    3. If the fields are set then place the message (pointer) in the mailbox 
       (PENDING.DAT) of the person(s) they have forwarded the message to and 
       increment the mail count
    
    Point 2. is where the problem arises what can the customer do to bypass
    AUTO-FORWARD if the PROFS mails is "RESTRICTED" or "PRIVATE" ?
    
    Also does AUTO-FORWARD work as above in version 3.0 of ALL-IN-1 ?
    
    Thanks
    
    Sunil
T.RTitleUserPersonal
Name		DateLines
526.1 A brief history of auto-forwardAIMTEC::WICKS_AMore Ship dates than actual ShipsTue Apr 21 1992 15:1213
    Sunil,
    
    not quite - firstly was the auto-forward field really that long in
    v2.3? (my memory fails me this early).
    
    Secondly an auto-forwarded message never gets anywhere near the Pending
    file of the recipient because the Fetcher spots the auto-forward and
    reposts the partly unpacked message (the envelope) in the Sender
    queue with the new address specified.
    
    Regards,
    
    Andrew.D.Wicks
526.2Looked at the wrong version !!!GIDDAY::SETHIMan from DownunderThu Apr 23 1992 03:0812
    Andrew,
    
    >not quite - firstly was the auto-forward field really that long in
    >v2.3? (my memory fails me this early).
     
    You are right I was looking at the auto-forward on the Version 2.4
    system.  It had got upgraded and I forgot.
    
    Thanks,
    
    Sunil
526.3NON_FORWARDABLEIOSG::SHOVEDave Shove -- REO-D/3CMon Apr 27 1992 11:096
    You could have your gateway set the NON_FORWARDABLE attribute.
    
    (Use MB$TOOLS:MRNBSDMP to see what element gets set in the NBS message
    when NON_FORWARDABLE is set in ALL-IN-1).
    
    Dave.
526.4If for some reason that doesn't workWAYLND::HOWARDBen. It should do what people expect it to doTue Apr 28 1992 17:3916
    Dave has the answer, I would expect, since he is years ahead of most
    of us in this area.  Failing that, you might try an alternate MTS.  I
    put an example of this basic concept in note 2874 in the ALL-IN-1_V24
    conference.  One drawback is that SUBSCRIBERS mail probably won't get
    delivered at all, but only for users that have autoforward set, since
    you would change the MAIDES field for the users that set autoforward,
    and change it back to ALL-IN-1 when they cancel autoforward. (I'm still
    trying to push this piece of code which nobody seems to want ;-)).
    
    I didn't quite follow this part in .0:
    
    �    I have basically told him how the AUTO-FORDWARD machanism works and
    �    what field is set in the users profile (PROFIL.MAIL_FORWARD[OA$USER]
    �    and the others 2 to 4).
    
    Ben