G-Lock Email Processor is the most complete solution for processing incoming e-mails and automating business processes. G-Lock Email Processor provides you with the ability to develop a set of rules that determine how you want to process your incoming messages. It runs as a system service on your PC. The service automatically starts each time you switch your PC on - no need to start the program manually. Using our G-Lock Email Processor you can read messages from POP3 and IMAP mailboxes, filter the messages by different conditions, extract any data from the message body, message header, and text attachments and save the data to a file. Thus, G-Lock Email Processor can handle purchase orders, messages where the text layout is known (web forms), bounced e-mails, subscribe and unsubscribe e-mails, auto replies or any kind of messages of a specific format you may receive.
G-Lock Email Processor can insert extracted data into a local or remote database, update the database or delete records from the database based on the extracted data. The program can work with any ODBC compatible database. Just imagine how much time you would spend for manually extracting the data from the messages and adding it to the database. In G-Lock Email Processor you setup the rule only once determining the criteria to catch the e-mails, fields you want to extract and database to insert the data to. The program will handle the messages according to your settings without your participation - faster, easier and better than you can imagine. In addition, using G-Lock Email Processor you can send a reply to the recipient immediately after the message is processed, or schedule a series of follow-up e-mails to each recipient. And you can send attachments with the messages too - all is completely automatically with G-Lock Email Processor.
What's new in this version:
Version 3.2.7: Added: "Do not backup processed emails" option to Backup/Restore. Added: application/json and application/jsonrequest content type in the HTTP request component. Fixed: issue with the scheduler (checking time). Fixed: issue with multiple form variables in the HTTP Request component.