- Email DIY
One of the features that gets the most love from our customers are Routes. Routes let you accept, parse and POST or forward your incoming emails. We’ve done some work lately to make Routes even more useful by adding the ability to test your webhook endpoints when you want to POST your incoming emails to your app. None of this matters though if you are not able to effectively accept the incoming emails. Today, we’ll walk you through some examples of the most common ways to group incoming emails for processing. These methods use Regular Expressions which are extremely powerful, but can also be tricky to work with sometimes. Hence today’s post. Hope you enjoy it!
The Regular Expression notation for Routes is based on the Python spec and there is an excellent review of Regular Expressions over at python.org. We’re not going to go into all the details, but we do want to point out one error that developers who are new to regular expressions often make:
The asterisk “*” itself is not a wildcard in regular expression syntax.
To match any character, you need to use a period “.”
To match any series of characters, you’d use a period followed by an asterisk “.*”
Here are some of the most common regular expressions that we see customers using when receiving messages. This list only scratches the surface of what you can do, but hopefully it will get you thinking about the power of regular expressions.
To make things easier, we’ve grouped the expressions into 3 groups
Explanation- we are looking for a specific recipient for any domains currently loaded in the Mailgun “Domains” tab. Keep in mind, you must have your MX records pointed to Mailgun before Mailgun will accept messages for that domain.
Explanation- Mailgun configures our inbound mail server to accept recipients with plus addressing. You could also limit the plus addresses by using the syntax from the below example.
Explanation- we’ve used regular expressions to define a set of recipients that are valid for a specific domain.
Explanation- we’ve created a “catch all” for a specific domain. Don’t get confused with the global catch all that Mailgun Routes provides where all emails received are forwarded.
match_recipient('(?P<user>.*?)@example.com') -> forward('g<user>@externaldomain.com')
Explanation- we want Mailgun to receive and forward the incoming message to an external domain, but retain the user to user mapping. To do this, we use a named capture. The named capture will remember the “user” and use it in the forward action.
Explanation- we want the route to trigger for any email that is from “firstname.lastname@example.org”. Notice we add the wildcards before and after the email address. This is because a “From” field can contain several other attributes. For example, the sender’s name. “Mailgun Bob <email@example.com>”
Explanation- we are looking for any messages with a subject that contains “urgent” OR “help” OR “asap”. We add wildcards on both the beginning and end. This example would trigger on a subject like this: “My request is urgent!”.
match_header('X-Mailgun-Sflag', 'Yes') -> forward('firstname.lastname@example.org')
Explanation- Mailgun provides spam filtering for inbound messages. When we determine a message is spam, we inject a special header. You can use Routes to filter messages based on these headers. In this case, we are forwarding the message to an external mailbox, so we can review it later.
Explanation- we’ve created a “catch all” for a specific domain, but we only route messages when it’s a reply to our original thread. You could also use “Fw” to represent a forwarded message.
Explanation- we’ve created a “catch all” for a specific domain, but we only route messages when the content language is in English. For other languages, check out the ISO specification for content languages, https://en.wikipedia.org/wiki/ListofISO639-1codes.
We hope these examples will help you write more effective regular expressions for filtering your incoming emails. Something else you’d like to know how to write? Let us know in the comments and we’ll see if we can come up with an example.
Last updated on August 28, 2019