simutek
Tue May 15 02:53:00 CDT 2007
Did you solve your problem?
I have the same issue with e-mails that gets returned with a Delivery Status
Notification. I think this is because of the Bare LF problem.
I have also created a Callout, but it does not seem to work. This is my
callout.config:
<callout.config version="2.0">
<callout entity="email" event="PreCreate">
<subscription assembly="Simutek.Mscrm.Callouts.dll"
class="Simutek.Mscrm.Callouts.Callout">
<prevalue>description</prevalue>
</subscription>
</callout>
<callout entity="email" event="PreUpdate">
<subscription assembly="Simutek.Mscrm.Callouts.dll"
class="Simutek.Mscrm.Callouts.Callout">
<prevalue>description</prevalue>
</subscription>
</callout>
</callout.config>
I believe you must add <prevalue> for Microsoft CRM to pass values to your
callout method. Nevertheless, our callout does not work and we even get this
warning in the event log:
Source: MSCRMCallout
Event ID: 16902
Description: Error: Precallout event cannot have pre-/post-image
subscription. event: preupdate, entity: email
--
Regards,
Michael Bergman
SIMUTEK AB
"dramsden" wrote:
> Hi,
>
> We have an issue where the bulk email or replying to an email using the CRM
> client causes some emails to be rejected by mail servers due to CRM not
> properly terminating strings with a CRLF.
>
> Instead, on occasions, the emails end up having just an LF which some mail
> servers will reject (
http://cr.yp.to/docs/smtplf.html). This does appear to
> be a known issue with CRM 3.0.
>
> I have an EmailCallout DLL that will rewrite messages to replace any bare
> LFs with the correct CRLF. However when I try it I don't see any improvement.
> Below is the callout.config.xml file I have written. Is it correct?
>
> <callout.config version="3.0"
> xmlns="
http://schemas.microsoft.com/crm/2006/callout/">
> <callout entity="email" event="PreCreate">
> <subscription assembly="EmailCallout.dll" class="EmailCallout.ParseText"/>
> </callout>
> </callout.config>
>
> I made sure I ran an "iisreset" after making the changes. No errors are
> logged in Event Viewer.
>
> Can anyone help with this situation?