Outlook 2007 Mail Send issue

[Guest]

Hello,

We have an Outlook add-in which incorporates a batch send feature. This
feature is designed to send multiple news letters to clients. Since this
would be very slow if we used the Outlook Send feature we incorporated a
third party SMTP ActiveX control which would send the emails out in a
multithreaded environment. This add-in has been in production for almost a
year. Long story short the add-in was due for an update for Outlook 2007 and
as luck would have it the add-in in fact is broken for Outlook 2007.

To the problem …

We are using the _MailItem object to copy, duplicate and store these
messages in a separate folder for a record of the email. The actual send is
accomplished by the third party SMTP ActiveX control - nothing to do with the
MailItem send method. The problem is that the message is processed but never
makes it outside of the PC. We actually see our Symantec Antivirus software
processing the message with that little Outbound envelope that pops up. As I
thought and probably you – I disabled the Antivirus software yesterday and
voila the message was sent successfully. So first thing this morning I got
the folks at Symantec on the phone and told them they had an issue with their
software with Outlook 2007 installed. But much to my chagrin this morning the
symptom changed and I could no longer send a message with the antivirus
software disabled.

So now it appears that Outlook 2007 has some added protection that is
interfering with our email processing. Does anybody have a clue what is going
on? I have contacted the designer of the third party software and Symantec.
They both seem to think that Outlook 2007 is doing some thing to the port to
screw things up. Any help or thoughts would greatly be appreciated.

Thanks,
Tom -

 

[Ken Slovak - [MVP - Outlook]]

Without knowing what the ActiveX control is doing it would be hard to say
what's happening. Any errors in the code, from the control or in the event
logs? I haven't seen any differences in how Outlook 2007 handles sending
emails and I don't see what it could be doing to mess up the control.
Symantec is another story and doing scans on outgoing emails is a known
problem in lots of areas and is generally considered to be worse than the
problem it was meant to solve. Without knowing more I'd still suspect Norton
of being the problem.

 

[Guest]

Hi Ken,

I hate these types of issues when several companies are involved. I can tell
you that the third party control does not generate any errors. We actually
sent the log file to the vendor of the control and he verified that there
were not any errors present. I have disabled the Symantec Antivirus and I
still cannot send the emails through the ActiveX control. In addition
Symantec has also asked me to uninstall their software and do further
verification. I really do suspect Symantec; but it is funny when I disable
their software the problem still exists.

Thanks for your reply!

Tom -

 

[Guest]

Hi Ken,

It is definitely something to do with Outlook 2007. I uninstalled the
antivirus software and created a standalone test application that exercises
the third party ActiveX Control and I can definitely send messages while
Outlook 2007 is running from the test application (different process). Which
leads me to believe that Outlook 2007 is doing something to prevent a message
from being sent from the same process? I have some further testing to do -
but at this time I think it is something to do with Outlook 2007. Again there
are not any problems with Outlook 2003 and below.

Tom -

 

[Ken Slovak - [MVP - Outlook]]

Well, I've seen enough things different/modified/broken in Office 2007 so I
can see that it might be something new there, but without knowing more about
what's happening and how they're trying to do things I can't express any
sort of opinion. I do know that some things that weren't supported but
worked in the past may not work now, but that's what happens when you use
unsupported methods.

About the only thing I can think of that might be helpful is for either the
vendor of the ActiveX control or your company to file a support incident
with MS and let them run with that ball and see what they come up with.