Prev: SBS 2008 Backup-Fails with Creation of the shared protection point
Next: CTIW Fails When Looking for Router
From: "Robbin Meng [MSFT]" on 23 Nov 2009 04:15

Hello Dave,

Thanks for your post and Larry's input.

Does the blocking reprot mail issue just occur? Has the report ever worked before?

To troubleshoot this issue, at this point, I would like to provide some suggestions:

1. Please open SBS console and locate to "Monitoring and Reporting". Click the "Change server status settings" option and check remove the old report and create a new one with the
administrator(a)yourdomain.com as email recipient.

2. Please open SBS console and locate to "Monitoring and Reporting". Click "Setup Monitoring Reports and Alerts" and then select "reinstall Monitoring status". Follow and finish the wizard, select
administrator(a)yourdomain.com as email recipient too.

3. If the issue persists that the above defined recipient still cannot receive the report email, then please follow the steps in below Message Tracking article to track all the mail flow of recipient and
check whether the email has been sent to that user or not.

If the report email has been sent but the recipient didn't received, it should be a mail transport issue. Otherwise, if the report email has not been sent or generated, it should be a corrupted Monitoring and
Report issue. Please track it and we can perform further steps according to the Message Tracking results.

Exchange 2003 Message Tracking and Logging
http://www.msexchange.org/tutorials/Exchange-2003-Message-Tracking-Logging.html

Hope this helps. Also, if you have any questions or concerns, please do not hesitate to let me know.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================



From: Dave on 23 Nov 2009 15:48
This report I'm talking about comes from outside the network, vendors server

can't do #1 monitoring hasn't been setup
did #2

--
Dave


""Robbin Meng [MSFT]"" wrote:

>
> Hello Dave,
>
> Thanks for your post and Larry's input.
>
> Does the blocking reprot mail issue just occur? Has the report ever worked before?
>
> To troubleshoot this issue, at this point, I would like to provide some suggestions:
>
> 1. Please open SBS console and locate to "Monitoring and Reporting". Click the "Change server status settings" option and check remove the old report and create a new one with the
> administrator(a)yourdomain.com as email recipient.
>
> 2. Please open SBS console and locate to "Monitoring and Reporting". Click "Setup Monitoring Reports and Alerts" and then select "reinstall Monitoring status". Follow and finish the wizard, select
> administrator(a)yourdomain.com as email recipient too.
>
> 3. If the issue persists that the above defined recipient still cannot receive the report email, then please follow the steps in below Message Tracking article to track all the mail flow of recipient and
> check whether the email has been sent to that user or not.
>
> If the report email has been sent but the recipient didn't received, it should be a mail transport issue. Otherwise, if the report email has not been sent or generated, it should be a corrupted Monitoring and
> Report issue. Please track it and we can perform further steps according to the Message Tracking results.
>
> Exchange 2003 Message Tracking and Logging
> http://www.msexchange.org/tutorials/Exchange-2003-Message-Tracking-Logging.html
>
> Hope this helps. Also, if you have any questions or concerns, please do not hesitate to let me know.
>
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
> ==================================================================
> Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
> https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect website:
> https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx
>
> If you want to use a newsreader other than a web forum to access these newsgroups,
> please refer to the following blog to apply NNTP password and configure a newsreader:
> http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
> ==================================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ==================================================================
>
>
>
> .
>
From: "Robbin Meng [MSFT]" on 23 Nov 2009 22:07

Hi Dave,

Thanks for your response.

I think Larry has delivered good analysis as well as suggestions. Please take your time and use Message Tracking to check whether your SBS received the report email and dropped it finally. If so, let
us know what the detailed error messages recorded so that we can perform further research and find out if it is caused by your SBS server side or the sender side.

Moreover, here is a tool to test Inbound SMTP Email to see if there is any improper configuration of your SMTP virtual server.

Exchange Server Remote Connectivity Analyzer Tool(ExRCA).

Inbound SMTP Email Test
http://www.msexchange.org/articles_tutorials/exchange-server-2007/tools/exchange-server-remote-connectivity-analyzer-tool-part2.html

Here is the tool:
https://www.testexchangeconnectivity.com/Default.aspx

Other tool:
Microsoft Windows Small Business Server 2003 Best Practices Analyzer
<http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3874527a-de19-49bb-800f-352f3b6f2922>

Hope it helps.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support


From: Ace Fekay [MCT] on 24 Nov 2009 01:04
"Dave" <Dave(a)discussions.microsoft.com> wrote in message
news:A9CD3A16-98D9-4F3D-9727-DF5B87B24EC8(a)microsoft.com...
> It's not internal, comes from a vendor's server.
> --
> Dave
>

I know a lot of info was covered in this thread between everyone, but I just
wanted to understand the scenario a little better. Are you saying that the
report is coming from a a server somewhere on the Internet and not inside
your network? If so, is the report's "From:" address an internal user's
actual email address, such as AnInternalUser(a)yyy.com, or is it the "From:"
address a name that is not an actual internal user, yet has the same domain
suffix as your mail server, such as
someUserThatDoesNotExistInternally(a)yyy.com?

If so, have you configured the IMF, or do you have a third party spam
software. If so, I would look at either of their settings.

Otherwise, are you using a POP3 connector?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.





From: Dave on 30 Nov 2009 10:23
Okay,
ran the smtp inbound test, see below:

Testing Inbound SMTP Mail flow for domain payroll(a)qqest.com
Inbound SMTP mail flow was verified successfully.
Test Steps
Attempting to retrieve DNS MX records for domain qqest.com
Successfully retrieved one or more MX records from DNS
Additional Details
MX Records Host mail.qqest.com, Preference 1


Testing Mail Exchanger mail.qqest.com.
This Mail Exchanger was tested successfully.
Test Steps
Attempting to resolve the host name mail.qqest.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 67.137.30.226

Testing TCP Port 25 on host mail.qqest.com to ensure it is listening and
open.
The port was opened successfully.
Additional Details
Banner Received: 220 barracuda.qqest.com ESMTP
(3869784aaaa24f32f8070d56dce0275b)

Attempting to send test email message to payroll(a)qqest.com using MX
mail.qqest.com.
The test message was delivered successfully.
Testing the MX mail.qqest.com for open relay by trying to relay to user
Admin(a)TestExchangeConnectivity.com
Open Relay test passed. This mx is not an open relay
Additional Details

didn't understand the article




--
Dave


""Robbin Meng [MSFT]"" wrote:

>
> Hi Dave,
>
> Thanks for your response.
>
> I think Larry has delivered good analysis as well as suggestions. Please take your time and use Message Tracking to check whether your SBS received the report email and dropped it finally. If so, let
> us know what the detailed error messages recorded so that we can perform further research and find out if it is caused by your SBS server side or the sender side.
>
> Moreover, here is a tool to test Inbound SMTP Email to see if there is any improper configuration of your SMTP virtual server.
>
> Exchange Server Remote Connectivity Analyzer Tool(ExRCA).
>
> Inbound SMTP Email Test
> http://www.msexchange.org/articles_tutorials/exchange-server-2007/tools/exchange-server-remote-connectivity-analyzer-tool-part2.html
>
> Here is the tool:
> https://www.testexchangeconnectivity.com/Default.aspx
>
> Other tool:
> Microsoft Windows Small Business Server 2003 Best Practices Analyzer
> <http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3874527a-de19-49bb-800f-352f3b6f2922>
>
> Hope it helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>
> .
>
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: SBS 2008 Backup-Fails with Creation of the shared protection point
Next: CTIW Fails When Looking for Router