While building a business application for internal use, I found that McAfee wanted to block all of my outgoing emails from my app. I also noticed that something (McAfee) was blocking my ability to telnet to an SMTP server on port 25. My application needed email capability, and I didn’t have time (or money) to negotiate with McAfee to get the application added to their special white-list.
So I asked my self the question, “How does outlook get around it? Or Thuderbird?”. The answer is that McAfee keeps a white-list of applications that are allowed to send mail.
You can find this list in the McAfee program under the Access Protection Properties.Under the properties you’ll see a listing of categories on the left side. Click on the category marked Anti-virus Standard Protection. On the
right side you’ll see Prevent Mass Mailing Worms From Sending Email. If you click edit while high-lighting this, you’ll see the list of applications that can send email, also know as the white-list.
This was my white-list. Choosing any of these as your assembly name will allow your application to email on computers using McAfee.
agent.exe, amgrsrvc.exe, apache.exe, ebs.exe, eudora.exe, explorer.exe, firefox.exe, firesvc.exe, iexplore.exe, inetinfo.exe, mailscan.exe, MAPISP32.exe, mdaemon.exe, modulewrapper*, mozilla.exe, msexcimc.exe, msimn.exe, mskdetct.exe, msksrvr.exe, msn6.exe, msnmsgr.exe, neo20.exe, netscp.exe, nlnotes.exe, nrouter.exe, nsmtp.exe, ntaskldr.exe, opera.exe, outlook.exe, Owstimer.exe, pine.exe, poco.exe, RESRCMON.EXE, rpcserv.exe, SPSNotific*, thebat.exe, thunde*.exe, tomcat.exe, tomcat5.exe, tomcat5w.exe, VMIMB.EXE, webproxy.exe, WinMail.exe, winpm-32.exe, worldclient.exe, wspsrv.exe
I haven’t had much luck in adding my exe name to this list – always seems to disappear after a certain period of time. So, I just changed my exe name to one that was on the list.
I Visual Studio 2008, you perform that in the project properties. In this case, I just used the exe name neo20.exe. I don’t know what application that belongs to, but it lets me send mail on PCs running McAfee.Changing this has no effect on your actual project name, it only changes the name of the exe at run time.
I should also note that this will not allow your message to send emails during debugging sessions since Visual Studio actually runs the project as yourAssemblyName.vshost.exe. You’d have to add *.vshost.exe to the McAfee white-list. I could never get it to stick.
Here is an example of an error you may receive in Visual Studio if McAfee is blocking your application from sending mail