Basically, if a webmail service doesn't pass along your IP, there would be no way for recipient networks to ever block a flood of unwanted email because they could never blacklist, say, yahoo.com.
I read something about this lately... maybe from Paul Buchheit?
I just picked the two latest I got (and redacted them) as an example.
The first one sent through GMail (SMTP I guess, not webmail) :
Return-Path: <[email protected]>
Received: from [192.168.1.18] (123-123-123-123...bbox.fr. [123.123.123.123])
by mx.google.com with ESMTPSA id ...
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
and another one, through OVH this time : Received: from unknown (HELO ?192.168.0.23?) ([email protected]@123.123.123.123)
by ns0.ovh.net with SMTP;
Both "123.123.123.123" were the public IP address from their DSL connections. In both cases as you can see, I could know both IP addresses.I learned this myself recently from an article here on HN, https://news.ycombinator.com/item?id=2083798
Haven't checked it myself, just reported there by a former gmail engineer in the context of their anti-spammer efforts.
Here's a video with Mike Hearn giving a talk about spam. At the end and middle are mentions about gmail's lack of IP from sent emails, the end specifically from a network admin expressing his grievances about Google's efforts being a hindrance to law enforcement.
https://ripe64.ripe.net/archives/video/25/
It is , however, standard practice for most SMTP providers to do this.
Aha, it was on reddit, and is here: https://moderncrypto.org/mail-archive/messaging/2014/000780....
Ah, and you're right, I misremembered what it said about that, indeed it says gmail does not do that. okay!
Obviously it _could_ if it wanted to, and other webmail might. But gmail does not, okay!
So is the guess here (assuming this is even true) that he had an email server running at home, leaked the ip, and then was attacked when someone found it?