For full details check Scott's announcement DasBlog 1.9.7 Release - Final ASP.NET 1.1 Version

This will be the last version written for dot net 1.1 and the blog engine that could will move off to the richer 2.0 class library.  The next milestone will be DasBlog 2.0 which will be compiled under Visual Studio 2005 ( One could use Orcas) and run in medium trust environments.  This should allow for DasBlog to run in most hosted environments.

SMTP Server = relay-hosting.secureserver.net

Notification E-Mail address = WhateverYouWant@yourdoman.com

check Enable SMTP basic Authentication

You will need one of your godday.com email account user name and passwords for sending.

Smtp user name= youremail@yourdoman.com

smtp password= yourdoman email password

smtp port = 25

Have fun.  I wouldn't recommend having notifications for referrals and pingbacks.

Its events like this that make me wonder why I run my own DasBlog engine and not some Wordpress or Blogger site.

2007-03-12 19:12:51 PM
450
PingbackServerError:
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at CookComputing.XmlRpc.XmlRpcClientProtocol.GetWebResponse(WebRequest request)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at newtelligence.DasBlog.Runtime.Proxies.PingbackClientProxy.ping(String sourceUri, String targetUri)
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.Pingback(String sourceUri, String pingbackService, String pingbackTarget, String entryTitle)
while processing http://thisoldcode.microfisch.com/PermaLink,guid,830a2557-66ad-48e2-ae67-16e2beaccd71.aspx,http://blogs.zdnet.com/microsoft/?p=315.

When DasBlog throws up, it really does a number on your shoes.

Although the application did not come to a crashing halt my Sirius post early set off an exception, the URL i posted cause to many redirects.  That is not a problem DasBlog handled it gracefully and logged the event.  but There is not error code for this event wich means I cannot view my activity event log with out throwing an exception.  Simple enough to correct rather then just parsing The int out of the events string I can use try catch.  Now i need to decide the severity of the bug, do i push this change to crazylittlethingcalledlamp, and underthemicrosope?  Will my brother or wife really care that they can see events? 

Here are the steps I took in order to run DasBlog under medium trust.
(To test dasBlog in development add the following to web.config.
    <system.web>
        <!--  level="[Full|High|Medium|Low|Minimal]" -->
         <trust level="Medium" originUrl=""/>)

 Add requirePermission=false attribute to the following sections  
 <configSections>
  <!-- USED FOR CUSTOM MACROS ONLY
        <section name="newtelligence.DasBlog.Macros" type="newtelligence.DasBlog.Web.Core.MacroSectionHandler, newtelligence.DasBlog.Web.Core" /> -->
        <section name="newtelligence.ControlImages" type="newtelligence.DasBlog.Web.Core.WebControls.ControlImageModuleSectionHandler, newtelligence.DasBlog.Web.Core" requirePermission="false" />
        <section name="newtelligence.DasBlog.UrlMapper" type="newtelligence.DasBlog.Web.Core.UrlMapperModuleSectionHandler, newtelligence.DasBlog.Web.Core" requirePermission="false"/>
        <!-- http compression handler section -->
        <sectionGroup name="blowery.web">
            <section name="httpCompress" requirePermission="false" type="blowery.Web.HttpCompress.SectionHandler, blowery.Web.HttpCompress"/>
        </sectionGroup>
    </configSections>
 
May need to update blowery.web
I changed based on dotnuke blog entry http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/67/threadid/11086/threadpage/1/scope/posts/Default.aspx
{
 The web.config change worked locally but not on my web host.  I was able to get my site working with Blowery HttpCompress v6 for .net 2.0 by modifying HttpCompress.cs line 85:
 From:
    string realPath = app.Request.Path.Remove(0, app.Request.ApplicationPath.Length+1);
 To:
    string realPath = Path.GetFileName(app.Request.Path);
}
I don't think this was necessary.  But it was the first step I took

XmlNamespaceUpgradeReader inherits from xmltextreader which has a demand of full trust, I just removed all references of  XmlNamespaceUpgradeReader.
 
Update to the latest freetextbox build or use a different control option.
 
Update latest version of basic date picker which has the script files embedded.  It’s important to note that you will need to add a compression exclusion path for webresource.axd in web.config.
 <blowery.web>
<excludedPaths>
<add path="WebResource.axd"/>
</excludedPaths>

Remove icsharp zip component or find an updated version that will run under medium trust.  I just switched to .net 2.0’s compression library.

Remove diagnostics.trace.write