Seeburger Message Tracking - File Store Dinamic variables

Hello,
I dont have to much information about FileStore Module. I will appreciate if someone have information of this
or
If someone knows how to use dinamic variables with File Store....
Thanks & Regards,
lpbuff

Hi Suresh,
My question goes because I want to store in MT database some information of my message, but it should be before the message mapping that i use an UDF. Because i have a condition in my Receiver Determination so some message are not going to pass however i want to store some values in the MT database...so i need to store variable in File Store...i dont have documentation of this module so i've just know the usual parameter....
Any idea?...
Thanks!
lpbuff

Similar Messages

Seeburger Message Tracking

Hi,
Can anyone please tell us how to use seeburger message tracking.
I understand that there are 3 steps to be done.
1. Mapping in IR should have a UDF which referrers to the standard Seeburger function jar files.
2. Module configuration in the channel with FileStore module.
3. Configuration in Message Tracking.
But need some details about each step.
Could anyone please provide a document which explains this configuration.
Thanks in advance
Jagruthi

Hi,
before these steps you need to have MT installer file based on your database and some settings needs to be done at database level.
if you have seeburger manuals there is one pdf 'SAPXI_Archiving_en.pdf' which talks about MT.
Suresh

Seeburger message tracking archiving / deleting question

Hello,
We are using Seeburger 1.7 with XI 7.0 for our EDI translations..We store information in Seeburger Message Tracking for our business requirements.I would like to know how these entries could be archived(Compressed) and stored or deleted after certain days so that we wont max up our storage..?
Any suggestions are appreciated.
Thanks in advance!
Larry

Prateek,
Thanks for your response.Yes,I could find the "Archive Configuration" option..when I click that it shows me a screen saying show master data with two items with check boxes (Document Types & Archiving Systems)..On clicking the details of them I see set of parameters which shows the profile and the document type..not sure how to proceed from here to set up any archiving / deletion..any help is appreciated..
Regards,
Larry.

How to populate the Sender and Receiver GLN/ID in the Seeburger Message Tracking

HI Team,
Scenario :
ECC--> PI--> Party
Sending GS1 XML Message to party (Not EDI). Sender Party and Receiver Party appearing as expected.
BUT User expecting to see the Sender GLN and Receiver GLN in Seeburger Message Tracking.
It should be dynamically picked form GS1 Message. Should Appear in RED BOXES Shown below.What Module Parameters Should be used for this.
I have Tried destTargetMsg and destSourceMsg. But did'nt work.
can anyone please Help

Hi Veman
You are correct. For XML to XML, you do not need BIC module.
However, since you are not using BIC module, you will not be able to enrich the metadata using the archiveXI parameter during processing at the adapter framework.
Another place to enrich the metadata would be during message mapping. You can call a custom UDF to populate the metadata and create an entry in Seeburger Message Tracking.
Please refer to the Seeburger manual for Message Tracking Function for more details on how to create the UDF.
Rgds
Eng Swee

Multi mapping & seeburger Message Tracking (Filestore module)

Hello,
For the people who knows seeburger archiving...
Anybody make the scenario using multi mapping (split in the receiver) with message Tracking seeburger (File Store module in the Receiver Channel)?

Hi,
before these steps you need to have MT installer file based on your database and some settings needs to be done at database level.
if you have seeburger manuals there is one pdf 'SAPXI_Archiving_en.pdf' which talks about MT.
Suresh

Seeburger Message Tracking Update

Hi All,
I m working on one IDOC to Bank (820 document ) scenario. I am using the File adapter at receiver side and dumping a XML file.
I am trying to Update the message tracking in the seeburger using a function in message mapping which basically uses a UDF which includes use of MTMasterXI.
Any pointers on how to update the message trace in Seeburger Workbench will be appreciated.
Regards..
Sachin Dhingra

What do you mean by "update the message trace"?
You can see the message in Message Tracking tab of Workbench. But before that a bit more settings are required.
- Mapping in IR like you did it by creating UDF. It should refer to the standard Seeburger function jar files.
- Module configuration in the channel with FileStore module.
- Configuration in Message Tracking.
I hope the Message Tracking is already working for you when you click on Message Tracking tab.
Regards,
Prateek

Multiple Partners for the same customer in Message tracking of SEEBURGER

Hi,
This is for third party customers which use EDI messages. We have for one customer multiple partner numbers configured in Partner profile. I would like to know while configuring the trading partners in SEEBURGER Message Tracking, can we have multiple keys for the same customer for multiple partners for an INVOIC02. Like the following keys:
12345_INVOIC02
34567_INVOIC02
45678_INVOIC02

