469,641 Members | 1,534 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,641 developers. It's quick & easy.

SMTP & Mailer.exe Sample

Has anyone played with MS's SMTP sample, mailer.exe? I downloaded the
sample, and ran it, but keep getting the error "Failure sending mail". Where
might I look for more information? Maybe some troubleshooting tips?

Thanks in advance, you folks have helped with some of my other projects,
simply by answering someone else's question.

Al G
Jan 31 '07 #1
4 2958
"Al G" <ag*******@nospam.charter.netwrote in
news:0P***************@newsfe02.lga:
Has anyone played with MS's SMTP sample, mailer.exe? I downloaded the
sample, and ran it, but keep getting the error "Failure sending mail".
Where might I look for more information? Maybe some troubleshooting
tips?

Thanks in advance, you folks have helped with some of my other
projects, simply by answering someone else's question.
Perhaps using .NET's built in mail classes instead?

Jan 31 '07 #2

"Spam Catcher" <sp**********@rogers.comwrote in message
news:Xn**********************************@127.0.0. 1...
"Al G" <ag*******@nospam.charter.netwrote in
news:0P***************@newsfe02.lga:
>Has anyone played with MS's SMTP sample, mailer.exe? I downloaded the
sample, and ran it, but keep getting the error "Failure sending mail".
Where might I look for more information? Maybe some troubleshooting
tips?

Thanks in advance, you folks have helped with some of my other
projects, simply by answering someone else's question.

Perhaps using .NET's built in mail classes instead?
That's what I was trying to investigate when I found the Mailer sample.
I'm comfortable in VB, but fairly new to dotnet.

I probably should mention that I am using VS2005/SP1, XP, and have
located the IIS and have the default SMTP vitual server. I am on a network
at work, that has internet access through a router.

My goal is a console application triggered by a batch file to send
customer reports as attachments via email. Everything is in place, and is
currently working(sorta) using an off the shelf product called "Windmail".
"Windmail" is unreliable, and produces no meaningful error messages, so I'm
out to replace it.
Al G
Jan 31 '07 #3
"Al G" <ag*******@nospam.charter.netwrote in
news:7x***********@newsfe05.lga:
My goal is a console application triggered by a batch file to send
customer reports as attachments via email. Everything is in place, and
is currently working(sorta) using an off the shelf product called
"Windmail". "Windmail" is unreliable, and produces no meaningful error
messages, so I'm out to replace it.
Take a look at the System.Net.Mail namespace - it's the .NET 2.0 mail
class. .NET's 2.0 mail class has been totally rewritten and is native to
..NET (no external components I believe) so it's quite reliable:

http://www.systemnetmail.com/
Jan 31 '07 #4

"Spam Catcher" <sp**********@rogers.comwrote in message
news:Xn**********************************@127.0.0. 1...
"Al G" <ag*******@nospam.charter.netwrote in
news:7x***********@newsfe05.lga:
> My goal is a console application triggered by a batch file to send
customer reports as attachments via email. Everything is in place, and
is currently working(sorta) using an off the shelf product called
"Windmail". "Windmail" is unreliable, and produces no meaningful error
messages, so I'm out to replace it.

Take a look at the System.Net.Mail namespace - it's the .NET 2.0 mail
class. .NET's 2.0 mail class has been totally rewritten and is native to
.NET (no external components I believe) so it's quite reliable:

http://www.systemnetmail.com/
Cool, that worked. Thanks for your help.

Al G
Jan 31 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

15 posts views Thread by Steven Burn | last post: by
1 post views Thread by michi | last post: by
34 posts views Thread by antonyliu2002 | last post: by
reply views Thread by jlconde | last post: by
5 posts views Thread by Josh | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.