Windows SBS 2008 cannot send reports via email


  • When I try to configure SBS 2008 to send reports in the SBS Console via email, I get an error that it could not send it.  Here are details from the console.log and protocol logs:

    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,2,,,>,"220 Microsoft ESMTP MAIL Service ready at Sun, 14 Mar 2010 16:01:25 -0500",
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,3,,,<,EHLO SBS,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,4,,,>, Hello [],
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,5,,,>,250-SIZE,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,6,,,>,250-PIPELINING,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,7,,,>,250-DSN,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,8,,,>,250-ENHANCEDSTATUSCODES,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,9,,,>,250-STARTTLS,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,10,,,>,250-X-ANONYMOUSTLS,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,11,,,>,250-AUTH NTLM,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,12,,,>,250-X-EXPS GSSAPI NTLM,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,13,,,>,250-8BITMIME,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,14,,,>,250-BINARYMIME,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,15,,,>,250-CHUNKING,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,16,,,>,250-XEXCH50,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,17,,,>,250 XRDST,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,18,,,<,AUTH ntlm,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,19,,,>,334 <authentication response>,
    2010-03-14T21:01:25.901Z,SBS\Default SBS,08CC91D09FC4ABEF,20,,,*,,Inbound authentication failed as we reject well-known account authentication for ZZZZZ\Administrator
    2010-03-14T21:01:30.926Z,SBS\Default SBS,08CC91D09FC4ABEF,21,,,>,535 5.7.3 Authentication unsuccessful,
    2010-03-14T21:01:30.926Z,SBS\Default SBS,08CC91D09FC4ABEF,22,,,<,MAIL FROM:<>,
    2010-03-14T21:01:35.934Z,SBS\Default SBS,08CC91D09FC4ABEF,23,,,>,530 5.7.1 Client was not authenticated,
    2010-03-14T21:01:35.934Z,SBS\Default SBS,08CC91D09FC4ABEF,24,,,-,,Local

    And in console.log:

    [11836] 100314.160121.3753: Reporting: GenerateReport: Start Generating report
    [11836] 100314.160121.6095: Reporting: GenerateReport: Finished Generating report
    [11836] 100314.160121.6719: AdminTME: Status: TaskId = TaskGenerateMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: True, Warning: False, Continue: True, Message: 
    [11836] 100314.160135.9347: Exception: 
    An exception of type 'Type: System.Net.Mail.SmtpException, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
    Timestamp: 03/14/2010 16:01:35
    Message: The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated
    Stack:    at System.Net.Mail.MailCommand.CheckResponse(SmtpStatusCode statusCode, String response)
    	   at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
    	   at System.Net.Mail.SmtpClient.Send(MailMessage message)
    	   at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MailUtil.SendMail(String from, String[] to, String subject, Boolean isBodyHTML, String body, String inlineAttachmentPath, String[] attachments)
    [11836] 100314.160137.2921: AdminTME: Status: TaskId = TaskEmailMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: False, Warning: False, Continue: False, Message: 
    [11700] 100314.160137.2921: AdminTME: Committer: Completed called
    [11700] 100314.160137.2921: AdminTME: Committer: Task was cancelled.

    Since SBS 2008 by default tries to send out as the logged in account when you try and test it I cannot really change that. Any help would be appreciated.
    domingo, 14 de marzo de 2010 21:15


Todas las respuestas

  • You may want to check out this thread:

    Since this is SBS and is a different beast than Exchange, I suggest asking any further questions in the SBS 2008 forums:

    • Marcado como respuesta pwnell martes, 16 de marzo de 2010 17:35
    lunes, 15 de marzo de 2010 0:13
  • Thanks, I have read those articles.  I ended up creating a new administrator user with domain admin privileges, and when using that I can send out the test SBS reports just fine.  It is just when you are logged in as the standard Administrator user that it does not work due to Exchange policies.

    martes, 16 de marzo de 2010 17:35
  • I have same problem with pwnell.
    I can authenticate relay with all user account.   but not default build-in "administrator" account.

    there must be some inherit deny permission somewhere that control this.   

    as pwnell mention about "exchange policies" or  default "administrator" account is not allowed by design"

    anyone know how to make "administrator" work on authenticate relay in exchange 2007 ???

    sábado, 20 de noviembre de 2010 2:56
  • This happened to me after I reinstalled Symantec End Point protection on the server. Could be coincidental though.

    Trace looked like this (abbreviated):

    Inbound authentication failed as we reject well-known account authentication for MyDomain\Administrator

    ,SERVER2\Default SERVER2, ,*,,User Name: NULL

    ,SERVER2\Default SERVER2, ,*,Tarpit for '0.00:00:05',

    ,SERVER2\Default SERVER2, ,>,535 5.7.3 Authentication unsuccessful,

    ,SERVER2\Default SERVER2, ,<,MAIL FROM:<>,

    ,SERVER2\Default SERVER2, ,*,Tarpit for '0.00:00:05',

    ,SERVER2\Default SERVER2, ,>,530 5.7.1 Client was not authenticated,

    ,SERVER2\Default SERVER2, ,-,,Local

    What I did to fix this was to use a second receive connector that I had set up previously for a scanner to email to users through the server. This allowed anonymous authentication and was just set for the IP address of the scanner. I simply added the IP address of the server to this connector and restarted the transport service.

    Hope this helps someone!


    sábado, 30 de marzo de 2013 13:38