| Author |
Message |
Mark M
Guest
|
 Posted:
Mon Dec 13, 2004 12:18 pm Post subject:
Correct technology for .net based mail application? |
|
|
Hi everyone.
Sorry if this question has been answered somewhere, (but I couldn't
really see one.)
What is the correct technology to use when you want to build a mail
application in .net?
The requirements are that the app must be able to connect to an
exchange 2003 server.
It must be able to read mail from a dedicated inbox and save the body
of the message to a file. It must be able to read and save any
attachments of the message.
It must be able to send a message from the same dedicated user. It
must be able to resolve recipient addresses prior to sending the
message. (which I think rules out webdav?) It must be able to attach
a small (5K) text file to the message.
It must run on a windows 2003 server which is not the exchange server.
Finally, (phew) it must be a pure .net application. No installing
libraries from other applications.
I have done a lot of reading on cdo, cdosys... smtp, pop3, webdav...
and have probably confused myself enough that I can't see an obvious
answer. I would like to use one technology for the entire project,
but if I have to use more than one, that's ok.
All suggestions welcome.
Mark.
|
|
| Back to top |
|
 |
Michael
Guest
|
| Posted:
Mon Dec 13, 2004 10:16 pm Post subject:
Re: Correct technology for .net based mail application? |
|
|
WebDAV can be good choice in your case, only question is about resolving
recipient address.
If your recipients are stored in Contacts folder (or some other folder) then
you can resolve recipient address with WebDAV.
If your recipients are stored in GAL then you can't use WebDAV to resolve
recipient address but you can use LDAP (also pure .NET).
Michael
-------------------------------
If you need WebDAV API for Exchange server,
use our component WebDAV .NET for Exchange.
Check out http://www.independentsoft.com
"Mark M" <AskMe@Maybe.Not> wrote in message
news:41be30ef.267075864@msnews.microsoft.com...
| Quote: | Hi everyone.
Sorry if this question has been answered somewhere, (but I couldn't
really see one.)
What is the correct technology to use when you want to build a mail
application in .net?
The requirements are that the app must be able to connect to an
exchange 2003 server.
It must be able to read mail from a dedicated inbox and save the body
of the message to a file. It must be able to read and save any
attachments of the message.
It must be able to send a message from the same dedicated user. It
must be able to resolve recipient addresses prior to sending the
message. (which I think rules out webdav?) It must be able to attach
a small (5K) text file to the message.
It must run on a windows 2003 server which is not the exchange server.
Finally, (phew) it must be a pure .net application. No installing
libraries from other applications.
I have done a lot of reading on cdo, cdosys... smtp, pop3, webdav...
and have probably confused myself enough that I can't see an obvious
answer. I would like to use one technology for the entire project,
but if I have to use more than one, that's ok.
All suggestions welcome.
Mark.
|
|
|
| Back to top |
|
|
Mark M
Guest
|
| Posted:
Tue Dec 14, 2004 4:24 am Post subject:
Re: Correct technology for .net based mail application? |
|
|
Thanks Michael. I'll continue my reading and look into using LDAP in
..Net.
Mark.
On Mon, 13 Dec 2004 17:16:47 +0100, "Michael"
<michael@discussions.microsoft.com> wrote:
| Quote: | WebDAV can be good choice in your case, only question is about resolving
recipient address.
If your recipients are stored in Contacts folder (or some other folder) then
you can resolve recipient address with WebDAV.
If your recipients are stored in GAL then you can't use WebDAV to resolve
recipient address but you can use LDAP (also pure .NET).
Michael
-------------------------------
If you need WebDAV API for Exchange server,
use our component WebDAV .NET for Exchange.
Check out http://www.independentsoft.com
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in