E-mail in: requests and replies by e-mail
Artavolo can take mail as well as send it. With e-mail in set up:
- Replies become comments. The e-mails a client portal sends about a request carry a reply address for that request. A client's or a member's reply becomes their comment on it. The quoted earlier message is cut off, and its files are attached.
- A table can take requests. An owner switches on Requests by e-mail in a page's settings. Each new e-mail to the table's address becomes a record: its subject, its text, its sender and its files go into the fields the owner picks. A sender who is a contact of the base's client portal is linked to the record, with their company, and gets its replies by e-mail.
Artavolo runs no mail server of its own. A mail service receives the mail for an inbound domain and posts each message to Artavolo.
Настройте го
You need a domain, or subdomain, used only for this, such as in.yourcompany.com, and an account with a mail service that can receive mail (Mailgun, Brevo, or any service that can post a message as JSON).
- In the mail service, add the inbound domain and set its MX records as the service says.
- On the Artavolo server, set the domain and read the webhook addresses:
`` php utilities/mail-in.php --domain=in.yourcompany.com ``
- In the mail service, send every message for
*@in.yourcompany.comto the address it printed:- Mailgun: Receiving, Create route, expression
match_recipient(".*@in.yourcompany.com"), action Forward to the Mailgun address, and Stop. - Brevo: Inbound parsing, with the Brevo address as the webhook. Brevo keeps attachments behind its own API, so files sent through Brevo are not taken.
- Всичко останало (a Cloudflare Email Worker, a script): post JSON
{"to", "from", "from_name", "subject", "text", "message_id", "auto_submitted", "attachments": [{"name", "content"}]}with each attachment's content in base64.
- Mailgun: Receiving, Create route, expression
Keep the webhook addresses secret: whoever has one can post mail as anyone. php utilities/mail-in.php --domain= switches e-mail in off.
What is kept out
- Each address carries a signature, so nobody can guess another record's or table's address.
- A reply counts only from a member of the base who may comment there, or from a portal client who sees the record. Anyone else's reply is dropped.
- Auto-replies (out of office,
Auto-Submitted) and mail from the inbound domain itself are dropped, so two robots never write to each other forever. - Each message is handled once, by its Message-Id, even when a service posts it twice.
- Files go through the same checks as uploads: the types the site takes, the size limit, and the workspace's storage.
Въпрос, на който тези страници не отговарят?
Пишете ни и ще ви отговорим по имейл, обикновено в рамките на един работен ден.
Свържете се с нас