I have read through other posts about email not being sent and none of them seem to apply to my situation.  Here is what I have:

Server Hardware: 2 Intel Xeon 2.2 Ghz CPUs
OS: Microsoft Windows 2000 SP4
OnTime: 7.0.2.7191 (machine had OnTime 2006, which was uninstalled before 2007 was installed).
Problem: Since the upgrade to 2007, no email notifications have been sent.

I have checked: 

• All three OnTime services are running
• Suppress All Notifications is NOT set

I cannot check the database to see which DLL is being referenced because the machine only has SQL Server 2005 Express Edition which has no Management Studio installed.

When I run the "Test" for email I get this:

Trying to load assembly Axosoft.Common.SmtpClient.dll...
Loaded assembly Axosoft.Common.SmtpClient.dll successfully...
Setting mail assembly properties...
Trying to create a new mail message...
Created mail message successfully...
Setting message properties...
Trying to send email...
Error trying to send email; please review your exception log.

Looking at the Exception Viewer, I see the following two exceptions recorded at the time I run the test:

Exception Details
Exception ID:  421
Date:  6/1/2007 5:36 PM
Source:  System
Target Site:  Void Send(System.Net.Mail.MailMessage)
User:  Administrator
Message:  Failure sending mail.
Stack Trace:     at System.Net.Mail.SmtpClient.Send(MailMessage message)
   at Axosoft.Common.SmtpClient.SendEmail(IMailMessage message)
Additional Info:  ExceptionManager.MachineName -- Server007|ExceptionManager.TimeStamp -- 6/1/2007 5:36:42 PM|ExceptionManager.FullName -- Axosoft.Common.ExceptionManagement, Version=7.0.2.7191, Culture=neutral, PublicKeyToken=21e2e88ee444275a|ExceptionManager.AppDomainName -- OnTime.exe|ExceptionManager.ThreadIdentity -- 1|ExceptionManager.WindowsIdentity -- DOMAIN\Administrator|
Exception Type:  SmtpException

...and...

Exception Details
Exception ID:  420
Date:  6/1/2007 5:36 PM
Source:  System
Target Site:  System.Net.Mail.LineInfo Send(System.Net.Mail.SmtpConnection, System.String)
User:  Administrator
Message:  Object reference not set to an instance of an object.
Stack Trace:     at System.Net.Mail.AuthCommand.Send(SmtpConnection conn, String message)
   at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
   at System.Net.Mail.SmtpTransport.GetConnection(String host, Int32 port)
   at System.Net.Mail.SmtpClient.GetConnection()
   at System.Net.Mail.SmtpClient.Send(MailMessage message)
Additional Info:  ExceptionManager.MachineName -- Server007|ExceptionManager.TimeStamp -- 6/1/2007 5:36:42 PM|ExceptionManager.FullName -- Axosoft.Common.ExceptionManagement, Version=7.0.2.7191, Culture=neutral, PublicKeyToken=21e2e88ee444275a|ExceptionManager.AppDomainName -- OnTime.exe|ExceptionManager.ThreadIdentity -- 1|ExceptionManager.WindowsIdentity -- DOMAIN\Administrator|
Exception Type:  NullReferenceException

(Note: any personally identifiable information has been changed to protect the innocent).

Anyone have a clue what is going on here?

Thanks,
Dave Parker
IT SystemWorks

What do you use for your SMTP server?  Does it require authentication?

I think I have at least a lead on the issue.  This is actually a client that I am doing some IT work for and it turns out they recently switched from one ISP to another.  The Axosoft installation was trying to send email out through an account (which still exists) at the old ISP, but is doing so through the new ISP's network.  Thus, the old ISP is rejecting the send request as unauthorized.  Since I did not have any login info for the new ISP, I just put in the full credentials for the old one and that seems to have fixed the problem.   

So, the answer to your question is: No, it did not require authentication in the past, but Yes, now it does (if I want to use the same sonic.net account).

P.S.  Before anyone pipes up, yes, I will switch to an account at the new ISP as soon as I get the information from the client.

P.P.S. Please considered this a bug report/feature request to provide better error reporting for this condition.

Thanks,
Dave Parker
IT SystemWorks