Transport rule to prevent sending to multiple clients

Hello! I need to create a Transport rule to prevent our staff from accidentally including recipients from both of two of our clients. I.E. I need the rule to examine every message to see if contains both *@domain1.com AND *@domain2.com in either
the To, CC, or BCC fields. Is that possible? I've looked at the options through the GUI and PowerShell and can't seem to find exactly what I'm looking for.
thanks
Ray

Hi,
In Exchange 2010, to prevent your staff from accidentally including recipients from both of two of your clients: domain1.com and domain2.com, you can create a transport rule to achieve this goal.
In Exchange 2007, there is no related Conditions in Transport Rule that can help us to restrict users to send messages to a recipient in the domain1 or domain2.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

Plug-in or Rule to prevent sending a piece of mail meeting certain conditions

I'm looking for a plug-in, rule or process that would prevent me from sending a specific piece of mail. I doubt many people have this issue but sometimes I hit send w/o scrutinizing the "TO" and "CC". It's a bad habit of typing in the start of the name then accepting the first name without inspection. I know the best way is to get into a new habit of checking but I would love to set up some send rules that include conditions that keep me from doing the bone-head move. I've looked at the Apple Mail Rules, Act-On and a few others but everyhting is about organization and recieve. Thanks in advance for any help.

Welcome to Apple Support Communities.
What about unchecking 'Automatically complete addresses' in Mail, Preferences, Composing, Addressing?
That way you MUST type in the full email address.

Powershell script to add multiple domains to a transport rule

I have a transport rule in Exchange 2013 that I created in the EAC (mail flow>rules). it is set so *Apply this rule if.. the sender's domain is.. and then I entered a few domains.
I want to use a powershell script to enter multiple domains into the senderdomainis parameter using the set-transportrule. I would like to do this from a csv input file. The file has header row of domains and then the domains are listed
under it. This is also used successfully in a script that does content and sender id filter additions.
I tried the following:
$allowed = import-csv c:\temp\allowed.csv
$Rule=get-transportrule "safe domain List"
$Senderdomains =$rule.senderdomainis
foreach($row in $allowed)
$Senderdomains +=$row.domain
#Set-Transportrule "Safe Domain List" -senderdomainis $Senderdomains
It just adds a long line of all the domains mashed together without separation.
Any ideas would be helpful.
Thanks.

This isn't the most elegant solution, but I was able to accomplish it with this script:
$allowed = import-csv c:\temp\allowed.csv
$domains=Get-TransportRule "Safe Domain List" | select -ExpandProperty senderdomainis
foreach ($a in $allowed)
$domains += $a.domain
$domainstoadd = $domains | select -Unique
Set-TransportRule "Safe Domain List" -SenderDomainIs $domainstoadd
It's key to note that the column in the CSV file has a heading of "Domain". Basically the script pulls the existing array into a variable so you can add values from the CSV to the array. This creates duplicates,
so the "Select -Unique" is a quick and easy way to eliminate the duplicates.

Hub transport raw HTML code displays when iOS client used to send message

Has anyone else encountered (and hopefully fixed) this problem? I use HTML coding to format the signatures for my staff at the hub transport rule level. Here's an example:
 %%CustomAttribute1%% 
%%Title%% 
Tel:   %%PhoneNumber%% 
Fax:  %%FaxNumber%% 
%%Email%% 
<img border=0 width="240" height="62" src="http://wiglefamily.net/CABVI/CABVILogo.jpg" alt="CABVI Logo"> 
               <a href="www.cincyblind.org">www.cincyblind.org</a>
Disclaimer: The information contained in this electronic mail message may be confidential and protected information intended only for the use of the individual or entity
named above. As the recipient of this information you may be prohibited by State and Federal law from disclosing this information to any other party without specific written authorization from the individual to whom it pertains. If you have received
this communication in error, please notify us immediately and destroy the message and its attachments. 
It looks great when I sent from Outlook or even Android mail clients. However, when sent from iOS mail clients I get the following in the signature:
<html>
<body>
Michael Wigle IT Manager Tel: 513-487-4243 Fax: 513-221-2995
[email protected] [CABVI Logo] www.cincyblind.org Disclaimer: The information contained in this electronic mail message may be confidential and protected information intended only for the use of the
individual or entity named above. As the recipient of this information you may be prohibited by State and Federal law from disclosing this information to any other party without specific written authorization from the individual to whom it pertains.
If you have received this communication in error, please notify us immediately and destroy the message and its attachments.
</body>
</html>
As you can see, the raw HTML code shows but the AD variables populate correctly. Any ideas on a solution for this problem?

