> Ports 25, 443, 993 are needed in order to have a fully functional Own-Mailbox.

Even if you flout your ISP's server policy, there's still DHCP to contend with (changing IPs).

dynamic DNS exists. There's no reason why the host behind a MX entry can't be a dynamically updated address. MX records are names, not addresses.

Reverse DNS is a pretty big issue. You're not going to actually deliver any email without valid reverse DNS.

What is "valid"? I've been delivering personal email for 2 years from an IP whose reverse is like 1-2-3-4-static.hfc.comcastbusiness.net, and that name does not match what I put in my MX or HELO.

Now, granted, there are probably some systems that have issues with this, and maybe I do have failed deliveries I didn't notice, but you did say no email will deliver at all.

The mail systems that I run (at/for an ISP) would block your mail (although I am probably more strict about what I will accept than most).

Valid is generally the one that matches your HELO, and in a perfect world your machine's hostname.

I was under the impression that you just had to have an IP with an A record that matched the reverse DNS, even if it's not for the A record that's your email domain?

It depends on the MX you're delivering mail to. Some aren't restrictive at all, some will reject if there's an A/PTR mismatch, etc. I make use of FCrDNS on my mail systems.

From my initial read, seems like SMTP relay is the way to go with a device like this

It's a full, if small, computer, running Linux on an iMX233. Roughly equivalent to this sort of thing. https://www.olimex.com/Products/OLinuXino/iMX233/iMX233-OLin...

(I had to dig around in the BOM to find out that detail..)