T.R | Title | User | Personal Name | Date | Lines |
---|
4106.1 | | IOSG::CARLIN | Dick Carlin IOSG, Reading, England | Sun Apr 24 1994 19:54 | 13 |
| Jay
With regard to your specific questions:
1. They will require a Vax for message router (Transport Service
and Distributed Directory Service)
2. ALL-IN-1 IOS AXP 3.1 does not use Mailbus 400.
With regard to the general issue (eg how to configure the necessary
mixed architecture environment) we have prepared information on this
and I will see if I can get it made available here.
Dick
|
4106.2 | ALL-IN-1 V3.1 and MAILbus400 | IOSG::HOLTD | Dave Holt | Fri May 06 1994 17:46 | 9 |
| ALL-IN-1 will be able to access MAILbus400 through the new XMR gateway (OVMS VAX
only) planned to ship in July this year, coinciding with ALL-IN-1 V3.1 FCS. This
gateway will preserve all X.400 84 attributes most of which will be recognised
by MRIF V2.0 and be stored in the ALL-IN-1 File Cab. TeamLinks Clients should be
able to exploit these X.400 84 attributes given TeamLinks origins working with
DECmailworks.
Regards,
Dave Holt, ALL-IN-1 Product Management
|
4106.3 | XMR later than July | FORTY2::ASH | Mail Interchange Group, Reading | Mon May 09 1994 17:01 | 6 |
| Re .2
Now that XMR has closed Phase 1, its planned ship date is at the end (28th?)
of August.
grahame
|
4106.4 | A VAX is required for remote mail with ALL-IN-1 V3.1 on AXP | IOSG::MARSHALL | A glitch in reality | Mon May 09 1994 18:12 | 8 |
| >> ALL-IN-1 will be able to access MAILbus400 through the new XMR gateway
But ALL-IN-1 V3.1 will still need Message Router, running on a VAX, to do this.
So yes, ALL-IN-1 will require a VAX either in the cluster or network in order
to send mail off-node, whether to X.400 or other Message Routers.
Scott
|