See this for the pipeline tracing:
http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
There's a link in that article that takes you to:
http://technet.microsoft.com/en-us/library/bb125018(v=exchg.80).aspx
FYI, I think you're still a bit confused. Once again you said *from* when you meant *to*! :-)
--- Rich Matheisen MCSE&I, Exchange MVP

Send data to multiple clients from a server

My problem statement is this:
A server is created, say X. Multiple clients are created, say A, B & C. If X sends a message to A it should reach only A and should not go to B or C. Similarly if X sends message to B it should not reach A or C. I made a one to one communication with the following code:
//Server
import java.io.*;
import java.net.*;
class X
public static void main(String args[])throws Exception
ServerSocket ss=new ServerSocket(4321);
try
Socket s=ss.accept();
BufferedReader in = new BufferedReader(new InputStreamReader(System.in));
DataOutputStream out = new DataOutputStream(s.getOutputStream());
String str=in.readLine();
out.writeBytes(str+"\n");
s.close();
ss.close();
catch (IOException e){}
//Client A
import java.io.*;
import java.net.*;
class A
public static void main(String args[])throws Exception
try
Socket s=new Socket("localhost",4321);
BufferedReader in=new BufferedReader(new InputStreamReader(s.getInputStream()));
System.out.println(in.readLine());
s.close();
catch(Exception e){}
}But i dont know how to keep track of each client. Because all the clients sockets are created at the same port, ie. 4321. I think thread will help. But even then i dont know how to identify each client. Somebody please help. Thanks in advance.
Edited by: sowndar on Dec 5, 2009 1:21 AM

