I have been able to e-mail invoices to customers, just 2 weeks ago, using the Print Invoices option and selecting the email box when the Preview, Printer, Email, File option comes up.  The only thing that has changed is my userid is no longer an administrator.
Other scenarios:
I am logged onto my PC, logged into EVO as our temp, and can not send e-mail invoices.
I am logged onto a different computer, logged into EVO as our temp, who is NOT an administrator, and can e-mail invoices.
We have 2 other PC's that used to be able to e-mail invoices in previous versions but can not now.
 
Apparently it is not the administrator that was tied to my userid.  Nothing has changed on my computer it's self, but apparently that is what it is.  Can anyone help determine what we need to look at to fix this?
 
 
Version 7/26/13 SP1
 
Thanks.

The email settings are stored on the local computer tied to the Evo login ID and the company.  They are set at Settings US-A.  You need to create the email settings logged in as the user in question on that machine.

If you go back to US-A are the settings still there?  I have seen them go missing, not sure how or why.  They are stored in EVOSETTINGS.INI in the C:\ISTS folder if you want to make a backup of that file.

One by one our PC's quite being able to e-mail invoices, which now totals 4.  Is there a limit on how many you can send?  lol  Any idea as to why this is happening?  I could e-mail invoices yesterday from this last PC but not today.  Just comes back with E-mail NOT sent.
 
Help please.

I checked with our IT and nothing has changed on our e-mail server.  I have been deleting the files from the folder that stores the sent e-mails every month.  Hum, we are down to one pc that can still send e-mails.  Hopefully it won't fail us too soon.

David,  you will still hit a file number limit and it will cause strange things to happen in your system.  
 
We had another program that would generate a small file for everything it printed and every 6 months or so the system would start to crawl.  We never opened this folder, but when the system would try and write to this folder it would cause issues.
 
Just FYI -