Hi Satya,
you can define for a vendor/customer several partner functions with different
adresses. You can create certain partner roles several times.
If you create a purchase order, than you can choose the wanted
address and partnerrole on the header level. In the standard system you
can use the patner role 'OA' ordering address and for the finance
the 'IP' Invoice presented by.
I hope I was able to help you.
Kind regards,
Zsuzsanna

Messaging tracking logs filename format changed in Exchange Server 2013 sp1

Hi,
I have noticed that the file name format is changed for exchange server 2013 sp1.
Now it will have hh attached to it like
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
So the "hh" will goes from 00 to 23 for single day.
So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
And also how it will be decided to create the first file @ 7.30 AM.
Can anyone explain to me about this ? Why it is happening like this?
Thanks
Sandeep Gupta

Hi Sandeep,
This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
were created on 20140411.
Also, as you mentioned, the file name format is as:
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
However as I know, the format is like
MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
and the date/time information of the file to verify.
Title: Message Tracking
Link:
http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
Regards, Eric Zou

Exchange Server 2010 - Message Tracking Logs - Log file creation

Hi,
I would like to find out on the behavior of the exchange server in the way that it logs the message tracking.
Currently the parameter used is
MessageTrackingLogMaxDirectorySize - 10GBMessageTrackingLogMaxAge - 30daysI would like to check when the Max Directory Size has exceeded the value indicated, does Exchange server immediately deletes the oldest log file to make space for the new logs?And in the event that the oldest file is being open or locked, will exchange server delete the next oldest file? or it will reattempt to delete the "locked" file for a period of time?Lastly, when these "oldest" files is not able to be deleted, will exchange server stops logging new tracking events?Thanks!

Hi Zack,
Thank you for your question.
If you have configured the parameter of “MessageTrackingLogMaxDirectorySize” and “MessageTrackingLogMaxAge”, we think you have enable circular logging, it will delete the oldest message tracking log files for new log file when the either of the following
conditions is true:
The message tracking log directory reaches its specified maximum size.
A message tracking log file reaches its specified maximum age.
In addition, it didn’t exceeded the value indicated.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Message tracking centre log files

1) If message tracking is enabled, any idea where exactly the physical log files reside on windows 2008 server?2)
2) if message tracking logs only go back 30 days, is there anyway to restore older logs from backups so they can be searched in tracking centre?
3) is there any 3rd party tools that can search/parse message tracking logs, so you can just restore the raw log files from the backup and not have to touch the live system?
this if for exchange 2010.

Hi,
1) If message tracking is enabled, any idea where exactly the physical log files reside on windows 2008 server?
A: By default, the message tracking log files exist in %ExchangeInstallPath%TransportRoles\Logs\MessageTracking. For Exchange 2010, the logs are generally stored in C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking
directory. On an Exchange 2013 Mailbox server, you can use the Set-TransportServer cmdlet to set the log path, for example:
Set-TransportServer Exchange01 -MessageTrackingLogPath "D:\Message Tracking"
2) if message tracking logs only go back 30 days, is there anyway to restore older logs from backups so they can be searched in tracking centre?
A: Also, we can use the Set-TransportServer cmdlet to set the maximum age of a message tracking log file. The example sets the maximum age of a message tracking log file to 45 days:
Set-TransportServer Exchange01 -MessageTrackingLogMaxAge 45.00:00:00
For more information about how to configure Message Tracking, please refer to:
http://technet.microsoft.com/en-us/library/aa997984(v=exchg.141).aspx
3) is there any 3rd party tools that can search/parse message tracking logs, so you can just restore the raw log files from the backup and not have to touch the live system?
A: Exchange 2010 also have message tracking tool in Exchange Management Console to search the Message Tracking Log. For more information about it, please refer to Searching the Message Tracking Logs by Using the Exchange Management Console
part in the following article:
http://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx
Regards,
Winnie Liang
TechNet Community Support

Weblogic server 9.2 How to clear up JMS file store messages

Hi,
We are facong one issue in our weblogic production environment. The JMS file store size has become 7.2 G and its eatimg up almost all the server space. I have cheked through the jms module queues/ topics to see that if any messages are pending anywhere but nothing signifficant I can find out. Now our requirement is to clear up the file store the freeup the server space.
Could you please recommend how to do that in the backend.
Thanks
Rahul

Hi Rahul,
Store files grow to fit all current stored objects, but, as stored objects are deleted, the freed space is re-used for new persistent objects. It's possible your store grew to an unprecedented size because it was temporarily forced to store many objects - in which case you can shrink the file store using the store compression tool described by the other poster.
On the other hand, in almost all cases, unexpectedly large backlogs are generated due to either (A) an accumulation of a backlog of unprocessed messages, or (B) a bug in an application that processes received messages but never acknowledges them, such as may happen when an application creates a durable subscription on a topic but fails to service the subscription.
I recommend (again) checking your 'current' and 'pending' message statistics for each and every JMS Server, SAF Agent, and destination that the store hosts. You can also check your store statistics to see which 'connections' are developing a large accumulation of objects.
Regards,
Tom
P.S. You can post JMS related questions to the WebLogic Server JMS newsgroup.

