(I would like a solution to this in VB6 as this is what our needy app is
written in, but any solutions that involve .NET would be much appreciated
likewise as I could instantiate them, otherwise please forgive the
crossposting.)
I'm sure I've seen posts here before criticising the practice of automating
outlook for the purpose of programatically sending email, on the grounds that
it's naff. Well now we're really landed in it, it's more than naff. The IT
department have applied some security patch, and it means that a guy in our
department now has to sit there for about 10 minutes constantly clicking
"yes" to the message box that pops up saying "an external program is trying
to use outlook to send email, do you want to allow this?, blah blah blah".
So I desparately NEED to find a way of sending email without using outlook,
and I haven't got the foggiest! I've heard of something called "MIME" - is
this a load of API functions I need to be using?
One other thing - the configuration. It's dead easy to set up outlook in our
network - when loading the profile for the first time, you just tell it the
name of the exchange server to connect to (which we don't have control over)
and it picks it up. Can MIME (if that's the technology I need to be using)
connect to an exchange server?
I'm sure I could understand it once I knew the general structure, so any
links to the basics would be much appreciated, aswell as people's experience
with common pitfalls. No third party controls if possible, as our IT
department have to authorise things like that and they are mightily
suspicious of them.
But it would sure impress people if I could program our way out of this
stupid corner that IT have boxed us into, so any help is much appreciated!
Thanks
Sending and receiving email
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=email&lang=en>
> I've heard of something called "MIME" - is
> this a load of API functions I need to be using?
MIME is used for encoding mail attachments, for example.
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
See inline:
> I've heard of something called "MIME" - is
> this a load of API functions I need to be using?
MIME is short for Multipurpose Internet Mail Extension (I believe). It
is a way of formatting content in messages, it's not a protocol for sending
them.
> One other thing - the configuration. It's dead easy to set up outlook in
> our
> network - when loading the profile for the first time, you just tell it
> the
> name of the exchange server to connect to (which we don't have control
> over)
> and it picks it up. Can MIME (if that's the technology I need to be using)
> connect to an exchange server?
If your exchange server supports the IMAP or POP3 protocols, I would
suggest looking at the Indy Project:
It has a number of classes that you can use to send/receive mail. The
thing is, it won't connect to Exchange directly, so you will have to connect
through the POP3 or IMAP connector.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard.caspershouse.com
Further info can be found at:
http://www.slipstick.com/dev/ol2003problems.htm
http://www.slipstick.com/outlook/esecup/admin.htm
Hope this helps
Jay
"Bonj" <Bo...@discussions.microsoft.com> wrote in message
news:A3146A4F-ECE1-4EC2...@microsoft.com...
I would ask the IT department how to deal with the problem since THEY are
causing it and preventing YOU from doing your job.
Why should you (and your department) have to spent time (and hence money)
because another department is imposing it's own rules.
The IT department is suppose to help its users, not hinder them!!
John..
>
> It has a number of classes that you can use to send/receive mail. The
> thing is, it won't connect to Exchange directly, so you will have to connect
> through the POP3 or IMAP connector.
POP3 and IMAP are protocols for receiving mail,
I don't think they'd be much help with sending.
Bob
--
The box that is a problem is a "feature" Microsoft added to later versions
of Outlook 2000 security patches. This anonying feature was implimented to
prevent script based virii from mass mailing.
While I can say that the box is anonying, I'd much rather deal with it then
leave a system open to virus attacks since it's not properly maintained.
Here is the response I sent to Terry Holland about this very subject earlier
today:
The first option that comes to mind is for you to use CDO to directly access
Outlook and avoid the nice interface you are using. Note that CDO is a pain
to code in. The another option is to use a program called Outlook
Redemption (http://www.dimastr.com/redemption/), using this will allow you
to use the code you have already written with very few changes. I used it a
few years ago and it wasn't too expensive, had a lenient license, and the
creator was very helpful and quick at responding to questions. The final
option is to access the popup box from VB and sendkey commands to it to
automatically close it.
Outlook Redemption is really the best solution in my eyes; however, you
could use SendKeys. It's messing and definately not proper coding in my
eyes, but it will get the job none without a 3rd party program.
Hope this helps
Jay
"Paul Bobrowski" <nos...@msdiscussion.com> wrote in message
news:Ox3%23ARdwE...@TK2MSFTNGP14.phx.gbl...
Thanks for the correction.
--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard.caspershouse.com
"Bob O`Bob" <filt...@yahoogroups.com> wrote in message
news:u5kHUMdw...@TK2MSFTNGP10.phx.gbl...
"Bonj" <Bo...@discussions.microsoft.com> wrote in message
news:A3146A4F-ECE1-4EC2...@microsoft.com...
1. u can use a software called "Express ClickYes" from www.contextmagic.com
, It will bypass those security boxes that pop up in outlook
2. Use vbsendmail.ddl component for sending mails .. it's very simple to use
http://www.freevbcode.com/ShowCode.Asp?ID=109
--
Gaurav Creations
"Nospam" <nos...@please.co.uk> wrote in message
news:418916c6$0$25543$afc3...@news.easynet.co.uk...
>
MAPISession1.NewSession = False
MAPISession1.LogonUI = False
MAPISession1.DownLoadMail = False
MAPISession1.UserName = vbNullString
MAPISession1.SignOn
MAPIMessages1.SessionID = MAPISession1.SessionID
MAPIMessages1.MsgIndex = -1
MAPIMessages1.Compose
MAPIMessages1.RecipDisplayName = eMailAddress$
MAPIMessages1.MsgSubject = "Message From My Program!"
X$ = "Testing, testing, 1 , 2, 3" & vbCrLf
X$ = X$ & "This is line #2" & vbCrLf
X$ = X$ & "Etc." & vbCrLf
MAPIMessages1.MsgNoteText = X$
MAPIMessages1.Send False
DoEvents
MAPISession1.SignOff
I just tried this (using the program I took the code from) and was
surprised to see that the warning you're trying to avoid popped up. I
had never seen this before (its been several years since I used this).
I guess this code won't help you at all.
Sorry.
On Thu, 04 Nov 2004 05:40:59 -0700, Martin <martin...@comcast.net>
wrote:
That's good to know - I'll not go down that road then
I'm really trying to get it to work by using CDO without having IIS
installed on the machine, but it doesn't matter if it does because a lot of
the machines have got IIS installed.
Cheers anyway
I was hesitant to offer a reply as we resolved this problem somewhat
differently. We had a client that was running a suite of applications that
utilized email services. They broke for very much the reasons you listed. We
punted and implemented a COM+ messaging service. Notifications to send an
email were then sent to a central service which had its own email account.
hth
-ralph
They also had a special Queue they could use for Message Queuing
applications (MQ Series, MSMQ)...
Hope this helps
Jay
"Ralph" <msnews.20.nt...@spamgourmet.com> wrote in message
news:efPLcQow...@TK2MSFTNGP10.phx.gbl...