Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Anders Brohäll 295 posts 561 karma points c-trib
    Nov 04, 2013 @ 17:06
    Anders Brohäll
    0

    Email not being sent #2

    Hi,

    After upgrading from 3.0.15 to 3.0.17 sending email stopped working. 
    I don't know why, and i cant really debug the problem. 

    I'm certain that my SMTP settings are correct, aswell as the notifications/email part of umbracoSettings.config.

    I upgraded with the UmbracoContour_3.0.17_update.zip package. 

    I've tried both "network" and "specifiedPickupDirectory" as deliveryMethod in system.net/mailSettings/smtp with valid configurations - working with a simple System.Net.Mail.SmtpClient.Send() and w/ umbraco.library.Send(). Also, the umbracoLog doesn't log anything. 

    In web.config I've got these settings:

    <system.web>
    <httpModules>
      <add name="ContourFormBuilderHttpModule" type="Umbraco.Forms.CodeFirst.ContourFormBuilderHttpModule, Umbraco.Forms.CodeFirst" />
    </httpModules>
</system.web>
<system.webServer>
    <modules runAllManagedModulesForAllRequests="true">
      <add name="ContourFormBuilderHttpModule" type="Umbraco.Forms.CodeFirst.ContourFormBuilderHttpModule, Umbraco.Forms.CodeFirst" /> 
    </modules>
</system.webServer>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
</runtime> 

    Is there any settings i've missed?

    What can i do to debug it?
    Can I adjust the verbosity of the log?

    Copy Link
  • Anders Brohäll 295 posts 561 karma points c-trib
    Nov 04, 2013 @ 17:17
    Anders Brohäll
    101

    Found the problem and solved it.

    The upgrade script added a second assemblyBinding-section to web.config/runtime. 

    <runtime>
       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
    </assemblyBinding>  
    </runtime> 

     ... removing the secon sections solves the problem.

    Copy Link

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies