test-mailflow problems

[Frost''''IK]

We have reinstalled Operations manager 2007 and re-created test mailboxes on
our Exchange 2007 servers. We have deleted old ones and created new with a
script New-TestCasConnectivityUser.ps1. Now we have a lot of error messages
from operations manager.

Here is an example of such a message:

Source: EXCHANGE1 Alert: An error occurred while running the Test-Mailflow
(Local) cmdlet. (Pri: 1 Sev: 0 Res.state: Closed)
body: Alert: An error occurred while running the Test-Mailflow (Local) cmdlet.
Source: EXCHANGE1
Path: EXCHANGE1.domain.com
Last modified by: System
Last modified time: 20.03.2009 11:40:45
Alert description: Error occurred while executing the Test-Mailflow (Local)
diagnostic cmdlet.

The initial event reported:

The delivery receipt for the test message from
EXCHANGE1\***@domain.com to EXCHANGE1\***@domain.com was not received
within the execution timeout of 240 seconds. The cmdlet will not wait any
longer for the delivery receipt.

Response to rule: "{1240B1DB-E57C-62CF-1F65-B62A6DC4C786}"

Diagnostic command: "Test-Mailflow -ErrorLatency:60 -MonitoringContext:$true"

The command "Test-mailflow -ErrorLatency:1 -ExecutionTimeout:1
-MonitoringContext $true -verbose | FL"

gives that:

VERBOSE: Test-Mailflow : Beginning processing.
VERBOSE: Test-Mailflow : Searching objects "EXCHANGE1" of type "Server" under
the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on domain controller
'dc1.domain.com'.
VERBOSE: Test-Mailflow : Searching objects
"SystemMailbox{b165188e-d22c-43d0-928d-c0b1e0c5cee2}" of type
"ADSystemMailbox"
under the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on global catalog server
'dc1.domain.com'.
VERBOSE: Testing mail flow.


TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest : False

Events : {Source: MSExchange Monitoring Mailflow Local
Id: 1002
Type: Error
Message: The delivery receipt for the test message from
EXCHANGE1\***@domain.com to EXCHANGE1\***@domain.com
was not received within the error latency time
out of 1 seconds. The cmdlet will keep waiting until the
execution timeout or the arrival of the delivery receipt.
, Source: MSExchange Monitoring Mailflow Local
Id: 1001
Type: Error
Message: The delivery receipt for the test message from
EXCHANGE1\***@domain.com to EXCHANGE1\***@domain.com
was not received within the execution timeout
of 1 seconds. The cmdlet will not wait any longer for the
delivery receipt.}
PerformanceCounters : {Object: MSExchange Monitoring Mailflow Local
Counter: Mailflow Latency
Instance: EXCHANGE1
Value: -1}

Here is a starange thing. I do not see any maibox with a name
***@domain.com. My test mailbox on this server has a name
***@domain.com. And also I can see that one of my system mailbox has this
wrong mailbox address in its properties. But this is a system mailbox of a
storage another then a storage contained my new test mailbox.

I tried to start commandNew-TestCasConnectivityUser.ps1 but it does not help.

How can I target operations manager on a new test mailbox?

[Steven Halsey [MSFT]]

This post might be inappropriate. Click to display it.

[Frost''''IK]

All storages are online. How can I check that my system mailboxes are ok? I
cannot see any system mailboxes in Exchange Management Console. The cmdlet
get-mailbox does not show any system mailbox too.

Post by Steven Halsey [MSFT]
Test-mailflow does not use the same mailbox created by the
New-TestCasConnectivityUser.ps1. Test-mailflow uses the system mailboxes of
the two servers involved in the transaction.
New-TestCasConnectivityUser.ps1 creates a user that is used by the Client
Access and Unified Messaging Transactions.
You should figure out why mail to the system mailbox can not be recieved, is
the MDB offline that owns the System Mailbox? Has the System Mailbox been
moved to a different server?
You can't control which mailbox is used on each server. In the current
Exchange 2007 Converted MP Exchange decides which mailbox will be the target
of the Mailflow based on a round robin between the servers for Remote
Mailflow. For Example 3 servers A,B,and C. A sends to B, B sends C, C sends
A. If B happens to be a test server that isn't available then the send from
A to B will fail and you see errors like you are seeing with the time outs.
You can override the the target mailbox server for A by adding the
value -targetmailboxserver:C to the cmdletCommand parameter.
--
Steven Halsey [MSFT]

[Steven Halsey [MSFT]]

You can try using tools like the Exchange Mail Flow Troubleshooting
Assistant (http://msexchangeteam.com/archive/2006/08/07/428616.aspx) to
diagnose the issues.
I believe it uses the same test-mailflow commandlet, and has extra
diagnostics to help troubleshoot the issue, such as tracking the message
through message tracking.


When you ran the test-mailflow in verbose mode where did the email address
used map to? Was it a System Mailbox on an MDB on the same server that you
were running the mailflow test from? If this mailbox is on the same server
then the commandlet is targetting an appropriate system mailbox.

I believe you would need to use a tool like ldp.exe or adsiedit.msc to look
at the System Mailboxes as they are hidden from the Exchange UIs.
You want to see if the attributes proxyaddresses, and HomeMDB map correctly
to the objects. For instance the System Mailbox below, is homed on
"Ex2007mp3-mbx1\TestStorageGroup\TestPrivateMDB1".

Dn: CN=SystemMailbox{9C567385-6724-4DFA-864B-09A81589C9D0},CN=Microsoft
Exchange System Objects,DC=Ex2007mp3,DC=Local
proxyAddresses:
SMTP:SystemMailbox{9C567385-6724-4DFA-864B-09A81589C9D0}@Ex2007mp3.Local
homeMDB:
CN=TestPrivateMDB1,CN=TestStorageGroup,CN=InformationStore,CN=Ex2007mp3-mbx1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MPTest
Exchange Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=Ex2007mp3,DC=Local;
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Frost''''IK
All storages are online. How can I check that my system mailboxes are ok? I
cannot see any system mailboxes in Exchange Management Console. The cmdlet
get-mailbox does not show any system mailbox too.

Post by Steven Halsey [MSFT]
Test-mailflow does not use the same mailbox created by the
New-TestCasConnectivityUser.ps1. Test-mailflow uses the system mailboxes of
the two servers involved in the transaction.
New-TestCasConnectivityUser.ps1 creates a user that is used by the Client
Access and Unified Messaging Transactions.
You should figure out why mail to the system mailbox can not be recieved, is
the MDB offline that owns the System Mailbox? Has the System Mailbox been
moved to a different server?
You can't control which mailbox is used on each server. In the current
Exchange 2007 Converted MP Exchange decides which mailbox will be the target
of the Mailflow based on a round robin between the servers for Remote
Mailflow. For Example 3 servers A,B,and C. A sends to B, B sends C, C sends
A. If B happens to be a test server that isn't available then the send from
A to B will fail and you see errors like you are seeing with the time outs.
You can override the the target mailbox server for A by adding the
value -targetmailboxserver:C to the cmdletCommand parameter.
--
Steven Halsey [MSFT]

[Frost''''IK]

It's weird but I can see DSN messages in system mailbox, but Test-mailflow
reports error.


Test-mailflow report:


Test-mailflow -ErrorLatency:10 -ExecutionTimeout:240 -MonitoringContext
$true -verbose |FL
VERBOSE: Test-Mailflow : Beginning processing.
VERBOSE: Test-Mailflow : Searching objects "EXCHANGE1" of type "Server" under
the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on domain controller
'dc00.domain.com'.
VERBOSE: Test-Mailflow : Searching objects
"SystemMailbox{b165188e-d22c-43d0-928d-c0b1e0c5cee2}" of type
"ADSystemMailbox"
under the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on global catalog server
'dc00.domain.com'.
VERBOSE: Testing mail flow.


TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest : False

Events : {Source: MSExchange Monitoring Mailflow Local
Id: 1002
Type: Error
Message: The delivery receipt for the test message from
EXCHANGE1\***@domain.com to EXCHANGE1\***@do
main.com was not received within the error latency time
out of 10 seconds. The cmdlet will keep waiting until
the
execution timeout or the arrival of the delivery
receipt
., Source: MSExchange Monitoring Mailflow Local
Id: 1001
Type: Error
Message: The delivery receipt for the test message from
EXCHANGE1\***@domain.com to EXCHANGE1\***@do
main.com was not received within the execution timeout
of 240 seconds. The cmdlet will not wait any longer
for t
he delivery receipt.}
PerformanceCounters : {Object: MSExchange Monitoring Mailflow Local
Counter: Mailflow Latency
Instance: EXCHANGE1
Value: -1}

VERBOSE: Test-Mailflow : Ending processing.


DSN:

Your message has been delivered to the following recipients:

SystemMailbox{B165188E-D22C-43D0-928D-C0B1E0C5CEE2}<mailto:***@domain.com>

Subject: Test-Mailflow edc12594-5326-4270-9a3f-01c48b79896b
66c7004a-6860-44b2-983a-327aa3c9cfec

________________________________
Sent by Microsoft Exchange Server 2007

Post by Steven Halsey [MSFT]
You can try using tools like the Exchange Mail Flow Troubleshooting
Assistant (http://msexchangeteam.com/archive/2006/08/07/428616.aspx) to
diagnose the issues.
I believe it uses the same test-mailflow commandlet, and has extra
diagnostics to help troubleshoot the issue, such as tracking the message
through message tracking.
When you ran the test-mailflow in verbose mode where did the email address
used map to? Was it a System Mailbox on an MDB on the same server that you
were running the mailflow test from? If this mailbox is on the same server
then the commandlet is targetting an appropriate system mailbox.
I believe you would need to use a tool like ldp.exe or adsiedit.msc to look
at the System Mailboxes as they are hidden from the Exchange UIs.
You want to see if the attributes proxyaddresses, and HomeMDB map correctly
to the objects. For instance the System Mailbox below, is homed on
"Ex2007mp3-mbx1\TestStorageGroup\TestPrivateMDB1".
Dn: CN=SystemMailbox{9C567385-6724-4DFA-864B-09A81589C9D0},CN=Microsoft
Exchange System Objects,DC=Ex2007mp3,DC=Local
CN=TestPrivateMDB1,CN=TestStorageGroup,CN=InformationStore,CN=Ex2007mp3-mbx1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MPTest
Exchange Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=Ex2007mp3,DC=Local;
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Frost''''IK
All storages are online. How can I check that my system mailboxes are ok? I
cannot see any system mailboxes in Exchange Management Console. The cmdlet
get-mailbox does not show any system mailbox too.

Post by Steven Halsey [MSFT]
Test-mailflow does not use the same mailbox created by the
New-TestCasConnectivityUser.ps1. Test-mailflow uses the system mailboxes of
the two servers involved in the transaction.
New-TestCasConnectivityUser.ps1 creates a user that is used by the Client
Access and Unified Messaging Transactions.
You should figure out why mail to the system mailbox can not be recieved, is
the MDB offline that owns the System Mailbox? Has the System Mailbox been
moved to a different server?
You can't control which mailbox is used on each server. In the current
Exchange 2007 Converted MP Exchange decides which mailbox will be the target
of the Mailflow based on a round robin between the servers for Remote
Mailflow. For Example 3 servers A,B,and C. A sends to B, B sends C, C sends
A. If B happens to be a test server that isn't available then the send from
A to B will fail and you see errors like you are seeing with the time outs.
You can override the the target mailbox server for A by adding the
value -targetmailboxserver:C to the cmdletCommand parameter.
--
Steven Halsey [MSFT]

[Steven Halsey [MSFT]]

There was an issue where the virus/antispam provider changed the messages,
and this caused the mail flow message to no longer be recognized by the
Exchange commandlet.
http://technet.microsoft.com/en-us/library/cc721232.aspx under Test-mailflow
Alerts. So check and see if any engines scanning your emails are changing
the subject line of the message.
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Frost''''IK
It's weird but I can see DSN messages in system mailbox, but Test-mailflow
reports error.
Test-mailflow -ErrorLatency:10 -ExecutionTimeout:240 -MonitoringContext
$true -verbose |FL
VERBOSE: Test-Mailflow : Beginning processing.
VERBOSE: Test-Mailflow : Searching objects "EXCHANGE1" of type "Server" under
the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on domain controller
'dc00.domain.com'.
VERBOSE: Test-Mailflow : Searching objects
"SystemMailbox{b165188e-d22c-43d0-928d-c0b1e0c5cee2}" of type
"ADSystemMailbox"
under the root "$null".
VERBOSE: Test-Mailflow : Previous operation run on global catalog server
'dc00.domain.com'.
VERBOSE: Testing mail flow.
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest : False
Events : {Source: MSExchange Monitoring Mailflow Local
Id: 1002
Type: Error
Message: The delivery receipt for the test message from
main.com was not received within the error latency time
out of 10 seconds. The cmdlet will keep waiting until
the
execution timeout or the arrival of the delivery
receipt
., Source: MSExchange Monitoring Mailflow Local
Id: 1001
Type: Error
Message: The delivery receipt for the test message from
main.com was not received within the execution timeout
of 240 seconds. The cmdlet will not wait any longer
for t
he delivery receipt.}
PerformanceCounters : {Object: MSExchange Monitoring Mailflow Local
Counter: Mailflow Latency
Instance: EXCHANGE1
Value: -1}
VERBOSE: Test-Mailflow : Ending processing.
Subject: Test-Mailflow edc12594-5326-4270-9a3f-01c48b79896b
66c7004a-6860-44b2-983a-327aa3c9cfec
________________________________
Sent by Microsoft Exchange Server 2007

Post by Steven Halsey [MSFT]
You can try using tools like the Exchange Mail Flow Troubleshooting
Assistant (http://msexchangeteam.com/archive/2006/08/07/428616.aspx) to
diagnose the issues.
I believe it uses the same test-mailflow commandlet, and has extra
diagnostics to help troubleshoot the issue, such as tracking the message
through message tracking.
When you ran the test-mailflow in verbose mode where did the email address
used map to? Was it a System Mailbox on an MDB on the same server that you
were running the mailflow test from? If this mailbox is on the same server
then the commandlet is targetting an appropriate system mailbox.
I believe you would need to use a tool like ldp.exe or adsiedit.msc to look
at the System Mailboxes as they are hidden from the Exchange UIs.
You want to see if the attributes proxyaddresses, and HomeMDB map correctly
to the objects. For instance the System Mailbox below, is homed on
"Ex2007mp3-mbx1\TestStorageGroup\TestPrivateMDB1".
Dn: CN=SystemMailbox{9C567385-6724-4DFA-864B-09A81589C9D0},CN=Microsoft
Exchange System Objects,DC=Ex2007mp3,DC=Local
CN=TestPrivateMDB1,CN=TestStorageGroup,CN=InformationStore,CN=Ex2007mp3-mbx1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MPTest
Exchange Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=Ex2007mp3,DC=Local;
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Frost''''IK
All storages are online. How can I check that my system mailboxes are
ok?
I
cannot see any system mailboxes in Exchange Management Console. The cmdlet
get-mailbox does not show any system mailbox too.

Post by Steven Halsey [MSFT]
Test-mailflow does not use the same mailbox created by the
New-TestCasConnectivityUser.ps1. Test-mailflow uses the system
mailboxes
of
the two servers involved in the transaction.
New-TestCasConnectivityUser.ps1 creates a user that is used by the Client
Access and Unified Messaging Transactions.
You should figure out why mail to the system mailbox can not be
recieved,
is
the MDB offline that owns the System Mailbox? Has the System Mailbox been
moved to a different server?
You can't control which mailbox is used on each server. In the current
Exchange 2007 Converted MP Exchange decides which mailbox will be the target
of the Mailflow based on a round robin between the servers for Remote
Mailflow. For Example 3 servers A,B,and C. A sends to B, B sends C, C sends
A. If B happens to be a test server that isn't available then the
send
from
A to B will fail and you see errors like you are seeing with the time outs.
You can override the the target mailbox server for A by adding the
value -targetmailboxserver:C to the cmdletCommand parameter.
--
Steven Halsey [MSFT]

[Frost''''IK]

There is Symantec Mail Security for Microsoft Exchange on my hub servers and
it can change subject of incoming from outside messages to SPAM: subject...
But it does not even check internal mail and as you can see below the subject
is not changed.

Post by Frost''''IK
Subject: Test-Mailflow edc12594-5326-4270-9a3f-01c48b79896b
66c7004a-6860-44b2-983a-327aa3c9cfec
________________________________
Sent by Microsoft Exchange Server 2007