[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

225.0. "Auto_forwarding" by NCBOOT::HARRIS (oooppps) Thu Mar 12 1992 22:36

    has anyone come across this senario before - or have an idea for a
    solution
    
    	3 machines 	profsA	VAXA	profsB
    	2 users		usera	userb
    
    	userb's ALL-IN-1 account is autoforwarded to  profs account on
    machine profsB.
    
    	we keep getting delivery failures when usera sends electronic mail
    to userb.  there is a security feature on the profs machines that says
    that  mail cannot be accepted from another profs machine from this
    particular gateway.
    
    what the customer has asked me to lookinto is whether we can modify the
    way autoforward works -or write a script that will.  what they want to
    do is have the mail actually stop in ALL-IN-1 and pick up the ALL-IN-1
    users name etc., and then send the mail along as if it came from the
    ALL-IN-1 account(userb) and not the original sender (usera).
    
    so - anyone seen this before?  does it seem possible?  or am i
    dreaming?				ann

T.R	Title	User	Personal Name	Date	Lines
225.1	yes!	FORTY2::ASH	Grahame Ash @REO	`Fri Mar 13 1992 10:35`	17
	Ann, the short answer is, undoubtedly, yes. Exactly what you need to do may depend on exactly what you want to achieve. One way of getting it to work is to turn off AF, and then run a regular batch job which calls a script which reads userb's mail and sends it to the Profs system. Will Mail Forward be enough? Or do you want to make it appear if it actually originated at userb? > what the customer has asked me to lookinto is whether we can modify the > way autoforward works -or write a script that will. You can't change the way AF works - that's buried in the code. Another possibility is to do something as the mail is delivered. Change userb's MAIDES to be FORWARD and write an OA$LIB:FORWARD.COM which does the necessary (though this might be a bit painful for local users sending to userb. I'm sure some good advice will be in the following replies . . . grahame
225.2	Use the batch approach	SIOG::T_REDMOND	Thoughts of an Idle Mind	`Fri Mar 13 1992 19:27`	13
	Most customers that I have seen modify the autoforward option use the batch job approach. The menu option for AF writes the name of the user into an AUTOFORWARDING data set. A batch job, somewhat like the Mail jobs in that it resubmits itself to run every hour or so, runs through this data set, NEWDIRs to each user found, reads new mail and files it into a folder called "READ MAIL", and then calls MAIL FORWARD to forward each message to whatever mail destination the user has entered. The majority of customers that change autoforward do it to get around the problem (in their eyes) that autoforward does not leave a copy of messages in the original user's cabinet. Tony
225.3	FROM field may be wrong	IOSG::TALLETT	Mit Schuh bish hi	`Mon Mar 16 1992 08:27`	6
	Don't forget that if you REPLY on the IBM system, it will probably send it back to the ALL-IN-1 system, rather than the originator. Regards, Paul
225.4		NCPROG::HARRIS	oooppps	`Mon Apr 06 1992 20:27`	7
	hi - another idea on this. is it possible to modify AUTOFORWARD to send a message out each time a message is rec'd. instead of just the first time a user sends a message? ann
225.5	Try again using different words?!	FORTY2::ASH	Grahame Ash @REO	`Wed Apr 08 1992 11:38`	10
	> another idea on this. is it possible to modify AUTOFORWARD to send a > message out each time a message is rec'd. instead of just the first > time a user sends a message? ann, Er, are you getting AUTO-FORWARD confused with AUTO-REPLY (which only gets executed once/sender)? Or is it just me who's confused? grahame
225.6	slight brain cramp	NCCODE::HARRIS	oooppps	`Wed Apr 08 1992 15:57`	8
	re -.1 -.2 er ah, well... yea, i think i was confused. i meant autoreply. sorry 'bout that chief. ann
225.7	ALL-IN-1 Personal Assistant...	HYTIDE::CREAMER	Keep a low profile	`Wed Apr 08 1992 16:39`	9
	Ann, You might wish to look at the ALL-IN-1 Personal Assistant. It might do what you want. Jack Ex-Officio APA_Developer
225.8		NCBOOT::HARRIS	oooppps	`Fri Oct 02 1992 21:44`	7
	this was solved at the cutomer site by writing our own "custom mail forward" form, scps, and com files. thanks to all for their input! ann
225.9		NCBOOT::HARRIS	oooppps	`Fri Oct 02 1992 21:51`	17
	now for another question.... customer thinks the previous resident may have submitted an SPR, but no one knows for sure. So here's the question/concern... userA sets up an AF on the ALL-IN-1 account to their PROFS account (or any non-ALL-IN-1 mail system). when userA is sent an ALL-IN-1 that has userA listed as a CC: , when userA reads this message on the PROFS system, userA is now shown as the only TO: name. all other recipients are removed from the message. customer is using SOFTSWITCH as a gateway for ALL-IN-1 to non ALL-IN-1 systems. Could it be in SOFTSWITCH, or is this the way that AF works? should i have the customer SPR this? thanks - ann
225.10	can't have a single CC on an envelope	FORTY2::ASH	Grahame Ash @REO	`Mon Oct 05 1992 09:50`	17
	I think that ALL-IN-1 is doing this, because of the way that auto-forward works currently. If a message is being auto-forwarded back to MR by the Fetcher (as in this example), A1 creates a new envelope, with only the new address (the PROFS one in this case) on it. The original message file is sent with it - this will show USERA as a CC with an ALL-IN-1 address. As there is only a single recip on the envelope, it has to be a TO. This is (or was when the fix was put in!) a rule in MR (you can see that it looks silly to have a message with just a CC and no TO? Well, maybe!). But it looks as if either the PROFS gateway, or PROFS itself, is using the envelope address for display purposes - this is usually not recommeneded (users should be shielded from networky addresses). Perhaps there's something on this in the MAILbus conf on Forty2? It may be fixed, or fixable, there - I don't think ALL-IN-1 can do anything. grahame