• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

vbSendMail Virus Scan Issue

Hi,

I'm trying to use vbsendmail (freeware) to send emails from my app using smtp. Works fine on my personal computer, but at work having a problem with the virus protector. The app will be installed on a server and I cannot control the firewall nor the virus scan software.

How can I get around this?

thanks I'm quite at a loss....
0
surfsista9
Asked:
surfsista9
  • 4
  • 3
1 Solution
 
mugman21Commented:
"and I cannot control the firewall nor the virus scan software. " - Simple answer, your going to have too. Smtp will be sending the mail out on port 25, so make sure your firewall allows outbound traffic on that port (it should already).

Second, regarding the antivirus, which version is it, what company makes it. (I'm guessing McAfee here for some reason). If this is a standalone application, I don't think there should be a problem. Most AV's only hook into the popular email clients. I don't ever recall seeing a TDI filter included in an AV product, then again, never really looked.

I've never used this vbsendmail control before and have no idea how it works, if it is using outlook automation, then that's probably what is triggering the AV. If that is the case, writting an SMTP engine yourself should solve the AV problem. There are plenty of open source smtp engines in VB on planetsourcecode.com.

Mugman
0
 
surfsista9Author Commented:
vbsendmail is using wsock32 -- it is a freeware dll not a control. Apparently what I've read this dll is very mature and used quite a bit.  I haven't looked at the source code yet, but possibly there is something I can modify so this can work with McAfee?

You are right the AV is McAfee.
0
 
surfsista9Author Commented:
Vbsendmail is not using outlook automation at all.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mugman21Commented:
Sorry for the slow reply...

In that case, McAfee must include some sort of network filter (or it's hooking 'nasty like' as usual). McAfee is horrible about patching images in mem ect...

If there is no config option to disable the behavior that is giving your problems, don't try to defeat it. McAfee hooks so invasivly, you'll ultimatly make the system unstable if you try to bypass what it's doing. Remember, a large portion of it runs in kernel land, you can't compete on that level with VB.

The best way to get past this in my opinion would be to unistall McAfee. You can in turn install a different AV on this server, CA sucks but doesn't hook like McAfee does (at least not as bad).
0
 
surfsista9Author Commented:
Forgive my lack of knowledge...it seems I'm always stuck doing things I know little about. Do not ask me why...but, I'm curious how they are using smtp to send mail in other ways (other than wsock)  with McAfee. Somehow they must send mail using smtp. Guess I need to research.
0
 
mugman21Commented:
//Forgive my lack of knowledge...
Forgive my crappy way of expaining what is going on here.

//it seems I'm always stuck doing things I know little about.
This is how we all learn.

//I'm curious how they are using smtp to send mail in other ways (other than wsock)  with McAfee. Somehow they //must send mail using smtp.

It is using Winsock, since I haven't walked threw McAfee I can't tell you exactly what is happenin here but I can make some well informed guesses. McAfee hooks and patches in memory images a lot!!! What it is most likely doing is locating the 'in memory' image of the winsock dll. It then modifies the image in memory (it locates certain functions and modifies those by injecting it's own code). Then, when your program calls a winsock function, the call must go threw the normal winsock code, and then the code inserted into winsock by McAfee. Winsock is still being used, but it's behavior is modified from the code that McAfee injected. It's like taking a detour, you still get where you were going but it takes a little longer and you travel a different route. Same concept here, just with program flow - execution. This is esentially a hack and is a crappy method of doing this...

Now, after I just finished typing all that, I'm starting to have a vague recollection of McAfee using a LSP filter. I'm going to have to tear into McAfee later. Now I'm curious :-). I'll load McAffee onto my test machine tonight and fire up the kernel debugger to get a definitave answer on how McAfee does this....

None the less, switching AV products would still fix this. As I said earlier, trying to go around what McAfee is doing will lead to the system being unstable.

M

0
 
surfsista9Author Commented:
Thanks for the info.

Interestingly, it works on the server I needed it to work on (for another company) that has McAfee as well...so apparently they do not have this filter set. Eventually I will need to get this to work on the other company, so very interested in what you find out.

Surf
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now