[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

1175.0. "mail to SUBSCRIBERS: after TeamRoute install" by TPOVC::ROGERTSAI () Tue Aug 04 1992 11:28

Hi,
  I just install "TeamRoute for ALL-IN-1". And the mail destination field
of most users is changed form "ALL-IN-1" to "TMR" to receive TeamRoute routing 
    package. They can receive mail without problem. The oa$main.exe is
    tailored. 
  But the mail to system distribution list "Subscribers:" can not be delivered
to those users whose mail destination filed is set to "TMR".
  It seems that the script to handle sending mail to "subscribers" does not
deliver mail to those non-"ALL-IN-1" destination field users, even "TMR".

   Any idea  and suggestion ?

Regards,
Roger

T.R	Title	User	Personal Name	Date	Lines
1175.1		IOSG::MAURICE	Ceci n'est pas une note	`Tue Aug 04 1992 11:51`	10
	Hi Roger, I wonder if you had the wrong conference open ;^) Anyway in TeamRoute for ALL-IN-1 there is a special system distribution list called @TMR_SUBSCRIBERS which users have to use instead. Cheers Stuart
1175.2	Old habits will be hard to change	AIMTEC::WICKS_A	DEC Mail Works for ME sometimes	`Tue Aug 04 1992 23:59`	10
	Stuart, But training them not to use SUBSCRIBERS: is the challenge. Most 'users' probably won't even know TeamRoute is installed on the system and they'll just complain about 'lost mail'. Regards, Andrew.D.Wicks
1175.3	Its been QARed	IOSG::TALLETT	Arranging bits for a living...	`Wed Aug 05 1992 07:49`	14
	I QARed this against a while back against a PFR of ALL-IN-1. Now that we have the "I do/don't want to receive SUBSCRIBER mail" flag in the profile, the code that checks for non-standard mail addresses can go. Of course one would do a conversion procedure for PROFIL that set the "SUBSCRIBER mail" flag to "N" for all non-standard mail addresses, but then the user could change it if they wanted. No commitment implied or expressed... Regards, Paul
1175.4	In the meantime ..	FORTY2::ASH	Grahame Ash @REO	`Wed Aug 05 1992 13:25`	6
	You could customise the mail header forms to look for SUBSCRIBERS: and output a friendly message telling them the new name to use, or, simpler and more brutal (typical, eh?!), just take it out of the list of special mail addresses. grahame
1175.6	architechural point ?	IOSG::WDAVIES	There can only be one ALL-IN-1 Mail	`Wed Aug 05 1992 16:54`	6
	Why do the users need to have a maides of TMR now anyway ? Seems a bit kind-of-hackish... ? Shouldn't it be a stage before MAIDES is invoked... ? Winton
1175.8		FORTY2::ASH	Grahame Ash @REO	`Fri Aug 07 1992 10:03`	8
	> Wouldn't you need a BLISS compiler to modify OA$MAIDES and how many of > the 6 customers that ever bought BLISS will buy TeamRoute for ALL-IN-1? Yes, I did wonder if OA$MAIDES was still stuck in OAGBL or OALLV. Shame. One more vote with Paul in .-1 from me. g
1175.9	A first -pass at a functional spec	IOSG::WDAVIES	There can only be one ALL-IN-1 Mail	`Fri Aug 07 1992 10:33`	24
	ok, then Paul and GASH, At what point do you want these scripts to execute, and if they are used, should the rest of the code operate ? Is it system wide or per-user ? I guess the answer to 1) Send a) At start of users 'manual' Send - otherwise it could operate twice on the mail ? Or is this desirable ? Perhaps before delivery code. Recieving b) Just before delivery - so users own individual processing can be done - although this implies multi-scripts - a single script could multiplex using profile /data file information 2) Should continue to operate as before 3) One each per-system Winton