Thanks,
Maybe I need to clarify a few things. My email server is not in my home
network. My raspberry is, and it gets random IPs as sometimes it has to
go through a VPN to the internet.
Mail to my own domains is not permitted by default. This email from
raspberry is sent to my own domain (the one I'm using on this list) and
it fails the sender address domain not found and FQDN tests.
There is no relaying needed.
thanks
Dave
On 31/08/2020 00:05, Viktor Dukhovni wrote:
On Sun, Aug 30, 2020 at 11:54:19PM +0100, dave wrote:
That would be great if it works.
You mean that would be a double-barrelled shotgun you aim at your feet,
sure...
It may be easy to forge, but it can be harder to guess depending on what
name I choose?
But you both mention relay - is that in the loose sense of the word? I
don't need to relay it do I? Just permit?
Mail to your own domains is permitted by default. You don't need to
"permit" specific sender domains. It is sending to other people's
domains (relaying) that requires access control. The rest of the
access policy is then about blocking inbound spam and the like.
Now you for some reason report that your Raspberry Pi client is
not a stable client IP on your network. If you take it with
you on the road, you'll need either a VPN back to an internal
network, a client cert or SASL auth.
