Joe Enos
unread,Jun 13, 2009, 10:02:46 AM6/13/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting
If a particular ISP can't send email to hotmail domains, then that ISP
has some serious problems.
You didn't mention your audience - assuming your audience is normal
people (not internal employees), then in my opinion there's no way you
can expect them to install IIS or SMTP server. We're talking about
opening firewall ports, installing major Windows components, all to do
a basic task like sending email, assuming the user's ISP even allows
them to act as a SMTP server, which some don't.
If you really can't get the standard email stuff working, which
there's no reason you shouldn't be able to as long as the end user can
connect to a SMTP server, then I'd suggest exposing a simple web
service that does the dirty work of sending emails, and have your
application connect to that web service and pass along the appropriate
details. The user would then only need to be able to hit the web,
which they definitely will be able to do with zero configuration.
>
mili...@iprogrammer.com