[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

2132.0. "VAXmail forwarded to ALL-IN-1 IOS & distribution lists" by MSBCS::KING (AVS BXB/LTN System Management Group DTN:293-5677) Wed Jan 20 1993 21:58

I have a user who wants to see all of the recipients of a message that is 
received in ALL-IN-1 IOS when it is originally addressed to her VAXmail account.
(i.e. node::user).  She has VAXmail forwarded to ALL-IN-1 IOS via MRGATE. When a
message arrives via MRGATE, and she wants to show header (SH) it lists only 1 
recipient, herself as node::username.

Is this a function of MRGATE?  Does MRGATE stip out all of the other recipients
from the header of the message?  I have noticed that messages which do not go
through MRGATE, namely they are not sent from VAXmail, include all of the 
recipients in the header. I have v3.2 Mrgate running on a remote node and
it is currently configured as such:

Maximum number of recipients at a node is 1.

The version of ALL-IN-1 IOS is v3.0.



Thanks,


Bryan

T.R	Title	User	Personal Name	Date	Lines
2132.1	They are added as an attachment, but not in the header!	BRUMMY::MARTIN::BELL	Martin Bell, TCC, Birmingham UK	`Thu Jan 21 1993 08:19`	23
	Bryan, on the previous version of MRGATE (v3.1), various combinations of TOs and CCs were included in the ALL-IN-1 mail header (as seen via SH). I can't remember the exact circumstances, but it meant that sometimes users didn't realise that someone else had in fact received the message, so they forwarded (the duplicate) on. On MRGATE v3.2, as a partial get-around, a full list of addressees was appended onto the message as an attachment, so that you could see all the TOs and CCs as initially intended. Unfortunately this didn't get included on the ALL-IN-1 mail header, so you can't see them with SH. Another problem is that every single mail message sent via MRGATE ends up with an attachment, which can double the number of records in the SDAF file. I am not from engineering, so i can't tell you when things will all get sorted out. Presumably whenever ALL-IN-1 becomes fully X.400 complient, but you need to ask that question in A1INFO!! You could also try the MAILbus conference to see what the next version or MRGATE will do! mb
2132.2	Not an ALL-IN-1 problem	SCOTTC::MARSHALL	Spitfire Drivers Do It Topless	`Thu Jan 21 1993 11:22`	23
	>> Unfortunately this didn't get included on the ALL-IN-1 mail header How could it possibly be included in the mail header? MRGATE sends a message with one addressee, a text body part, and a text attachment. There is nothing "special" about the attachment that tells ALL-IN-1 it is really a list of addressees. ALL-IN-1 just treats it as an ordinary attachment; what else can it do? i can't tell you when things will all get sorted out Unfortunately, there is nothing that we can sort out on this one. It's up to MRGATE to put the correct message header on its messages. ALL-IN-1 can't arbitrarily decide that some messages have the "wrong" header and so change them. I doubt if it would even be possible to put in special code to check for messages coming from MRGATE. >> Presumably whenever ALL-IN-1 becomes fully X.400 compliant X.400-ness has nothing to do with it: again, the problem isn't at the ALL-IN-1 end. As Martin said, contact the Mailbus people to see what MRGATE is going to do in the future. Scott
2132.3	VMSmail import	IOSG::NEWLAND	Richard Newland, IOSG, REO2-G/L2	`Thu Jan 21 1993 14:06`	6
	If you use the EM V (VMSmail import) option to bring your VMS mail into ALL-IN-1 then all the addressing information is preserved. Richard
2132.4		BRUMMY::MARTIN::BELL	Martin Bell, TCC, Birmingham UK	`Thu Jan 21 1993 14:39`	15
	Re: .2 Oops, sorry Scott, i had my MAILbus head on, so i was implying that ALL-IN-1 could do something about a problem that MRGATE has. I suppose what i really was getting at is that eventually, when ALL-IN-1 and Message Router (hence MRGATE) all talk X.400 properly then things will be much better. Re: .3 Watch out though, using EM V can mess up your date/timestamps, and you can't reply to the sender properly (i think). mb
2132.5	VMSmail at fault too....	IOSG::PYE	Graham - ALL-IN-1 Sorcerer's Apprentice	`Thu Jan 21 1993 15:26`	9
	Actually it isn't MRGATE that has the problem (or at least it isn't only MRGATE!) since VMSMail doesn't fully expand addresses on the message. IF you've addressed it using a personal nickname (i.e. a logical in VMSMail speak) or a distribution list. You can see this on the MRGATE attachments. There's an earlier notes stream in here about the MRGATE attachments. Graham
2132.6		FORTY2::ASH	Grahame Ash @REO	`Fri Jan 22 1993 13:55`	16
	<<< Note 2132.4 by BRUMMY::MARTIN::BELL "Martin Bell, TCC, Birmingham UK" >>> >Watch out though, using EM V can mess up your date/timestamps, and you >can't reply to the sender properly (i think). Well, maybe. The date you see in indexes (modified) is set to the time of the V, but the created date is preserved, so you'll see it OK when you read it. I'm not aware of any problem with reply to sender, though, of course, you can't reply to all recips unless they were specified in full on the VMSmail To: line (and comma-, not space-separated, I believe). Yes, I hate this problem, and always use EM V . . . (and with my nodename I have to repeat that it's not MRGATE's fault!) grahame