Arvid Haugen
04-May-2006, 09:08 AM
Hi,
we have an application that send/read e-mail through the ExtendedMAPI
interface.
After we installed Eurekalog the sending of mail stopped working.
The reason is:
We activated "Email send Options" in Eurekalog with "Use Email Client".
When deativating this feature the problem does not occure.
When try to send e-mail we have a code that reads som properties for the
e-mail beeing sendt.
function GetStrProp(inMsg: IRwMapiMessage; inFNamn: String; inDefault:
String = ''): String;
begin
try
result := inMsg.PropByName(inFNamn).AsString;
except
result := inDefault;
end;
end;
As you see this code is based on exception handling.
Everytime an exception is triggered here - even though it is handled - it
causes Eurekalog to open an e-mail with an Eurekalog.
To workaround the problem we included ERwMapiException in the "Exception
generating no error" list.
I would say that since the exception is handled Eurkalog should not trigger
on it.
Best regards,
Arvid Haugen
we have an application that send/read e-mail through the ExtendedMAPI
interface.
After we installed Eurekalog the sending of mail stopped working.
The reason is:
We activated "Email send Options" in Eurekalog with "Use Email Client".
When deativating this feature the problem does not occure.
When try to send e-mail we have a code that reads som properties for the
e-mail beeing sendt.
function GetStrProp(inMsg: IRwMapiMessage; inFNamn: String; inDefault:
String = ''): String;
begin
try
result := inMsg.PropByName(inFNamn).AsString;
except
result := inDefault;
end;
end;
As you see this code is based on exception handling.
Everytime an exception is triggered here - even though it is handled - it
causes Eurekalog to open an e-mail with an Eurekalog.
To workaround the problem we included ERwMapiException in the "Exception
generating no error" list.
I would say that since the exception is handled Eurkalog should not trigger
on it.
Best regards,
Arvid Haugen