Transport maps: add a "Local delivery" checkbox

[WordsOfMe]

Summary

Mailcow's transport maps do not provide an intuitive way to get a certain e-mail address delivered locally. As a next hop, neither of "127.0.0.1", "localhost" or "local:" will work. What worked for me is the IP address of the local network interface (in my case: 172.27.x.y). Not rocket science, but not straightforward either.

It would be very convenient to have an additional checkbox "Local delivery" for each rule in the web interface.

Motivation

This would make things more straightforward to configure, and also you could then see at a glance which e-mail addresses are indeed to be delivered locally, without comparing the "next hop" IP to your servers' network interface IPs.

Additional context

No response

[apio-sys]

But by default delivery is done locally unless you set a transport map to deliver to an external server no? That is useful for instance in the case of a server migration towards mailcow. While users still on the old/other server, one would forward them there via individual transport maps pointing to the external IP. And once migrated, one would delete that user's transport map and from there on delivery will be local to mailcow. But maybe I'm missing what you are trying to achieve?

[WordsOfMe]

In my case I run a listserver (mailman) in a separate LXC container, so in the transport map all e-mails to *@lists.example com get the listserver's IP as next hop - so far, so good.

But I have some deleted lists (like e.g., [email protected]) that still get spammed, so I want these addresses to be delivered locally as a spamtrap. I also would like to have [email protected] to be delivered directly to my root mailbox, so I could still get such e-mails if the listserver is stuck.

[apio-sys]

OK I see (I think). But in that case, you could set an alias on [email protected] and set it to learn as spam no?

[WordsOfMe]

...yes, you are absolutely right. I was under the impression that transport maps would be evaluated first, and that such an alias would only work if the e-mail address is also listed in the transport maps for local delivery. But that is indeed not the case. Thank you for pointing this out!