Message Tracking - Determing what happens to specific email

Good afternoon all! I have a situation with a client Exchange 2010 server. They have a front end/back end exchange setup. They are running this on Server 2008 R2. Mail is setup and working great. They have ONE specific email
they receive on a nightly basis. This email makes it through the front end spam solution, then passes the receive connector. In the message tracking logs I see the message is received. It is sent to a distribution group. Other email
that is sent to the distribution group will have a corresponding expand and deliver logs. This particular email does not have anything further than receive. No other logs to identify why it is not being delivered or dropped or anything. I
have run the following command to ensure I have the full information:
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>get-exchangeserver | where {$_.isHubTransportServer -eq $tru
e -or $_.isMailboxServer -eq $true} | Get-MessageTrackinglog -MessageId "[email protected]" | fl
RunspaceId              : e5feafd8-bb88-414d-ad8f-7841df4ad30d
Timestamp               : 10/24/2014 12:20:44 AM
ClientIp                : *.*.*.* (Front End IP)
ClientHostname          : frontend.spam.solution
ServerIp                : 192.168.10.240
ServerHostname          : Exch2010.domain.local
SourceContext           : 08D1BC5A8D9DC4B6;2014-10-24T05:20:43.396Z;0
ConnectorId             : Exch2010\Default Exch2010
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 3816
MessageId               : <[email protected]>
Recipients              :
{[email protected]}
RecipientStatus         : {}
TotalBytes              : 5091
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Delivery Status Notification (Failure)
Sender                  :
[email protected]
ReturnPath              : <>
MessageInfo             : 00A: NTS:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, Exch2010.domain.local]}
There are no further logs on this message. For those that will read the delivery status notification. This message is a bounce back message that they are not receiving. I did change the Default Properties on the remote domains, so that
Allow external out-of-office messages and legacy out-of-office messages is selected as well as under message format: Allow Auto replies, Allow Auto Forward, Allow Delivery Reports, Allow Non-Delivery Reports are also all selected.
I am lost on where to figure out what happens to this email after the receive connector gets it. Messages normally have other messages that show additional information; however this message just dies there.
Any ideas or help would be greatly appreciated!
Thanks
Jason

Thanks for the reply. I actually started with searches for anything going to that distribution group. I used the GUI version, then went to the shell. Neither was able to produce anything beyond receive. I thought maybe the group was
not setup properly to get emails from the outside, but after testing from my email address directly to the group, I see normal behavior it expands then delivers to the store. With these particular emails, they only ever have the event of receive nothing
further. Any ideas where to look when that happens?
Thanks
Jason

Capture error message and write the error message to file

Anyone know that how to caputre the error message which is generated in a scope catch? and then write the error message to file?
Thanks a lot!!

Hi,
Please try the following:
1. Double click on the newly created catch activity (denoted by an ‘!’ symbol
on it)
2. In the General Tab, Click on the ‘Browse Faults’ icon (denoted by a torch
symbol)
3. A fault chooser window opens, (Eg. Expand partner links->CreditRatingService
-> CreditRatingService -> FaultNegativeCredit)
4. Create a variable (Eg. Fault1_NegativeCredit) in the Fault chooser window to store this value.
5. Create a partner link, configured as a file adapter. (Specify your output file in this file adapter wizard)
6. Invoke this partner link and pass the 'Fault1_NegativeCredit' variable to that partner link
I hope you are aware of the terms I used, the steps are just guide lines. practically, u need to do a few more steps. Please refer the BPEL tutorials on exception handling and file adapters. that will help you...
best regards
Message was edited by:
hem chand

Error-Receiver File Adapter using Variable substitution when file is empty

XI Experts,
We are on PI 7.0, SP14.
We are using variable subtitution to get the filename from source message. This works fine as long as we have data in the payload for filename element. But we have a scenario where we don't have to create file when certain condition does not exists in source message so in the message payload filename element will not exists in such condition and file will be empty and we should not create file.
Parameter in the communication channel for Handling empty message is "Ignore".
Does anyone knows how to handle this scneario. We don't want to default any file name in the message mapping if source file name element does not exists.
We are following getting error in the Adapter engine.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file
Thanks
MP

You can implement this by writing the module to throw an exception or whatever method you want to execute.
If you don't want to receive an error message then module is suitable for you.
Gaurav Jain

Problem receiving from sender, showing in SmtpReceive log but not Message Tracking

