Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular expressions in the routing address #480

Closed
sperlic opened this issue Feb 1, 2018 · 2 comments
Closed

Regular expressions in the routing address #480

sperlic opened this issue Feb 1, 2018 · 2 comments
Labels

Comments

@sperlic
Copy link

@sperlic sperlic commented Feb 1, 2018

Hi guys,

We have a situation where domen.tld is used for regular email messages and for transaction messages across the route notifications-{INSTANCE_ID}@domain.tld[1]. Is it possible to use a regular expression in the ruting address to route only the addresses that contain notifications -.*@domain.tld? Wildcard address *@domain.tld makes us a redirection loop when the transaction message is sent to regular user user@domain.tld back through the Postal.

[1] The server that performs the separation and routing (via Postfix) for the domain.tld is located on another machine in relation to Postal which currently has a wildcard route.

Let me know if you need more informations about this scenario.

Thank you for the great product!

@willpower232

This comment has been minimized.

Copy link
Collaborator

@willpower232 willpower232 commented Feb 3, 2018

I don't believe such a thing is currently possible, there is only the wildcard redirect *@domain.tld.

We don't really use routes so not sure exactly what changes are needed but I don't believe it would be complicated to add.

If you add that feature yourself, do send a pull request.

@Csardelacal

This comment has been minimized.

Copy link

@Csardelacal Csardelacal commented Jan 24, 2020

I know this is a bit older thread.

But I found out that this is actually possible in vanilla Postal and made a blog post about it)

You may not be able to use notifications-*@domain but you can create a route for notifications@domain and then send emails to notifications+id@domain and it will work just fine.

Postal respects the fact that the + symbol in email addresses is akin to the # character for URL fragments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.