[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

4293.0. "Support of BCCs (Blind Carbon Copy) on reception?" by KOLFAX::WIEGLEB (Cloning the nose) Fri Jun 24 1994 21:23

    A customer is using the MBLINK mail gateway from Amadeus to connect
    Lotus Notes to ALL-IN-1.  The product takes Blind Carbon Copy (BCC)
    recipients on messages to ALL-IN-1 and turns them into Carbon Copy (CC) 
    recipients.  
    
    In talking to the MBLINK support people, they state that they are doing
    this deliberately because ALL-IN-1 does not support BCCs on reception.
    Is this true?  I have been able to find no mention of whether ALL-IN-1
    supports this or not.  To what level does ALL-IN-1 support (or not
    support) BCCs on reception?
    
    I don't care whether ALL-IN-1 can generate BCCs - I just need to know
    the how and when of support on reception.
    
    Thanks much,
    
    - Dave

T.R Title User Personal
Name Date Lines

4293.1 Not until 3.1 AIMTEC::FARLEY::PORTER_T Terry Porter - Customer Support Fri Jun 24 1994 22:43 12

T.R	Title	User	Personal Name	Date	Lines
4293.1	Not until 3.1	AIMTEC::FARLEY::PORTER_T	Terry Porter - Customer Support	`Fri Jun 24 1994 22:43`	12
	ALL-IN-1 IOS does not support blind carbon copy prior to V3.1, which introduces BCC support. Having said that the normal convension when sending from a BCC enabled application to a non-BCC application is to send the BCCs as seperate messages, one message to each BCC recipient, this is how V3.1 deals with this situation. This avoids TO and CC recipients learning about the BCC recipiants, which is whole point of having BCC. maybe the gateway designers should think again :-) Terry

ALL-IN-1 IOS does not support blind carbon copy prior to V3.1, which 
introduces BCC support.

Having said that the normal convension when sending from a BCC enabled 
application to a non-BCC application is to send the BCCs as seperate 
messages, one message to each BCC recipient, this is how V3.1 deals with 
this situation. This avoids TO and CC recipients learning about the BCC 
recipiants, which is whole point of having BCC.

maybe the gateway designers should think again :-)

Terry