mnguyen021997
asked on
trapping an SMTP request
i am looking to have a handler called when any mail application submits a "send mail" via smtp. is there a way to hook all smtp requests from a mail client within windows?
There are many ways and they all have pro/cons. Perhaps a bit more about what you are trying to accomplish would help...
ASKER
so when a user trys and sends mail through either OE, eudora, netscape, etc i would like to trap that request and trigger an application to be launched (for all intents and purposes, it could be an MS Agent or something to greet them).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
is there not a way to hook it from a registry entry? i was under the assumption you could write your own protocol handler by redirecting some entries in the registry.
robpitt,
Interesting idea about the SPI. It's one of those Winsock 2 features that has gone practically unnoticed. I'm not sure what is more thinly documented, the NDIS driver interface or the WINSOCK 2 SPI....
mnguyen,
There is a grain of truth to what you are saying but the implications are large. True, a registry entry is all it takes to insert a driver into the Windows network protocol stack but, and this is a big BUT, what you do must be a fully compliant driver for the place where you insert it. If not, you'll almost certainly get a BLUE SCREEN and a really messy situation. I pointed you to the NDIS intermediate driver since it's far simpler that a full-blown NDIS network driver or a protocol driver.
Interesting idea about the SPI. It's one of those Winsock 2 features that has gone practically unnoticed. I'm not sure what is more thinly documented, the NDIS driver interface or the WINSOCK 2 SPI....
mnguyen,
There is a grain of truth to what you are saying but the implications are large. True, a registry entry is all it takes to insert a driver into the Windows network protocol stack but, and this is a big BUT, what you do must be a fully compliant driver for the place where you insert it. If not, you'll almost certainly get a BLUE SCREEN and a really messy situation. I pointed you to the NDIS intermediate driver since it's far simpler that a full-blown NDIS network driver or a protocol driver.
ASKER
i actually thought it was easier then that. at least for "http" you could even devise your own protocol "mnguyenTP" that is used. but perhaps this is used only in the context of a browser.
I'm not sure at all what you are referring to unless it is the HTTP PROXY protocol. That's really easy to "tap into" via the proxy settings in all browsers. SMTP does NOT have a proxy protocol that is commonly used so you're back to my earlier suggestion about a local server. This is essentially a proxy for the real SMTP.