On 2025-03-28 at 14:59:36 UTC-0400 (Fri, 28 Mar 2025 19:59:36 +0100)
Marco Moock via mailop <m...@dorfdsl.de>
is rumored to have said:

Am Fri, 28 Mar 2025 12:38:02 -0400
schrieb Bill Cole via mailop <mailop@mailop.org>:

On 2025-03-28 at 11:32:50 UTC-0400 (Fri, 28 Mar 2025 16:32:50 +0100)
Marco Moock via mailop <m...@dorfdsl.de>
is rumored to have said:

Hello!

When trying to deliver DMARC reports to <dm...@u64.de>, I get

   ----- The following addresses had permanent fatal errors -----
<dm...@u64.de>
    (reason: 550 This address does not send an unsigned return
path.)

What does this message mean?

SMTP MAIL FROM is from=<postmas...@dorfdsl.de
Return-Path: <postmas...@dorfdsl.de>

FWIW, those two are usually tightly bound: the Return-Path header
does not normally exist until it gets created when the message is
delivered *out* of SMTP (e.g. to a mailbox.) What can be be varied is
the "From:" *header* address.

The message is a DMARC report generated by opendmarc on my machine
(srv1.dorfdsl.de)

Most likely they have implemented BATV to reject bogus bounces. BATV
assures that all mail with a "From" header of postmas...@dorfdsl.de
will have a SMTP sender address with a keyed modification of the
"real" address.

This is rather confusing for me. I don't use BATV at all - neither I
use such addresses nor do I validate that in any way.

And I put the wrong address in my description. I should have said <dm...@u64.de>, the address you are trying to send to. *THAT* address appears to have BATV (or something similar) enabled.

Obviously this is wrong to do with a DMARC reporting address. Also, BATV is only supposed to apply to bounces that offered with a null envelope sender address. So unless you're mistaken about the original message's sender address (i.e. it is really '<>'when talking to the MX for u64.de) the problem is the recipient's configuration.


--
 Bill Cole
 b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
 Not Currently Available For Hire
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Reply via email to