RICHARD%NET.EBT.ANRJ.BR@uicvm.uic.edu (Richard Sabah) (07/07/90)
This message is empty.
RICHARD%NET.EBT.ANRJ.BR@uicvm.uic.edu (Richard Sabah) (07/27/90)
I have a question about routing. Let's suppose, I have
the follow configuration.
---> --->
----------- MTA3 ----
| |
---> | |
MTA1 ---------- MTA2 |
| |
| |
----------- MTA4 ----
---> --->
A UA at MTA1 submits a message to users at MTA3 and
MTA4. MTA1 sets the responsability flag and transfers the
message to MTA2. MTA2 will duplicate the message and transfer to
mTA3 and MTA4.
How to prevent MTA3 from receiving the message and
transfering it to MTA4 and vice-versa with the MTA4.
Thanks in advance
Richard Sabah
Embratel
Rio de Janeiro, Brazil
richard@net.ebt.anrj.br
richard%net.ebt.anrj.br@brfapesp.bitnetStef@nrtc.northrop.COM (Einar Stefferud) (07/27/90)
In your situation described below, it is simply a matter of only propigating the responsibility bit with the copy for which the receiving (relaying or delivering) MTA is responsible. The responsibility bit is set on a per recipient basis. All other addresses in any propigated copy must have the responsibility bit turned off for all adresses for which the MTA is not responsible, and all MTAs must not relay or deliver a message to a recipient for which they are not responsible. This is fundamentally what "responsibility" means. Best...\Stef > ---> ---> > ----------- MTA3 ---- > | | > ---> | | > MTA1 ---------- MTA2 | > | | > | | > ----------- MTA4 ---- > ---> ---> > > A UA at MTA1 submits a message to users at MTA3 and > > MTA4. MTA1 sets the responsability flag and transfers the > message to MTA2. MTA2 will duplicate the message and transfer to > mTA3 and MTA4. > How to prevent MTA3 from receiving the message and > transfering it to MTA4 and vice-versa with the MTA4.
rwheeler@pbhya.PacBell.COM (Ron Wheeler) (07/27/90)
Richard, If X.400 works as advertised, AND you have not turned on the disclose other recipients flag, then MTA2 will re-envelope the message and send to MTA3 ONLY the addressees on MTA3. Likewise the envelope that goes to MTA4 will only have the addressees of MTA4. This will prevent the duplicate delivery you have suggested. Ron
khiem@hpinddm.cup.hp.COM (Khiem Ho) (07/27/90)
> Richard, > > If X.400 works as advertised, AND you have not turned on the disclose > other recipients flag, then MTA2 will re-envelope the message and send > to MTA3 ONLY the addressees on MTA3. Likewise the envelope that goes to > MTA4 will only have the addressees of MTA4. This will prevent the duplicate > delivery you have suggested. > > Ron Actually this is not necessarily true. The Disoclosure of Other Recipients is a per message flag, and does NOT necessarily result in removing of other recipient names from the envelope (at least as defined by the stds and implemented in a number of implementations). All this flag does is to prevent, in theory, the MTA from giving the other names to the UA; but this feature, as far as I know, is not really well-understood or useful, and caused more confusion than anything else. It was an attempt to provide Bcc feature by the MTA. As stated in some previous message, setting the Responsibility flag as appropriate for each recipient will do the job. Khiem
tim@piglet.planet.bt.co.uk (Tim Maude,B81 G61,6734,) (08/06/90)
> > I have a question about routing. Let's suppose, I have > the follow configuration. > > > ---> ---> > ----------- MTA3 ---- > | | > ---> | | > MTA1 ---------- MTA2 | > | | > | | > ----------- MTA4 ---- > ---> ---> > > > A UA at MTA1 submits a message to users at MTA3 and > MTA4. MTA1 sets the responsability flag and transfers the > message to MTA2. MTA2 will duplicate the message and transfer to > mTA3 and MTA4. > > How to prevent MTA3 from receiving the message and > transfering it to MTA4 and vice-versa with the MTA4. > > > Thanks in advance > Richard Sabah > > Embratel > Rio de Janeiro, Brazil > > richard@net.ebt.anrj.br > richard%net.ebt.anrj.br@brfapesp.bitnet When MTA2 duplicates the message, it does not make an exact copy, it should make two copies, one which contains the reciepients on MTA3, and one for MTA4. Of course this is only in the envelope, the contents are not touched. Thus MTA3 does not know that MTA4 should get a copy and so does not route a copy to it. ------------------------------------------------------------------- Tim Maude RT7431 email: tim@planet.bt.co.uk British Telecom Research Laboratories phone: +44 473 646734 Martlesham Heath fax: +44 473 642163 Ipswich IP5 7RE U.K. -------------------------------------------------------------------