smtpMail

[=?Utf-8?B?R2VyaGFyZA==?=]

Hi,

For years I have been using a simple method of sending email notifications
from a Windows app for one of my clients using:

System.Web.Mail.SmtpMail.SmtpServer ...
System.Web.Mail.SmtpMail.Send ...

It has been very reliable and stable. However, his provider is now
requiring that it be sent to a specific port, and may also require
authentication.

What is the recommended method for adding in these additional requirements?
I don't see a way to do it with the simple smtpMail.

Thanks.

[Mark Rae [MVP]]

"Gerhard" <Ge*****@community.nospamwrote in message
news:58**********************************@microsof t.com...

However, his provider is now requiring that it be sent to a specific port,

http://www.systemwebmail.com/faq/2.9.aspx

and may also require authentication.

http://www.systemwebmail.com/faq/3.8.aspx

Also, assuming you're using at least .NET 2.0, you should seriously consider
using System.Net.Mail, as System.Web.Mail is now deprecated...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[=?Utf-8?B?R2VyaGFyZA==?=]

Thanks. This should work fine. I'm afraid the main client that needs this
currently is still on .net version 1.1.

"Mark Rae [MVP]" wrote:

"Gerhard" <Ge*****@community.nospamwrote in message
news:58**********************************@microsof t.com...

However, his provider is now requiring that it be sent to a specific port,

http://www.systemwebmail.com/faq/2.9.aspx

and may also require authentication.

http://www.systemwebmail.com/faq/3.8.aspx

Also, assuming you're using at least .NET 2.0, you should seriously consider
using System.Net.Mail, as System.Web.Mail is now deprecated...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Mark Rae [MVP]]

"Gerhard" <Ge*****@community.nospamwrote in message
news:D5**********************************@microsof t.com...

[please don't top-post]

>Also, assuming you're using at least .NET 2.0, you should seriously
consider
using System.Net.Mail, as System.Web.Mail is now deprecated...

Thanks. This should work fine. I'm afraid the main client that needs
this
currently is still on .net version 1.1.

Ouch! Presumably you've informed them that mainstream support for that
version ends next month...?
http://support.microsoft.com/lifecyc...ilter=FilterNO
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Steven Cheng [MSFT]]

Hi Gerhand,

For system web mail and smtp authentication, you can check the following
article also:

#SMTP Authentication using System.Web.Mail (CDOSYS)
http://www.codeproject.com/KB/dotnet...SMTP_AUTH.aspx

As Mark suggested, if possible, it is definitely recommended that we use
the .NET 2.0 System.Net.Mail to substitute the old system.web.mail one.

And just like the "systemwebmail", here is also a FAQ for system.net.mail:

#Frequently Asked Questions for System.Net.Mail
http://www.systemnetmail.com/

Hope this also helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subs...#notifications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>From: =?Utf-8?B?R2VyaGFyZA==?= <Ge*****@community.nospam>
References: <58**********************************@microsoft.co m>

<#3**************@TK2MSFTNGP03.phx.gbl>

>Subject: Re: smtpMail
Date: Mon, 1 Sep 2008 09:40:01 -0700

>
Thanks. This should work fine. I'm afraid the main client that needs

this

>currently is still on .net version 1.1.

"Mark Rae [MVP]" wrote:

>"Gerhard" <Ge*****@community.nospamwrote in message
news:58**********************************@microso ft.com...

However, his provider is now requiring that it be sent to a specific

port,

>>
http://www.systemwebmail.com/faq/2.9.aspx

and may also require authentication.

http://www.systemwebmail.com/faq/3.8.aspx

Also, assuming you're using at least .NET 2.0, you should seriously

consider

>using System.Net.Mail, as System.Web.Mail is now deprecated...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[sloan]

I have a small library that wraps up different smtp configurations nicely.
1.1 code is there as well.
If you put it in, you won't have to worry about changing smtp needs.

http://sholliday.spaces.live.com/blog/cns!A68482B9628A842A!138.entry


"Gerhard" <Ge*****@community.nospamwrote in message
news:58**********************************@microsof t.com...

Hi,

For years I have been using a simple method of sending email notifications
from a Windows app for one of my clients using:

System.Web.Mail.SmtpMail.SmtpServer ...
System.Web.Mail.SmtpMail.Send ...

It has been very reliable and stable. However, his provider is now
requiring that it be sent to a specific port, and may also require
authentication.

What is the recommended method for adding in these additional
requirements?
I don't see a way to do it with the simple smtpMail.

Thanks.