N
Norman Rosenthal
have a SBS2003 Server Small Business Std Edtiion and I am having a problem
with VSAPI. Anyone have any ideas. The issue is that when I enable VSAPI
certain random messages I cannot open unless I disable VSAPI. It happens
with the same messages each time and does not jump around. Here is what
the developer said
Anyone have any ideas
We have tried to reproduce the problem that you have encountered at your
installation; however we did not manage - not even with the email that you
have sent us.
From our log files and tests that we have done on your server, the problem
is surely coming from the VSAPI interface installed in your Exchanges
Server. This is providing the VSAPI application (Mail in this case) with the
message. Therefore, Mail is not getting to scan the message.
This was tested with both MailSecurity and the Microsoft sample VSAPI
module. By disabling the VSAPI application you will be disabling the VSAPI
interface, and therefore you would not have the problem that you have
encountered.
We would recommend that you contact Microsoft in this case. You can keep us
cod in your correspondence with Microsoft so we can provide the technical
details for the problem.
Thank you.
with VSAPI. Anyone have any ideas. The issue is that when I enable VSAPI
certain random messages I cannot open unless I disable VSAPI. It happens
with the same messages each time and does not jump around. Here is what
the developer said
Anyone have any ideas
We have tried to reproduce the problem that you have encountered at your
installation; however we did not manage - not even with the email that you
have sent us.
From our log files and tests that we have done on your server, the problem
is surely coming from the VSAPI interface installed in your Exchanges
Server. This is providing the VSAPI application (Mail in this case) with the
message. Therefore, Mail is not getting to scan the message.
This was tested with both MailSecurity and the Microsoft sample VSAPI
module. By disabling the VSAPI application you will be disabling the VSAPI
interface, and therefore you would not have the problem that you have
encountered.
We would recommend that you contact Microsoft in this case. You can keep us
cod in your correspondence with Microsoft so we can provide the technical
details for the problem.
Thank you.