This is the first part of a 2 series tutorial to setup action mailbox with postfix. In this part, we will implement action mailbox with postfix and test in development. If you are only looking to configure postfix in production server to pipe emails, you can read the second part . here Rails 6 released with many awesome features and action mailbox is one of them that has come to make the life easier. : Official Action Mailbox Guide Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Mailgun, Mandrill, Postmark, and SendGrid. You can also handle inbound mails directly via the built-in Exim, Postfix, and Qmail ingresses. So basically, action mailbox can be used to forward all incoming emails to your rails app and process it further as required like storing attachments, creating records from the email body in you db and many more. Skills required to follow the tutorial Intermediate: Rails Linux skills to work with commands in server where your app has been deployed Requirements Setup Action Mailbox with relay option for Postfix Receive incoming emails through relay (Postfix) Pipe Postfix to forward all incoming emails to our shell script Process Email in the mailbox as required Resources Already Available Tutorial to implement and test action mailbox in development. Some questions in Stack Overflow but without required answers for our implementation! Frustrating! You should have Existing app built with rails 6 Steps First of all we will setup action mailbox and test in our local machine. Step 1: Setup action mailbox Install migrations needed for InboundEmail and ensure Active Storage is set up: shell $ rails action_mailbox:install $ rails db:migrate Step 2: Ingress Configuration We will be configuring Postfix among various available options. Tell Action Mailbox to accept emails from an SMTP relay: ruby config.action_mailbox.ingress = # config/environments/production.rb :relay Step 3: Generate Password for authenticating requests Generate a strong password that Action Mailbox can use to authenticate requests to the relay ingress. Use rails credentials: edit to add the password to your application's encrypted credentials under action_mailbox.ingress_password, where Action Mailbox will automatically find it: ruby YOUR_STRONG_PASSWORD action_mailbox: ingress_password: If you are using editor you can edit credentials with following command: nano shell $ EDITOR= rails credentials:edit "nano" Alternatively, you can also provide the password in the environment variable. If you are using gem it is as easy as: RAILS_INBOUND_EMAIL_PASSWORD figaro yml RAILS_INBOUND_EMAIL_PASSWORD: 'YOUR_STRONG_PASSWORD' Step 4: Setup a mailbox Now we should setup a mailbox that will process all incoming emails as we require. Generate new mailbox shell $ bin/rails generate mailbox forwards This will create inside forwards_mailbox app/mailboxes ruby # app/mailboxes/forwards_mailbox.rb < ApplicationMailbox class ForwardsMailbox def process end end Step 5: Whitelist email domains We can configure our to accept all incoming emails to our rails app and forward it to our for further processing. But Action Mailbox also accepts regex to whitelist domains or match certain emails. application_mailbox forwards_mailbox Accept all incoming emails ruby routing => # app/mailboxes/application_mailbox.rb < ActionMailbox::Base class ApplicationMailbox :all :forwards end Accept single email domain ruby routing /.*@email-domain.com/i => # app/mailboxes/application_mailbox.rb < ActionMailbox::Base class ApplicationMailbox :forwards end Accept multiple email domains ruby routing /.*@primary-email-domain.com # app/mailboxes/application_mailbox.rb < ActionMailbox::Base class ApplicationMailbox |.*@secondary-email-domain.com/i => :forwards end This regex matching is telling application mailbox to forward or route all emails coming from to our . For e.g. if we configure it to be and our rails app receives email to , since this email matches with the pattern , it will be forwarded to our where we can further process it. @email-domain.com forwards_mailbox /.*@gmail.com/i john-doe@gmail.com @gmail.com forwards_mailbox Note: Your mailbox name should match the name you've given it in the routing params i.e. will route to . forwards forwards_mailbox Step 6: Test in development For testing in development, Action Mailbox provides UI to test inbound emails in the development environment. To access this, fire up the Rails server first ruby
$ rails s Now go to and click on . http://localhost:3000/rails/conductor/action_mailbox/inbound_emails Deliver new inbound email Fill in all the then click . Ohh wait! before that let's add to our method so we know action mailbox is actually forwarding our emails to the right place. Deliver inbound email byebug process ruby byebug # app/mailboxes/forwards_mailbox.rb < ApplicationMailbox class ForwardsMailbox def process end end You should make sure that email in from input box matches the email domain configured. Now when you click , the execution of the server process should stop at the method since we have a breakpoint at there. This means action mailbox is correctly forwarding incoming emails and our configurations are correct. You can perform further process as required in your app now. Deliver inbound email process That's it, we have now successfully setup action mailbox and tested in development it is working. In the second part, we will configure postfix in production server to pipe emails to our rails app where action mailbox will further process it. You can read it . here If you have any confusions or suggestions, please let me know in comment section below. References Action Mailbox Previously published at https://thedevpost.com/blog/setup-action-mailbox-with-postfix-part-1/

How to Setup Action Mailbox with Postfix [Part 2]

Personal Site

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

How to Setup Action Mailbox with Postfix [Part 1]

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Extracting Information From Hash in Ruby on Rails

10 Cool CI/CD Tools For Your Project

27 Stories To Learn About Ssl

20 Essential Backend Tools For Developers

3 Most Common Ways to Connect your Node and React Applications

Extracting Information From Hash in Ruby on Rails

10 Cool CI/CD Tools For Your Project

27 Stories To Learn About Ssl

20 Essential Backend Tools For Developers

3 Most Common Ways to Connect your Node and React Applications

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps