On 1 Feb 2021, at 14:35, Tim Coote wrote:
Hullo
I’ve been running my email domain using postfix for most, possibly
all of this century. Recently, I’ve had to add in the SPF/DMARC
capabilities, and postsrsd to rewrite the return addresses of
forwarded email. I do have a number of users who forward using the
Unix ~/.forward mechanism. Recently, I noticed some failures like
this in maillog:
“”"
Jan 29 19:18:43 mercury postsrsd[425]: srs_forward: <""> not
rewritten: No at sign in sender address
“””
Upon inspection, comparing fields in emails that are forwarded with
their original forms, it looks to me like the issue is that postsrsd
is being handed “Message-id” fields, rather than “From:”, or
“Reply-To:”, and for these specific emails, there is no
“Message-id:”.
Before I pollute the mailing list with all the gory details. Is this a
known/expected/ever seen behaviour?
SRS rewriting should not operate on ANY header addresses. It is
designed, like SPF, to operate on the SMTP envelope sender.
It is normal for automated messages such as bounces to have a null
envelope sender, so it is possible to pass a null address to postsrsd.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
