Configure Conversation Continuity with Email
SMTP_AUTHENTICATION
, SMTP_USERNAME
and SMTP_PASSWORD
are present in your .env file. To disable this behaviour either comment out or delete these lines from your configuration. This will allow you to send outbound messages from the same server without a premium service. Please note many ISP’s do not allow email servers to be run from their networks. It is your responsibility to ensure adequate access control preventing yourself becoming an open relay and ensuring your server is able to get past your recipients spam filters for example SPF, DKIM & DMARC dns records.
This configures the ingress service for the app. Now we have to set the password for the ingress service that we use.
https://example.com/rails/action_mailbox/mailgun/inbound_emails/mime
if example.com
is where you have hosted the application.
your-domain.com
pointed towards Sendgrid
Configure SendGrid Inbound Parse to forward inbound emails to forward your inbound emails to /rails/action_mailbox/sendgrid/inbound_emails
with the username actionmailbox
and the password you previously generated. If the deployed application was hosted at example.com
, you can configure the following URL as the forward route.
https://example.com/rails/action_mailbox/mandrill/inbound_emails
if example.com
is where you have hosted the application.
If you want to know more about configuring other services visit Action Mailbox Basics
bin/rails
. For example
my_incoming_message
into a Chatwoot instance running on localhost
- assuming my_incoming_message
contains an RFC 822 compliant message.
The ingress tasks provided by Action Mailbox are a thin layer around an HTTP endpoint exposed by Action Mailbox. An alternative to using those tasks is to talk to the http endpoint directly. The following script achieves the same.
/home/chatwoot/bin/import_mail_to_chatwoot
, a configuration for doing so from an IMAP inbox is as follows.
getmail
regularly, for example using a cron job. For IMAP
you can also run it constantly using getmail --idle INBOX
, though that will need some care to deal with interrupted connections, etc.
your-domain.com
, where your-domain.com
is the domain for which you set up MX records in the previous step.
replyto:
in the following format reply+<random-hex>@<your-domain.com>
and reply to those would get appended to your conversation.