Here's my crazy idea, tell me if you've done something similar:
Scenario: An Intranet asp.net application.
- Email gets downloaded from a mail server to my web server
- The web application stores the mail information within
SQL Server
Scenario #1:
- User access their mail through the asp.net, and a web
interface
Scenario #2:
- Users access their mail from Outlook, but the mail is sent
from teh web server (somehow simulating a "mail server"
.
Has anyone done something similar to this?
I know what you're thinking: If they have a web mail interface, why would they use outlook?! Well, they have to buy Office XP with our software (because we use some Office dll's elsewhere in the system, which isn't all web based), so if they purchase Outlook we can't really tell them not to use it.
However, there must be some way to be able to *fool* outlook into thinking its hitting an email server when its really just hitting a service on the web server that takes the information, makes mail messages, and sends them back.
Thoughts?
Thanks,
D'Arcy
Scenario: An Intranet asp.net application.
- Email gets downloaded from a mail server to my web server
- The web application stores the mail information within
SQL Server
Scenario #1:
- User access their mail through the asp.net, and a web
interface
Scenario #2:
- Users access their mail from Outlook, but the mail is sent
from teh web server (somehow simulating a "mail server"
Has anyone done something similar to this?
I know what you're thinking: If they have a web mail interface, why would they use outlook?! Well, they have to buy Office XP with our software (because we use some Office dll's elsewhere in the system, which isn't all web based), so if they purchase Outlook we can't really tell them not to use it.
However, there must be some way to be able to *fool* outlook into thinking its hitting an email server when its really just hitting a service on the web server that takes the information, makes mail messages, and sends them back.
Thoughts?
Thanks,
D'Arcy