Routing by sender

[hucknz]

Would you consider adding support for routing by sender rather than recipient?

Your app is great but it works the opposite way to what would be ideal for my use case. In my use case I would like to route to different destinations based on which system sends a message. e.g. Unifi Controller sends from unifi@domain.com and goes to Pushover, UISP sends from uisp@domain.com and goes to Discord.

Today I would have to setup a user on each platform to send the email notifications from, rather than just being able to set the sender address and point the app at Mailrise.

Thanks!

[EINDEX]

I made a tiny change on my fork version, which supports routing by sender & recipient.

The config should be updated to

configs:
  "sender@mail.com":   // sender mail
    "recipient@mail.com": // recipient mail
      urls:
        - pover://USER_KEY@TOKEN

The email routing match logic is the same as the current logic.

[hucknz]

Awesome, thanks @EINDEX. Do you have a prebuilt Docker container available? No worries if not, just checking before I setup a build.

[EINDEX]

Not yet, you can build one. 😄

[ZzenlD]

Hey @EINDEX , could you also make this customized router available as import_code, like described here? That would allow the official Docker image to be used, along with the (improved) router :)

I've been trying to do it myself for a while, but I just can't get it to work. Of course, only if it's not too much trouble for you.

[intweed]

I'm all for it – that feature would be super useful!

[EINDEX]

Hi @ZzenlD and @intweed, Thanks for your interest in this feature.
I am also happy if I am able to use the official image, will do some research on this.

[EINDEX]

In the meantime, consider @YoRyan made an enhancement label to this issue, I am happy to make a PR as well.
Hope is not gonna breaking any existing configuration.

[Taaqif]

Any update on this?

This feature would be amazing

[EINDEX]

sorry, is super busy in the last month and holidays.

[EINDEX]

I made a gist file here, You can using import_code function for it.

https://gist.github.com/EINDEX/964b7e751341e84882ad52f357568a7e

[EINDEX]

Also, for the native support, PR is ready at #157

[ZzenlD]

Heyy thanks a lot for your hard work, thats fantastic.
I have one small suggestion for improvement.

I have some recipients who have a period in their email address, e.g.:

configs:
  "sender@mail.com":   // sender mail
    "foo.bar@mail.com": // recipient mail with a period
      urls:
        - pover://USER_KEY@TOKEN

Mailrise responds with the following error message:
CRITICAL:sent2recv_router.py:Invalid config key 'foo.bar@mail.com'; should be a string or an email address without periods in the username

Could you adjust the router so that it can handle this? I've already tried it myself but unfortunately couldn't get it to work...

And one last quick question: Is there a reason why a separate sender.conf is needed, or can I also specify my mailrise.conf with MAILRISE_SENDER_CONFIG and leave everything in one file?

Thank you very much for everything so far :)

[EINDEX]

Hi @ZzenlD, you welcome.

CRITICAL:sent2recv_router.py:Invalid config key 'foo.bar@mail.com'; should be a string or an email address without periods in the username
Could you adjust the router so that it can handle this? I've already tried it myself but unfortunately couldn't get it to work...

For this one, should be mailrise original logic handle that, I reuse the same logic, could you please try using email with . as sender in mailrise.conf. if that not work you can rise another issue for this.

And one last quick question: Is there a reason why a separate sender.conf is needed, or can I also specify my mailrise.conf with MAILRISE_SENDER_CONFIG and leave everything in one file?

This because the import code limitation, I had try to read mailrise.conf but it will cause the default mailrise simple router failed, and somehow not working. 😢