Most of the users servers I'm referring to are on the other side of our mail gateway, so we know where they are sending from (through our gateway) but when the client's domain is used on an inbound message, we would be able to simply reject, knowing it's not the users servers sending it.
I agree don't re-invent, but some clients have many providers that send email on their behalf making it more complicated. On Fri, Jul 22, 2022 at 10:08 AM Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 21.07.22 um 22:58 schrieb Joey J: > > Hello, > > > > Is there a way for me to block mail that claims its from a certain > > domain, based on my own valid ip address list? > > > > Example: > > > > myserver.com - IP address 1.2.3.4 > > If a messages comes in from any server other than 1.2.3.4 for domain > > myserver.com reject it? > > SPF > > > I know SPF/DKIM/DMARC would also help here, but trying to almost make my > > own ACL > > why reinvent the wheel? > > such lists go outdated over time and are only asking for touble > -- Thanks! Joey
