bug-mailfromd
Re: [Bug-mailfromd] removing headers (client ip)
> > It only removes the information of the current server, so the previous
> > 'hops' are still there. :/
>
> Right, but you insert 'Received: internal info suppressed', which is
> plain wrong. The format of a Received header is descibed strictly
> enough in RFC 5321, section 4.4, and 'internal info suppressed' is
> far from matching that definition. Sure enough, one can insert into
> message header whatever he wants, even a couple hundred lines from
> 'Alice in Wonderland' in a pinch. That doesn't mean, however, that mail
> transport systems on the route will be able to digest the inserted
> stuff. What's worst, you can never be sure what a mail transport system
> would do if it is unable to make sense of your headers: pass the message
> on or just drop it.
Reading about this yesterday I have come to understand that it is quite a sensitive topic. However many of these RFC's have been written before the GDPR. Currently the legislation is like this that "the IP address could be considered as personal data, as in any case it allows or helps the direct or indirect identification of an individual." Proton and gmail emails are completely removing the previous and own Received headers.
So I am a bit in doubt what to do. The 'internal info suppressed' was just for testing to see what would change. Currently I am running with with
$?sfrom xxxxxxx (x.x.x.x) $.by $j $?r with $r$. id $i$?u for $u; $|;
Because it could be good to have 'proof' that a log entry is related to the message via the id. I wonder where proton and gmail are doing this, i guess in the dkim.