Our Exchange 2007 server (SBS2k8 really) has had problems receiving mail from a certain sender the last few weeks. With the SMTPReceive set to verbose, I can see the mail coming in but it never shows up in the message tracking logs.
Looking at similar issues, I thought maybe the content filtering agent might have been grabbing it, so I set up a transport rule to take any mail from this particular domain and set the SCL to 0 as well as bcc a copy of it to myself. But I just noticed
another entry in yesterday's smtpreceive log and that didn't do the trick (or forward a copy to me for that matter).
I'm including some samples from our SMTP log. I can see that when it works, after the 354 Start mail input line, our server sends a 250 2.6.0 code confirming the message has been queued for delivery, at which point the remote server sends a QUIT and
we close it. But when it fails, there's nothing after the 354 line.
Example of good transmission:
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,0,10.0.100.3:25,50.xxx.xxx.xxx:9100,+,,
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,1,10.0.100.3:25,50.xxx.xxx.xxx:9100,*,SMTPSubmit SMTPAcceptAnySender AcceptRoutingHeaders,Set Session Permissions
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,2,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,"220 xxx.xxx.com Microsoft ESMTP MAIL Service ready at Wed, 23 Apr 2014 11:00:49 -0400",
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,3,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,EHLO other.domain.com,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,4,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-xxx.xxx.com Hello [50.xxx.xxx.xxx],
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,5,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-SIZE 26091520,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,6,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-PIPELINING,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,7,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-DSN,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,8,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-ENHANCEDSTATUSCODES,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,9,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-STARTTLS,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,10,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-AUTH,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,11,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-8BITMIME,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,12,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-BINARYMIME,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,13,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 CHUNKING,
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,14,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,MAIL FROM:<[email protected]> SIZE=3497,
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,15,10.0.100.3:25,50.xxx.xxx.xxx:9100,*,08D11000FE2BD02F;2014-04-23T15:00:49.620Z;1,receiving message
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,16,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.1.0 Sender OK,
2014-04-23T15:00:50.073Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,17,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,RCPT TO:<[email protected]>,
2014-04-23T15:00:50.291Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,18,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.1.5 Recipient OK,
2014-04-23T15:00:50.338Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,19,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,DATA,
2014-04-23T15:00:50.338Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,20,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,354 Start mail input; end with <CRLF>.<CRLF>,
2014-04-23T15:00:50.525Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,21,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.6.0 <[email protected]> Queued mail for delivery,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,22,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,QUIT,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,23,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,221 2.0.0 Service closing transmission channel,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,24,10.0.100.3:25,50.xxx.xxx.xxx:9100,-,,Local
and an example of the message not being successfully received:
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,0,10.0.100.3:25,50.xxx.xxx.xxx:10131,+,,
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,1,10.0.100.3:25,50.xxx.xxx.xxx:10131,*,SMTPSubmit SMTPAcceptAnySender AcceptRoutingHeaders,Set Session Permissions
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,2,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,"220 xxx.xxx.com Microsoft ESMTP MAIL Service ready at Thu, 24 Apr 2014 07:57:36 -0400",
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,3,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,EHLO other.domain.com,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,4,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-xxx.xxx.com Hello [50.xxx.xxx.xxx],
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,5,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-SIZE 26091520,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,6,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-PIPELINING,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,7,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-DSN,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,8,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-ENHANCEDSTATUSCODES,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,9,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-STARTTLS,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,10,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-AUTH,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,11,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-8BITMIME,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,12,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-BINARYMIME,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,13,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 CHUNKING,
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,14,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,MAIL FROM:<[email protected]> SIZE=3481,
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,15,10.0.100.3:25,50.xxx.xxx.xxx:10131,*,08D11000FE2BD40D;2014-04-24T11:57:37.220Z;1,receiving message
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,16,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 2.1.0 Sender OK,
2014-04-24T11:57:37.610Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,17,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,RCPT TO:<[email protected]>,
2014-04-24T11:57:37.719Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,18,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 2.1.5 Recipient OK,
2014-04-24T11:57:37.750Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,19,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,DATA,
2014-04-24T11:57:37.750Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,20,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,354 Start mail input; end with <CRLF>.<CRLF>,
2014-04-24T11:57:37.875Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,21,10.0.100.3:25,50.xxx.xxx.xxx:10131,-,,Remote
Interestingly, we used to receive email from this sender in the past. When it stopped working, it didn't quite stop working outright - at some point after the deliveries stopped, 2 made it in, but nothing again since then.

Check the agent logs on the machine. The Exchange anti-spam agents log files are found here:
C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\AgentLog
If you use Forefront, its agent log files are usually here:
C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server\Data\FSEAgentLog
Other software may have its log files elsewhere.
--- Rich Matheisen MCSE&I, Exchange MVP

Seeburger Message Tracking - File Store Dinamic variables

Similar Messages

Maybe you are looking for