using (
}

Is essentially the same as:

try {
}
finally {
thing.dispose();
}

I’ve heard numerous complaints about Stream(Writer/Reader), SqlConnection, MailMessage, and a few others slowly hogging memory unless you explicitly dispose() them, since they’re unmanaged objects.  

In any case, I don’t see that it needs a new namespace, but then, I haven’t read C# Best Practices. By Python/C++ reasoning, since there ought not to be any duplication of method/class/variable names in the class, a new namespace isn’t necessary. Any particular reason why I should use a namespace for it? 

Yes, that’s a complete if. I could use &&, but it seems more readable without. 

All the lblXXXX and txtXXXX methods are fucking delegates. Actually, the only delegates he had in the code.

public delegate void TextlblDisplayTodayAddCallback(string textdisplaytodayadd);
private void TextlblDisplayTodayAdd(string textdisplaytodayadd)
{
     try
     {
          if (lblFaxesTodayDisplay.InvokeRequired)
          {
               TextlblDisplayTodayAddCallback d = new
               TextlblDisplayTodayAddCallback(TextlblDisplayTodayAdd);
     Invoke(d, new object[] { textdisplaytodayadd });
          }
          else
          {
               lblFaxesTodayDisplay.Text = textdisplaytodayadd;
          }
     }
     catch (Exception f)
     {
     MessageBox.Show("Error : " + f.Message);
     }
}

Presumably this avoids deadlock conditions or… something. I can’t even tell what the fuck the point of it is. A look on MSDN tells me that Windows forms are not threadsafe, and this is supposed to help that (since these are sometimes called from outside threads), but it seems kludgy. I haven’t looked into replacing these yet. Still about halfway through the code trying to de-spaghettify it. 

Tons of these around, too:

if (textBox1.Text == "")
{
     TextbtnStartadd("The program is missing the ini file.  You are not allowed to start faxing.");
}
else
{
     Textbox1Append("\r\nThe program is missing the ini file.  You are not allowed to start faxing.");
}

Some with slightly varying syntax, but they’re all just a waste of code.

First, make namespaces and call them with using. Your first replacement block has reset.Dispose(), but you don’t need to (and shouldn’t, by best practices) call anything.Dispose(). If you call a using statement inside your method call/class, the class called by that statement will automatically be disposed when the call ends. Then again, you say memory management is not a real issue with this.

Also, because I don’t see a /*snip*/ here, I’m assuming this is a complete if statement?

if (totalSeconds % 3600 == 0)
{
if (totalSeconds == 0)
{
log.Rotate(fileErrorLog);
reset.Labels(true, true);
reset.Counts(true, true);
}
else
{
reset.Labels(false, true);
reset.Labels(false, true);
}
reset.Dispose();
}

If it is, you can use && (as you used before) to save a bit on code complexity.

The various lblXXXX and txtXXXX methods in Form1 would probably be worthy of inclusion on the Daily WTF, because he’s yet again reinventing the wheel. TextBox1Add(string), really? Not TextBox1.Text = TextBos1.Text.ToString() + string? I guess he doesn’t know what boxing is, as we talked about yesterday.