Email Data Connection - Rich text fields (XHTML) not being read by email processing agent - InfoPath Dev
in

InfoPath Dev

Email Data Connection - Rich text fields (XHTML) not being read by email processing agent

Last post 04-17-2008 09:05 AM by Clay Fox. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-17-2008 01:26 AM

    Email Data Connection - Rich text fields (XHTML) not being read by email processing agent

     

    Hi,

     

    We are using InfoPath to generate some formatted mails for one of our applications. Now, these mails work fine when they are received using Outlook by the recipients. However, one of the recipients is a automated email processing agent (not owned by us so I can’t provide much technical details on the agent’s implementation) which receives the mail, extracts the relevant fields and updates a database with those values. Now, when the mail reaches that agent, the RTF items don’t appear. We know this since the agent sends a reply to this mail and we don’t get to see the RTF fields there.

     

    When we did some testing by manually sending RTF (i.e. with formatting/bold etc) to the agent using Outlook, it was able to parse that test properly as plain-text.

     

    We are fine if the RTF comes as formatting-stripped, plain-text format to the agent, but we need to provide these fields to the agent in order to ensure complete integration between systems. We would really appreciate if anyone could provide a direction/approaches to resolve this.

     

    Regards,

    Sayan

     

     

    Filed under: , ,
  • 04-17-2008 09:05 AM In reply to

    Re: Email Data Connection - Rich text fields (XHTML) not being read by email processing agent

    Couple ideas I can think of.

    Can you send the fields on the subject line? Could send a special mail via a second data connection.

    Another idea is use a mail box with forwarding rules to see if a forward will change the properties of the email.

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.