Hello everyone,
If I have been silent lately, it’s because I have been away for 2 weeks at a time during the past three weeks…
To answer @ALT-92’s question
SMTP is designed that way "by design". The IP address of the machine that connects is indicated in the chain of "Received‑by" headers, at the top of the stack at each hop.
If @ALT‑92 even sees his private address 192.168.X.X it’s because his own mail client supplied that information during the HELO phase of the SMTP dialogue (or he has a home mail relay).
Google once decided to change the game by hiding the end‑user’s IP address. This is only possible through a webmail where the first address visible in the SMTP path is that of the webmail server.
And now people want to treat that as a standard. Who makes the rule? Google or the IETF?
In the case of OVH, you need to know that there are specifics at the smtp server ssl0.ovh.net. There is a "home‑grown" proxy mechanism that makes this proxy – not your real IP – appear as the first SMTP hop.
Here is a real, barely anonymized trace:
Received: from 11.mo584.mail-out.ovh.net (11.mo584.mail-out.ovh.net [46.105.34.195])
by [recipient server] (Postfix) with ESMTPS id ED8E7FF695
for <f@d.n>; Tue, 19 May 2026 09:09:15 +0000 (UTC)
Received: from director1.ghost.mail-out.ovh.net (unknown [10.110.0.231])
by mo584.mail-out.ovh.net (Postfix) with ESMTP id 4gKTPk62W8z8HKM
for <f@d.n>; Tue, 19 May 2026 09:09:14 +0000 (UTC)
Received: from ghost-submission-7d8d68f679-nzxnd (unknown [10.110.164.235])
by director1.ghost.mail-out.ovh.net (Postfix) with ESMTPS id B7AA0C14B4
for <f@d.n>; Tue, 19 May 2026 09:09:14 +0000 (UTC)
Received: from XXX1 ([37.59.142.103])
by ghost-submission-7d8d58f679-nzxnd with ESMTPSA
id B/mkH7ooDGq6YgQAuzhN7w
(envelope-from <f@d.n>)
for <f@d.n>; Tue, 19 May 2026 09:09:14 +0000
Authentication-Results:garm.ovh; auth=pass (GARM-103G006ef98eaf1-aa22-45d8-b161-ee6232b78d0a,
1BB0C11CAB58D43B1E5B321705E48F617F7B0D0D) smtp.auth=f@d.n
X-OVh-ClientIp:XXX2
MIME-Version: 1.0
Date: Tue, 19 May 2026 11:09:14 +0200
Comments: XXX1 is the hostname my mail client presented during the HELO phase.
37.59.142.103 is the IP address of the OVH proxy I mentioned earlier.
XXX2 is the IP address of my mail client, which OVH deliberately logged – otherwise the ssl0.ovh.net proxy becomes responsible for anything you might send as illegal mail, scams, etc. I completely understand OVH’s position of not wanting to assume that responsibility.
Conversely, when you receive a phishing email from an address hosted at Gmail, have you ever asked yourself how to trace the scammer if Google does not cooperate?