On Mon 03/Feb/2025 14:41:21 +0100 Todd Herr wrote:
On Sat, Feb 1, 2025 at 2:03 PM Alessandro Vesely <[email protected]> wrote:
On Sat 01/Feb/2025 00:31:02 +0100 Todd Herr wrote:
On Fri, Jan 31, 2025 at 5:01 PM Damian Lukowski
<[email protected]> wrote:
In practice, how common are messages with no domain in the From
header? I don't recall seeing any and I would expect that if there
are any, they're all spam that would get filtered for other
reasons.>>>>>> After seeing [1], I tried to find out whether DMARCbis had something else
to say about such case.
[1] https://github.com/msimerson/mail-dmarc/pull/255
Where in the DNS would one find a DMARC policy record named
"_dmarc.localhost"?
On your server you can define whatever you like. I have "localhost" in
named.conf.default-zones, from Debian defaults IIRC. Could add _dmarc as
well...
And why would one bother to do that?
For testing?
DMARC is for attempting to determine if a third-party Domain Owner has
authorized the use of its domain in the RFC5322.From header in mail that is
inbound to me.
Either you experiment with localhost actually pointing remotely, or
authenticated messages have to actually originate locally. SPF must authorize
127.0.0.1 and DKIM keys must be found locally.
However, my server refuses to relay messages From: vesely@localhost, even if
addressed to me. It claims "syntax error" (maybe the one-label domain rule?)
Mail inbound to my mail server that has an RFC5322.From domain that is
either "localhost" or "localhost.localdomain" and is from an external
source is clearly mail from an at-best misconfigured or unconfigured mail
server, and should be rejected out of hand simply because of that fact;
I don't think I have a filter against that.
DMARC has no role to play here.
Agreed.
Best
Ale
--
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]