YoungWinston wrote:
sowndar wrote:
Ok. I think i have to attach an unique ID to each client message. So that, with the help of that ID, the server can identify each client. Have i caught ur point?If you don't mind using a port per client, you could do something like a receptionist taking incoming calls (on 4321 only).
- Hi I'm Client xyz.
- Hi Client xyz, please call me back on port abcd and I'll put you straight through to our server.
Since 4321 is an "open line" you might have to have some sort of ID so that Clients know which return messages are meant for them, but messages on the other ports would all be direct Client to Server. Also, the Server is then is charge of port allocation and communication on the "open" port is kept to a minimum.4321 is the socket that the server is listening to. It's not what the actual communication will be carried out over. Run this, then telnet to port 12345 a few times
public class TestServerSocket {
public static void main(String[] args) throws Exception {
          ServerSocket server = new ServerSocket(12345);
          while (true) {
               Socket socket = server.accept();
               System.err.println(socket.getPort());
}Notice how each inbound connection is allocated a unique outbound socket.

Creation of transport rule to send all external mails through a particular server for a specific user..

HI,
In our Organisation We have a question, is there any possibility to create a transport rule for sending all external mails through a particular server by a specific user.
in our organisation we have exchange 2007 one mailbox server and two hub transport servers...and we are using symantic gate way..

Hi,
Based on my knowledge, we can use the following transport rule to make that except with one user, other users cannot send outbound external emails:
And I’m afraid that there is no Exchange feature to make one specific HUB server rout all external emails.
Because if a Send connector is configured to send messages to an external domain, any Hub Transport server in the organization will route a message for that domain to a source server for that connector to be relayed to the destination domain.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Moderation via Transport Rule and multiple Arbitration mailboxes

Hello,
when using moderation using a Transport Rule (Transport Rule Action "forward the message to addresses for moderation") it is possible to moderate messages sent to recipients outside the exchange organization (Transport
Rule Predicate "Sent to Users Outside The Organization"). This all works perfect so far using a single arbitration mailbox.
Now I would like to add additional arbitration mailboxes for load balancing purposes. As far as I understand, different arbitration mailboxes can configured on the recipients objects which are moderated using the set-<MailEnabledObject> -ArbitrationMailbox
'XYZ'
Now, for the described case above where the recipients are external (internet) and not available within the directory, is there a way to use multiple Arbitration mailboxes anyway and if yes, how ?
Any feedback welcome. Thanks in advance

Hi,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Niko Cheng
TechNet Community Support

Sending mouse pointer co-ordinates to multiple clients

Hi. I used the MouseMotionListener to get mouse pointer co-ordinates and send those values to one single client. Now i want to know how i could send those co-ordinate values to multiple clients at the same time? If i use multi-threading then what all the steps should i do in the run() method???

Hi. I tried another way. Its like this.
I declared two global variables x and y for holding two mouse co-ordinates in class a.
class a {
public static int x = 0;
public static int y = 0;
Now in the main method of one class, I accepted client connections and started the thread like this :
socket = server.accept();
thread= new HandlerThread(socket);
thread.start();
Now in the class HandlerThread this is what i did :
class HandlerThread extends Thread {
private Socket s1;
ObjectOutputStream oos;
public HandlerThread(Socket s) {
this.s1=s;
public void run() {
try
oos = new ObjectOutputStream(s1.getOutputStream());
oos.writeObject(a.x);
oos.writeObject(a.y);
catch(IOException e)
System.out.println("Exception"+e);
At the sender side when i moved my mouse pointer on screen, i was able to get the changing mouse co-ordinates value. But at the receiver side, only the initial value of x=0 & y=0 was obtained. I started two client connections and for both i received only the initial value. Can someone tell me what could be the reason for this?? Plz reply.

Transport rule exchange 2010 not sending reply gets stuck in Queue

I am trying to set up a transport rule in exchange 2010 that will auto reply to a email address that is no longer valid. One of our exec passed away and they want a reply setup to send an automatic message. I read somewhere that the auto reply may not be
the right way to go about this so I was trying to setup a transport rule. I used the wizard to make the rule for conditions 1 all outside email addresses 2 sent to the internal email address specified. Actions 3 Send rejections message to sender with enhanced
status code
Created the message in the rule and gave it a status code 5.7.228 no exceptions and created the rule
Went to an outside email account and sent to the internal users account. It was reported that it was delivered from our mail filter I verified that it did not get delivered to the user then a few min later the reply appears in the queue viewer on exchange
a few min later it is gone I figured it worked but when I checked it did not get delivered to the outside email address or seen going through the mail filter. I'm missing something I know its right there somewhere just looking to long and I cant see it.
This is baffling me as to what happened? What account is it sent from? The user, administrator or do I need to create a postmaster account for it to work? I am a one man shop and it get kind of baffling some times
Thanks in advance for any help I will keep looking for the answer
John R
John R

Hi John,
From your description, I would like to verify the following things for troubleshooting:
1. Please verify if users can send messages to external email addresses.
2. Please check if internal users can receive the rejection messages.
Best regards,
Amy Wang
TechNet Community Support
Yes users can send to external address and internal users receive NDR rejection messages
The system has been in production for 2 years. I'm just trying to find the best way to setup a auto reply for users that are no longer with us or have moved on.
Thanks for your help
John R

Create Transport rule for restrict message size and send a rejected message CC: to Administrator

I want to create a Exchange Transport rule for message size restriction (10 MB) when message size is exceed to 10 MB it rejected by the Exchange server and
also rejected message CC: to Administrator. I also create it but unable to configure rejected message CC: to Administrator. Thanks.
Babu

Hi Babu,
I have some tests in my environment using Exchange 2013, you can create a transport rule such as follows to achieve your goal.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Sending media to multiple clients

Hello everybody,
I'm searching for a way to make a datasource available to several clients.
My approach is:
-create a cloneableDatasource
-create a clone of this dataSource for every Client
-use clone as input for datasink
-send it to client
What would be the correct way to do that? Thanks for any advice,
Chris

VladimrN wrote:
Imagine there is a sender, who sends a stream to a receiver (server). On the other side there are several clients waiting.
At the moment the server receives media stream and sends that out to all receivers. Right, okay...
In case the receivers are just users of the same web-application, wouldn't it be much smarter to write the incoming stream in a file/pipe (server side). If you're wanting to save the file permanently to the server, sure...
I could put the URL of the file in a object-tag - all receivers would see the same without sending the stream from the server to several targets.Ummm, how do you expect the file to get from the server to the clients, magic? You're still talking about streaming here, or I suppose downloading / progressive downloading from the server to the clients. Either way, the file is going
In addition to that it wouldn't matter if a receiver joins after the stream has already begun and we wouldn't need any jmf installation at the receiver side.Ummmm, sure...
In this approach there i no need to stop or rewind the media at client side, because receivers only should see what the sender is sending at the moment.Actually, no... the client would be downloading the file, and could stop, rewind, fast forward, etc.. The end of the file would be the current point in the reception between the sender and the receiver-server...
Is this possible and how would the file on the server look like?Yeah, it's possible... but to be honest, I'm not sure what state a "being saved" file is in while JMF is writing to it. It's assuredly write-locked, but I'm not sure if it's read-locked as well.
You'd have to play around with the associated example code,
[http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/solutions/RTPExport.html]
And see what happens if you try to save to some file (say, "test.avi") in one JMF program while simultaniously trying to play that file in another JMF program.

Inconsistent Results from Transport Rule to reset SCL

I have a client who has multiple sites. Their exchange server receives "scan to email" emails from a Canon C2020 Digital Multifunction on a different site. To stop the Exchange 2013 Spam filter blocking the emails, I set up a Transport Rule.
The rule has the following properties
If the Sender Address matches [email protected]
Set the SCL to 3
Generate an incident report and email to the system admin, and inlcude the original email
Is the 3rd of 3 rules (the prior 2 add Disclaimers to outgoing emails depending on who the sender is)
Simple enough right.
Wrong - some staff scan to email repeatedly and the scan arrives ok in their inbox. Others, it simply will not let the email thru, and instead places the email into the Spam Mailbox. I open the blocked email, click on Send Again and
it arrives for the user.
Is the Transport Rule functionality buggy or prone to odd behaviour. I have sat and read through the Rule so many times it is tattooed onto my retina.
The Email addresses for all users are created by an Email address policy so all are a consistent format = Firstname + Surname 1st Initial@contoso .com.
There have been times where I have wondered if the rules are case sensitive when assessing the email addresses.
Any thoughts to put me out of my misery, please show me where I have done wrong....
Get-TransportRule returns
[PS] C:\Windows\system32>Get-TransportRule "[Cust-sos-IN] Reset SCL on Scanner emails" | Format-List
RunspaceId                                   : 7f9c4f6e-7d35-409e-acf9-cbb272720b8c
Priority                                     : 2
DlpPolicy                                    :
DlpPolicyId                                  : 00000000-0000-0000-0000-000000000000
Comments                                     :
ManuallyModified                             : False
ActivationDate                               :
ExpiryDate                                   :
Description                                  : If the message:
Is sent to '[email protected]' or
'[email protected]' or
'[email protected]' or
'[email protected]' or
'[email protected]' or
'[email protected]' or
'[email protected]'or...
and Includes these patterns in the From address:
'[email protected]'
Take the following actions:
Set the spam confidence level (SCL) to '3'
and Send the incident report to [email protected], Include
original mail
RuleVersion                                  : 15.0.2.0
Conditions                                   : {SentTo, FromAddressMatches}
Exceptions                                   :
Actions                                      : {SetSCL, GenerateIncidentReport}
State                                        : Enabled
Mode                                         : Enforce
RuleSubType                                  : None
UseLegacyRegex                               : False
From                                         :
FromMemberOf                                 :
FromScope                                    :
SentTo                                       :
{[email protected],
[email protected],
[email protected],
[email protected],
[email protected],
[email protected],
[email protected],
[email protected], [email protected],
[email protected],
[email protected], [email protected],
[email protected],
[email protected], [email protected],
[email protected]...}
SentToMemberOf                               :
SentToScope                                  :
BetweenMemberOf1                             :
BetweenMemberOf2                             :
ManagerAddresses                             :
ManagerForEvaluatedUser                      :
SenderManagementRelationship                 :
ADComparisonAttribute                        :
ADComparisonOperator                         :
SenderADAttributeContainsWords               :
SenderADAttributeMatchesPatterns             :
RecipientADAttributeContainsWords            :
RecipientADAttributeMatchesPatterns          :
AnyOfToHeader                                :
AnyOfToHeaderMemberOf                        :
AnyOfCcHeader                                :
AnyOfCcHeaderMemberOf                        :
AnyOfToCcHeader                              :
AnyOfToCcHeaderMemberOf                      :
HasClassification                            :
HasNoClassification                          : False
SubjectContainsWords                         :
SubjectOrBodyContainsWords                   :
HeaderContainsMessageHeader                  :
HeaderContainsWords                          :
FromAddressContainsWords                     :
SubjectMatchesPatterns                       :
SubjectOrBodyMatchesPatterns                 :
HeaderMatchesMessageHeader                   :
HeaderMatchesPatterns                        :
FromAddressMatchesPatterns                   :
{[email protected]}
AttachmentNameMatchesPatterns                :
AttachmentExtensionMatchesWords              :
HasSenderOverride                            : False
MessageContainsDataClassifications           :
SenderIpRanges                               :
SCLOver                                      :
AttachmentSizeOver                           :
MessageSizeOver                              :
WithImportance                               :
MessageTypeMatches                           :
RecipientAddressContainsWords                :
RecipientAddressMatchesPatterns              :
SenderInRecipientList                        :
RecipientInSenderList                        :
AttachmentContainsWords                      :
AttachmentMatchesPatterns                    :
AttachmentIsUnsupported                      : False
AttachmentProcessingLimitExceeded            : False
AttachmentHasExecutableContent               : False
AnyOfRecipientAddressContainsWords           :
AnyOfRecipientAddressMatchesPatterns         :
ExceptIfFrom                                 :
ExceptIfFromMemberOf                         :
ExceptIfFromScope                            :
ExceptIfSentTo                               :
ExceptIfSentToMemberOf                       :
ExceptIfSentToScope                          :
ExceptIfBetweenMemberOf1                     :
ExceptIfBetweenMemberOf2                     :
ExceptIfManagerAddresses                     :
ExceptIfManagerForEvaluatedUser              :
ExceptIfSenderManagementRelationship         :
ExceptIfADComparisonAttribute                :
ExceptIfADComparisonOperator                 :
ExceptIfSenderADAttributeContainsWords       :
ExceptIfSenderADAttributeMatchesPatterns     :
ExceptIfRecipientADAttributeContainsWords    :
ExceptIfRecipientADAttributeMatchesPatterns :
ExceptIfAnyOfToHeader                        :
ExceptIfAnyOfToHeaderMemberOf                :
ExceptIfAnyOfCcHeader                        :
ExceptIfAnyOfCcHeaderMemberOf                :
ExceptIfAnyOfToCcHeader                      :
ExceptIfAnyOfToCcHeaderMemberOf              :
ExceptIfHasClassification                    :
ExceptIfHasNoClassification                  : False
ExceptIfSubjectContainsWords                 :
ExceptIfSubjectOrBodyContainsWords           :
ExceptIfHeaderContainsMessageHeader          :
ExceptIfHeaderContainsWords                  :
ExceptIfFromAddressContainsWords             :
ExceptIfSubjectMatchesPatterns               :
ExceptIfSubjectOrBodyMatchesPatterns         :
ExceptIfHeaderMatchesMessageHeader           :
ExceptIfHeaderMatchesPatterns                :
ExceptIfFromAddressMatchesPatterns           :
ExceptIfAttachmentNameMatchesPatterns        :
ExceptIfAttachmentExtensionMatchesWords      :
ExceptIfSCLOver                              :
ExceptIfAttachmentSizeOver                   :
ExceptIfMessageSizeOver                      :
ExceptIfWithImportance                       :
ExceptIfMessageTypeMatches                   :
ExceptIfRecipientAddressContainsWords        :
ExceptIfRecipientAddressMatchesPatterns      :
ExceptIfSenderInRecipientList                :
ExceptIfRecipientInSenderList                :
ExceptIfAttachmentContainsWords              :
ExceptIfAttachmentMatchesPatterns            :
ExceptIfAttachmentIsUnsupported              : False
ExceptIfAttachmentProcessingLimitExceeded    : False
ExceptIfAttachmentHasExecutableContent       : False
ExceptIfAnyOfRecipientAddressContainsWords   :
ExceptIfAnyOfRecipientAddressMatchesPatterns :
ExceptIfHasSenderOverride                    : False
ExceptIfMessageContainsDataClassifications   :
ExceptIfSenderIpRanges                       :
PrependSubject                               :
SetAuditSeverity                             :
ApplyClassification                          :
ApplyHtmlDisclaimerLocation                  :
ApplyHtmlDisclaimerText                      :
ApplyHtmlDisclaimerFallbackAction            :
ApplyRightsProtectionTemplate                :
SetSCL                                       : 3
SetHeaderName                                :
SetHeaderValue                               :
RemoveHeader                                 :
AddToRecipients                              :
CopyTo                                       :
BlindCopyTo                                  :
AddManagerAsRecipientType                    :
ModerateMessageByUser                        :
ModerateMessageByManager                     : False
RedirectMessageTo                            :
RejectMessageEnhancedStatusCode              :
RejectMessageReasonText                      :
DeleteMessage                                : False
Disconnect                                   : False
Quarantine                                   : False
SmtpRejectMessageRejectText                  :
SmtpRejectMessageRejectStatusCode            :
LogEventText                                 :
StopRuleProcessing                           : False
SenderNotificationType                       :
GenerateIncidentReport                       :
[email protected]
IncidentReportOriginalMail                   : IncludeOriginalMail
RouteMessageOutboundConnector                :
RouteMessageOutboundRequireTls               : False
Identity                                     : [Cust-sos-IN] Reset SCL on Scanner
emails
DistinguishedName                            : CN=[Cust-sos-IN] Reset SCL on Scanner
emails,CN=TransportVersioned,CN=Rules,CN=Transport
Settings,CN=Contoso,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=CONTOSO,DC=LOCAL
Guid                                         : 5d1dbc9b-3718-4874-9552-296e8b98d874
ImmutableId                                  : 5d1dbc9b-3718-4874-9552-296e8b98d874
OrganizationId                               :
Name                                         : [Cust-sos-IN]
Reset SCL on Scanner emails
IsValid                                      : True
WhenChanged                                  : 17/03/2015 2:37:06 PM
ExchangeVersion                              : 0.1 (8.0.535.0)
ObjectState                                  : Unchanged

Hi MBKITMGR,
Agree with Zammit, you should use the BypassedSenders parameter to specifies the SMTP address values of senders.
After that, the Content Filter agent doesn't process any content filtering for messages received from the addresses listed on this parameter.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Where to check/enable for log keeping track of transport rule actions?

I have implemented some transport rules to "journal" all emails from specific clients as per this
thread.
So there are 4 transport rules to capture all those email:
1. email from Clients (incoming / FROM)
1.1 from users outside the organization.
1.2 sent to member of AD Group
1.3 sent to users inside the organization.
1.4 where the from address contains "domain of our clients list"
1.5 BBC to capture mailbox
2. email to Clients (outgoing/ TO)
2.1 from member of AD Group
2.2 from users inside the org
2.3 sent to users outside the organization.
2.4 where the to address contains "domain of our clients list"
2.5 BBC to capture mailbox
3. email to Clients (outgoing/ CC)
3.1 from member of AD Group
3.2 from users inside the org
3.3 sent to users outside the organization.
3.4 where the cc address contains "domain of our clients list"
3.5 BBC to capture mailbox
4. email to Clients (outgoing/ BCC)
4.1 from member of AD Group
4.2 from users inside the org
4.3 sent to users outside the organization.
4.4 where the bcc address contains "domain of our clients list"
4.5 BBC to capture mailbox
The symptoms are that while I am seeing by selecting random emails that everything seem to run fine (rule filtering from transport does get incoming and outgoing messages to that “capture” mailbox) and I tested this fine with some test emails
in different domains.
Somehow I am no getting the results I want. With business sending some test sets I should be finding in that mailbox, I do not find everything. Some of the email that apparently would logically be captured are not. Is business lying about the test sets they
send? I don’t think so and the fact is that I seem to be missing emails.
Anyhow my questions to you are the following:
1. Do you know of any logging done by the transport server to check on matches of the filters?
2. I am using outside and inside condition in the rules. Are they what I think they are?
I hope you can help. I think I am doing this right, but I cannot verify the process 100%. Some logs or additional information would help. Or perhaps I am not using the conditions properly.
Thank you in advance.
and BTW the environment is Exchange 2007

Based on my research, there is no specific log to match the filters. During the mail flow, only SMTP log and Message Tracking log can record the message information.
You can check the two logs if needed. For more information, please refer to the following steps.
Enable Message tracking log
1. Open the Exchange Management Console.
2. In the console tree, expand Server Configuration, and select Hub Transport.
3. In the action pane, click the Properties link that is directly under the server name.
4. In the Properties page, click the Log Settings tab.
5. In the Message tracking log section, Select Enable message tracking log to enable message tracking.
6. Click Apply to save changes and remain in the Properties page, or click OK to save changes and exit the Properties page.
Enable SMTP Log
1. In the console tree, expand Organization Configuration, and select Hub Transport.
2. In the action pane, click on Sender Connectors and right click on send connector and then click on properties.
3. Select “Verbose” under “Protocol logging level” and then click ok.
Then, you can find the logs from the following location.
Collect Message Tracking Log
On the Exchange server, go to directory “c:\program files\Microsoft\exchange server\TransportRoles\Logs\Message Tracking”
Collect SMTP log
Open the folder on the Hub Server,: C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend.
Thanks.
Novak
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Multiple client receivers

Hi Experts,
I have a requirement where the SENDER is SOAP and the receiver is RFC.
Sender send the data and it should be bifurcated to 6 clients based on some condition.
Previously I have created a rule in receiver determination to send the date to multiple receivers which are existed in the same client.
But now here they want to send the data to multiple client receivers based on the condition.
Do I need to create the CC and receiver agreement for each receiver or is there any other option available ?
Please help me out with this.
thanks and regards,
praveen

Hi praveen,
Yes. You can handle this in the same way by creating the condition in Receiver determination.
But here you need to create separate Interface determination and receiver agreement for each receiver. You can use existing RFC Communication channel in Receiver agreement.
Regards
Baskaran K

XI, SLD & multiple clients for DEV & QA

Ref: Re: 3rd party tech systems for multiple business systems...
I have a question regarding the avoidance of duplicated Configuration (Collaboration Profiles, Logical Routing & Collaboration Agreements) for different clients in the DEV/QA landscape.
As we know: many projects have multiple clients in DEV and QA. Here is an example landscape:
SXD_100 - Dev XI server
SED_100 - config dev
SED_200 - ABAP dev
SED_300 - unit test
SED_400 - sandbox
[ 1 technical system : 3 business systems ! ]
LDEV Legacy system
[ 1 technical system : 1 business system ]
SXQ_100 - QA XI server
SEQ_100 - clean config QA
SEQ_200 - ABAP QA
SEQ_300 - data migration prep
SEQ_nnn - yada, yada...
[ 1 technical system : nnn business systems ! ]
LQA Legacy system
[ 1 technical system : 1 business system ]
The problem:
SED_400->LDEV is used for prototyping integration
SED_100->LDEV is used for config development
SED_200->LDEV is used for ABAP development
SED_300->LDEV is used for unit tests
Receiver Determination is able to look into the message for a dynamic receiver, but we are not able to have a sender like "SED*"
The question:
Do we really need multiple sets of configuration in the Integration Directory? Is there a way to re-use the configuration for SED_100->LDEV for the other development efforts?
Any feedback would be greatly appreciated.
Rgds,
Derek

Hi Derek,
Since there can only one business system in SLD per client in SAP R/3.
e.g
SED_100 will have lets say BS_100_Dev
SED_200 and BS_200_Dev
In QA
SEQ_100 -> BS_100_QA
SEQ_200 -> BS_200_QA
It is not possible to configure the single scenario catering the Dynamic (multiple) sender agreement to Reciever.
But for QA you can use set transport target in SLD to reflect the BS_100_Dev -> BS_100_QA, where ever used.
This doesnot solve the problem of having dynamic sender service, it is just for information.
We also faced the same problem of testing a scenario from different clients of SAP :(.
Cheers,
Satish

Transport rule to prevent sending to multiple clients

Similar Messages

Maybe you are looking for