SMTP and IMAP configuration
Two connections cover all email: SMTP to send, IMAP to receive.
SMTP (sending)
Configure under superadmin/company email settings: host, port, encryption, username, password, from-name and from-address. This powers assignment emails, reminders, invoices, signing requests, client alerts and automation emails.
Test with the built-in send-test button after saving. If mail silently fails, check the application log; a wrong port or encryption pairing (465/ssl vs 587/tls) is the usual culprit.
IMAP (receiving)
Configured per company under Ticket Email Settings: host, port, encryption, username, password, enabled flag. One mailbox powers three features:
- Email-to-ticket: unseen mail becomes tickets.
- Email-to-task: plus-addressed mail (
inbox+p42@...) becomes tasks in project 42. - Reply threading: replies carrying a task token thread into that task's comments.
Provider notes
- Gmail and Google Workspace need an app password (or OAuth relay) for IMAP.
- Plus addressing works out of the box on Gmail, Outlook and most hosts; if your provider strips it, create explicit aliases for busy projects.
- Use a dedicated support mailbox; pointing IMAP at a personal inbox will convert personal mail into tickets.