Jose, I typically create a display only form to handle inbound email. Keeping minimal customization on the OOB forms. Just a push field filter from AR System Email Messages. You can then use the custom form to pull data, parse, configure, and push anything where you need it to go without any OOB customization.
Jason On Apr 16, 2012, at 7:07 AM, Jose Huerta <[email protected]> wrote: > ** > Hi all, > > I want to receive email from users, perform complex evaluations on it, and > act accordingly. > > For instance, If a pattern like INC____________ is found, then look for the > incident, add the content of the email as a work info, where the sender must > be the user corresponding to the sender address, and generate a response > email. If not, send an error mail. > > Well, My idea is to config an email inbox without parsing and create filters > on AR System Email Messages form. Don't know if it's the better approach. > Comments or suggestions? > > Parsing engine at the email engine seems to be insufficient, because users > can use a lot of formats. > > Thanks, > > Jose Huerta > http://theremedyforit.com/ > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
