Yeah.
This. The doctrine seems to be that they're sufficiently on the ball that they can handle all abuse issues internally, and thus, they hide that information, since it could be used to, for instance, launch a DDOS attach against the user's "Home" IP infrastructure. They might have a point, but given the ease at which people can sign up for a new (and abusive) account these days, I tend to give it serious side-eye. There’s also the ease at which some miscreants can abuse just about any service on day 0. ☹ Aloha, Michael. -- Michael J Wise Microsoft Corporation| Spam Analysis "Your Spam Specimen Has Been Processed." Got the Junk Mail Reporting Tool<http://www.microsoft.com/en-us/download/details.aspx?id=18275> ? -----Original Message----- From: mailop <mailop-boun...@mailop.org> On Behalf Of Grant Taylor via mailop Sent: Thursday, July 18, 2019 9:34 AM To: mailop@mailop.org Subject: Re: [mailop] How to identify source of email sent via Google? On 7/18/19 4:08 AM, Benoit Panizzon via mailop wrote: > Hi List Hi, > Unfortunately with emails sent over Gmail, there are no more IP source > before the Google IP Address, so I started wondering if there is any > other way to find an unique source in the Gmail Headers: I will be quite surprised if there is any information leak that provides what you want. Google tends to go out of their way to hide what you're asking for. There's also a real chance that there is no information for what you want. I.e. someone composed the message in the web interface or something else that submitted the email to Google via something other than SMTP. Google's SMTP servers would be the first SMTP servers in the message chain. Good luck. I would not hold my breath. -- Grant. . . . unix || die
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
