Open madmuffin1 opened 11 months ago
Are you not able to use something like Postfix to create a configurable catch-all for the rewritten RCPT TO? What mail server are you using? Curious as we would consider supporting this if there's no simple alternative for you.
I gave up running the servers myself and am hosting with a managed service. They won't allow any changes to their default configuration, but the spam filtering really sucks. (If I managed the machine, I would figure out how to fix the spam filter...)
This is primarily a family domain, so it's my dad, my mom, my wife and even my grandma. We live in different states and countries, that's why I do not want to change the IMAP server, as this would cause quite a number of devices needing to be reconfigured. Not much email volume, but lot's of spam coming trough...
(following up on #242, which is closed, but I believe that was a misunderstanding, I believe this is also what #249 is trying to achieve)
Scenario: I run a mail server. For a number of reasons, I need them to keep their setup as closely as it is as possible. But I am very unhappy with the current spam filter - and I was looking to use forwardemail mainly as spam filter. Other use cases - from the other referenced issues: Having a fully setup mail server, that has to move to a different port (since getting an open port 25 is an issue with some providers)
So, let's assume on my server there is a mailbox
foo@bar.com
, and my MX is currently set tomx.bar.com
.If I replace my MX with forwardemails MX, there is no way to have forwardemail direct all mail to mx.bar.com, without the envelope RCPT being rewritten to foo@mx.bar.com - which is not a valid address on that server.
I would suggest allowing something like
mx:mx.bar.com
as value, so forwardemail knows that it should not rewrite the RCPT skip the MX lookup part and forward all traffic to that server.Checklist