Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Unable to send one-time and scheduled reports through Exchange 2007/2010 as the SMTP server

    • Updated:
    • 22 Oct 2015
    • Product/Version:
    • Worry-Free Business Security Standard/Advanced 7.0
    • Worry-Free Business Security Standard/Advanced 8.0
    • Worry-Free Business Security Standard/Advanced 9.0
    • Platform:
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2000 Advanced Server
    • Windows 2000 Professional
    • Windows 2000 Server
    • Windows 2003 Enterprise
    • Windows 2003 Server R2
    • Windows 2003 Small Business Server
    • Windows 2003 Small Business Server R2
    • Windows 2003 Standard
    • Windows 2008 Enterprise
    • Windows 2008 Essential Business Server
    • Windows 2008 Server R2
    • Windows 2008 Small Business Server
    • Windows 2008 Standard
    • Windows 2011 Small Business Server Essentials
    • Windows 2011 Small Business Server Standard
    • Windows 2012 Enterprise
    • Windows 2012 Server Essentials
    • Windows 2012 Standard R2
    • Windows 2012 Web Server Edition
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows 8 32-bit
    • Windows 8 64-bit
    • Windows 8.1 32-bit
    • Windows 8.1 64-bit
    • Windows Mobile 5 Pocket PC
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Tablet PC
Summary

After installing Worry-Free Business Security (WFBS), you cannot send one-time and scheduled reports using the Exchange 2007 or 2010 as the SMTP server.
When you check the Ofcdebug.log, it shows that a report is successfully generated:

[rptman_Notification.cpp(143)]2012 05/23 11:51:19 [3990 : 3e84] (00) (E) [CMDHPMC][ofcservice.exe][ReportManager::ReplaceServerNameToken] truncate occured. szSubject:[[Security Server - GLOBAL-DC]Security Server Report] - [rptman_Notification.cpp(82)]
2012 05/23 11:51:19 [3990 : 3e84] (00) (D) [CMDHPMC][ofcservice.exe]_INI_SMTP_AUTH_ID=[] - [rptman_Notification.cpp(193)]
2012 05/23 11:51:19 [3990 : 3e84] (00) (D) [CMDHPMC][ofcservice.exe]_INI_SMTP_AUTH_PW=[***] - [rptman_Notification.cpp(196)]
2012 05/23 11:51:19 [3990 : 3e84] (00) (D) [CMDHPMC][ofcservice.exe]_INI_SMTP_AUTH_METHOD=[0] - [rptman_Notification.cpp(199)]
2012 05/23 11:51:24 [3990 : 3e84] (00) (W) [CMDHPMC][ofcservice.exe][ReportManager::NotifyByEmail] HOST:exchange.criso.com,PORT:25,TO:administrator@criso.com,Err:-4000029 - [rptman_Notification.cpp(219)]
2012 05/23 11:51:24 [3990 : 3e84] (00) (W) [CMDHPMC][ofcservice.exe][ReportManager::NotifyByEmail] zMailBody:A new report was generated at 5/23/2012 11:51:19.

However, the following error appears when running a packet capture while sending the report:

530 5.7.1 Client was not authenticated

Packet Capture

Click image to enlarge.

Details
Public

This issue happens because, by default, the Exchange 2007 or 2010 only accepts secured and authenticated connections. In this case, WFBS tries to connect to the SMTP server even without any authentication. This causes the said server to respond with "530 5.7.1 Client was not authenticated".

To resolve the issue:

  1. Open the Exchange Management Console.
  2. Go to Server Configuration > Hub Transport.
  3. Click New Receive Connector on the right pane.
  4. Enter a name for the connector (e.g. WFBS Report / OSCE Report).
  5. Select Internal under the Select the intended use for this Receive connector section, and then click Next.

    New Receive Connector

    Click image to enlarge.

  6. Click Edit to set the IP address(es) that Exchange will accept connections from.
  7. Enter the Security Server IP address on the Start Address and End Address fields. This allows only the Security Server to use this connector.

    Edit Remote Servers

    Click image to enlarge.

  8. Click Next, and then click Finish. The new receive connector should appear under the Server Configuration > Hub Transport.
  9. Right-click the new receive connector and click Properties.

    Receive Connector

    Click image to enlarge.

  10. Go to the Permissions Groups tab and tick Anonymous users check box.
  11. Click Apply and click OK.

    Permissons Groups

Premium
Internal
Rating:
Category:
Troubleshoot; Install; Upgrade; Update
Solution Id:
1112772
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.