From: Michel Posseth [MCP] on

Well the program i wrote was installed from a cd-rom ( DVD in a later
stage ) and had to function "out of the box"
and i bet not a lot of people ( end consumers ) know there e-mail settings
so i guess the same aplies as of today

Also you forget about the Lotus Domino situation or if there is a Outlook
server installed on a company network
( for a fact i never got Lotus to work )

So in these sitautions my solution was / is just fool proof and verry
simple to implement

>smtp is a very simple protocol.

For VB6 i used the VBSendmail.dll and in .Net you can just use the builtin
framework classes however they are perfect in a "simple" situation
even on a MS Exchange network it will not work if SMTP is closed on the mail
server ( this is default on Exchange ) , for a fact in the company i
currently work for we have a Linux mail server especially for our .Net apps
as the admins want to keep the "recomended" settings on the Exchange server
..


regards

Michel




"Tom Shelton" <tom_shelton(a)comcastXXXXXXX.net> schreef in bericht
news:%23MfI%23vj5KHA.5464(a)TK2MSFTNGP05.phx.gbl...
> On 2010-04-27, Michel Posseth [MCP] <msdn(a)posseth.com> wrote:
>>
>> I once wrote a VB6 catalogue program that had the ability to place orders
>> that had to be send to a e-mail adress of a reseller
>> after strugling with lots of methods ( registry etc etc ) to get the
>> local
>> SMTP server and at one point running into a big problem where the users
>> had
>> a Lotus Domino system i found out that it was much easier to send a form
>> posting over HTTP to a server that i controled and generate the e-mail
>> from
>> there
>> to be send to the order department of the company where i wrote the
>> program
>> for .
>>
>> I then only needed the local email adress so the order department could
>> optionally reply to the placed order
>>
>> Hope this helps
>>
>> Michel
>>
>
> I could see that in the old days - but, really how many companies don't
> have
> email now a days? Even a small company is going to have an email
> account -
> all you need to know is the server address and the login info to send an
> email. smtp is a very simple protocol.
>
> --
> Tom Shelton

From: Tom Shelton on
On 2010-04-27, Michel Posseth [MCP] <msdn(a)posseth.com> wrote:
>
> Well the program i wrote was installed from a cd-rom ( DVD in a later
> stage ) and had to function "out of the box"
> and i bet not a lot of people ( end consumers ) know there e-mail settings
> so i guess the same aplies as of today
>

And yet, they manage to get their outlook working... I'm willing to bet that
the guy that installs the software also knows the corporate email settings.
But, you know your users. Your way probably was best for your situation.

> Also you forget about the Lotus Domino situation or if there is a Outlook
> server installed on a company network
> ( for a fact i never got Lotus to work )
>
> So in these sitautions my solution was / is just fool proof and verry
> simple to implement
>
>>smtp is a very simple protocol.
>
> For VB6 i used the VBSendmail.dll and in .Net you can just use the builtin
> framework classes however they are perfect in a "simple" situation
> even on a MS Exchange network it will not work if SMTP is closed on the mail
> server ( this is default on Exchange ) , for a fact in the company i
> currently work for we have a Linux mail server especially for our .Net apps
> as the admins want to keep the "recomended" settings on the Exchange server
> .
>

Hmmm... That's interesting. Not having ever done anything with Exchange
admin, I know nothing about setting it up or configuring it. Or what is
recommended best practice or not. But, I know on every corporate exchange
network I have been on, I have no problems sending emails using the smtp
classes in .NET as long as I set the authentication properly...

--
Tom Shelton
From: Helmut Meukel on
>> For VB6 i used the VBSendmail.dll and in .Net you can just use the builtin
>> framework classes however they are perfect in a "simple" situation
>> even on a MS Exchange network it will not work if SMTP is closed on the mail
>> server ( this is default on Exchange ) , for a fact in the company i
>> currently work for we have a Linux mail server especially for our .Net apps
>> as the admins want to keep the "recomended" settings on the Exchange server
>> .
>>
>
> Hmmm... That's interesting. Not having ever done anything with Exchange
> admin, I know nothing about setting it up or configuring it. Or what is
> recommended best practice or not. But, I know on every corporate exchange
> network I have been on, I have no problems sending emails using the smtp
> classes in .NET as long as I set the authentication properly...
>


I gave up trying to understand what happens in the heads of IT admins.
Just yesterday I sent an update of my app to my customer - appended to an
email. This time I sent it to his private email address, not his company email
account.
Last time I had to send it twice, the exe was stripped from my email and after
hours trying to get it released from the IT he phoned me to send it to his
private
email account. There he _could_ download the exe to his company PC!
Funny how they have secured their company net, isn't it?

Helmut.

From: Bwig Zomberi on
Possibly. But most people develop scripts on an ordinary desktop and
upload to a shared hosting server. Most hosting providers configure an
SMTP server on the same web server so that script writers do not have to
explicitly specify an IP address.



Cor Ligthert[MVP] wrote:
> Bwig,
>
> Not on all OS versions
>
> "Bwig Zomberi" <zomberiMAPSONNOSPAM(a)gmail.com> wrote in message
> news:hr5ogn$1h6$1(a)speranza.aioe.org...
>> fniles wrote:
>>> Is there any way to send an email (either from a VB program or ASP or
>>> HTML)
>>> if the machine has no Outlook and/or SMTP server ?
>>> Thank you
>>>
>>>
>>
>> If it is your local computer, then installing IIS will provide a local
>> SMTP server. If you hosting on a shared server, the hosting provider
>> would have already configured an SMTP server. In most cases, you
>> wouldn't have to specify an SMTP server address. You just need to
>> simply set the from and to addresses and call send.
>>
>> --
>> Bwig Zomberi
>


--
Bwig Zomberi
From: Cor Ligthert[MVP] on
Helmut,

Default behaviour, exe's don't go trhough almost through not any mailserver
anymore.

The admins don't do that, they simply install the latest updates.

They have to do something extra to remove that, and who will do that as that
can be a reason for a complete company going down, they will be direct
fired, whatever they complain and right they have.

Cor

"Helmut Meukel" <NoSpam(a)NoProvider.de> wrote in message
news:excTnIl5KHA.1932(a)TK2MSFTNGP05.phx.gbl...
>>> For VB6 i used the VBSendmail.dll and in .Net you can just use the
>>> builtin
>>> framework classes however they are perfect in a "simple" situation
>>> even on a MS Exchange network it will not work if SMTP is closed on the
>>> mail
>>> server ( this is default on Exchange ) , for a fact in the company i
>>> currently work for we have a Linux mail server especially for our .Net
>>> apps
>>> as the admins want to keep the "recomended" settings on the Exchange
>>> server
>>> .
>>>
>>
>> Hmmm... That's interesting. Not having ever done anything with Exchange
>> admin, I know nothing about setting it up or configuring it. Or what is
>> recommended best practice or not. But, I know on every corporate
>> exchange
>> network I have been on, I have no problems sending emails using the smtp
>> classes in .NET as long as I set the authentication properly...
>>
>
>
> I gave up trying to understand what happens in the heads of IT admins.
> Just yesterday I sent an update of my app to my customer - appended to an
> email. This time I sent it to his private email address, not his company
> email
> account.
> Last time I had to send it twice, the exe was stripped from my email and
> after
> hours trying to get it released from the IT he phoned me to send it to his
> private
> email account. There he _could_ download the exe to his company PC!
> Funny how they have secured their company net, isn't it?
>
> Helmut.
>