meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ticket_email_parse [2023/10/07 08:05] – add notes on how ticket parsing works wrongechoticket_email_parse [2024/04/01 14:46] (current) – [Email ticketing] bigbug
Line 16: Line 16:
 3. Turn on: Settings > Ticket > Email-to-ticket parsing 3. Turn on: Settings > Ticket > Email-to-ticket parsing
  
-4. Add a cron job to run //cron_ticket_email_parser.php// every minute+4. Add a cron job to run //cron_ticket_email_parser.php// every minute (skip if you set it up [[cron#cron_scripts|earlier]] or installed using the [[installation_script|script]])
  
-5. Ensure that all clients have the correct 'website' configured at Clients > Edit Client //(optional - for auto-contact creation)//+5. Ensure that all clients have the correct 'domains' added in the Domain tracker module //(optional - for auto-contact creation)//
  
 ====== How it works ====== ====== How it works ======
Line 37: Line 37:
 ===== Notes ===== ===== Notes =====
   * Only supports **basic auth**entication. This will not work with Microsoft as they require OAuth.   * Only supports **basic auth**entication. This will not work with Microsoft as they require OAuth.
-  * The IMAP connection uses the same SMTP Username/Password configured for sending emails should be configurable in future 
   * As closed tickets cannot be re-opened, replies to closed tickets raise a notification   * As closed tickets cannot be re-opened, replies to closed tickets raise a notification
-  * Emails from addresses that can't be matched to a client (via the website), contact (via email), or existing ticket (via subject line) are left in the inbox and flagged for review+  * Emails from addresses that can't be matched to a client (via registered domains), contact (via email), or existing ticket (via subject line) are left in the inbox and flagged for review