I am contracting, my employers will want code that they can support (should
I leave), so I don't want to use any 3rd party stuff, unless its something
they decide to buy/use themselves.  I'll do the R&D also an write my own
class too.  I am comfortable with API calls also so I'll probably explore
that area too.  Thanks for the help/info.

Jack


----- Original Message -----
From: "Kim, Cardyin" <CKim@s...>
To: "professional vb" <pro_vb@p...>
Sent: Friday, May 24, 2002 12:58 PM
Subject: [pro_vb] Re: SMTP Server


Jack,

That is correct.  Luckily, there is an OCX that you can use
to do this for you that is completely free.

Here is the website:
http://www.ostrosoft.com/index.html

Personally, I can afford the R&D time and wish to understand
the process better, so I am in the process of writing my own
class to send this email using the VB winsock control.  I have
plans later on to use the Winsock API's or VB.NET system
classes to make the program a little bit faster/smaller.

If you choose to do the same and want to understand SMTP
and such, I recommend that you begin your reading with
RFC 821 to get an idea of how SMTP works and RFC 1521
for the handling of attachments (pay special attention
to the section on Base64 Content-Transfer-Encoding
which you will need to send attachments.

The above documents can be found all over the internet
or at http://www.faqs.org/rfcs/

Hope this helps.

Cardyin

-----------------------------------------
Cardyin Kim
Client/Server and Web Development Analyst
San Antonio Community Hospital
Upland, California
ckim@s...        (xxx) xxx-xxxx
-----------------------------------------


-----Original Message-----
From: Jack Dunstan [mailto:jdunstan7@h...]
Sent: Friday, May 24, 2002 9:37 AM
To: professional vb
Subject: [pro_vb] Re: SMTP Server


Thanks Guys - I appreciate the advice - my employer & user have moved on to
testing of other areas at this point.  I am working on another assignment,
but will investigate/test using a purely winsock/smtp approach as time
allows (and ofcourse when user comes back to this issue).  It seemed like
when I was testing the winsock approach (or maybe it was MAPI) I kept
getting this annoying pop-up from Outlook Express saying something like
"...an application is attempting to send an email.."  But from what you all
have stated, I should be able to put a winsock control on my form, somehow
get the tcp/ip address for the client's Exchange server, set my control to
use that address, configured for tcp/ip (not udp), and a few other things
and send the email without have any user input required - right?

Jack



----- Original Message -----
From: "Kim, Cardyin" <CKim@s...>
To: "professional vb" <pro_vb@p...>
Sent: Friday, May 24, 2002 11:39 AM
Subject: [pro_vb] Re: SMTP Server


I agree with Ajax in his position.  Although a little bit of a
pain during initial development, using winsock to connect to
an SMTP mail server is by far the easiest and most sure fire
way to include email functionality in any program.

By using this method, you do not need to have any
prerequsites installed on the client machine.  Meaning
that, if the client machine can ping the mail server
(connect to it via TCP/IP) then it can send mail.

Using CDO or MAPI, you need to insure that CDO/MAPI objects
are installed on the machine and the local mail client is
configured correctly.  In some types of implementation,
it requires that the user already have their email
client open.

Using a winsock level email allows for you to bypass
all of that hassle, and simply send the mail, whether
or not email is installed or configured correctly.
This is preferred especially when your program is
running on a server.

Cardyin

-----------------------------------------
Cardyin Kim
Client/Server and Web Development Analyst
San Antonio Community Hospital
Upland, California
ckim@s...        (xxx) xxx-xxxx
-----------------------------------------

-----Original Message-----
From: AJAX® [mailto:ajax@i...]
Sent: Thursday, May 23, 2002 9:34 PM
To: professional vb
Subject: [pro_vb] Re: SMTP Server


well jack,

I aint offended at all. So put that aside.

People like to use CDO because its easy 2 use. I do not prefer it because it
has always raised problems for me during deployment.

Also there is a mental block, that discourages people to use win sockets and
protocol level code. I feel that sending (i repeat "SENDING") emails esp
from an application is much better accomplished using winsock + smtp server
rather than any other method. www.vbip.com has some excellents code snippets
for virtually everything u can do using the internet backbone with VB. I
suggest u have a look there.

But ur the guy who is in the real time env, and its ur call.

regards,
ajax®...



to unsubscribe send a blank email to ..