On 09/28/2017 04:38 PM, Luke Martinez via mailop wrote:
I'm a little confused as to what is going on here.
This is probably one of the weirder message traces I've seen.
The message gets delivered to a tagged gmail address, and then it somehow ends up getting forwarded from a hetzner IP (2a01:4f8:151:4061:ed1d:9de7:f8b0:95c8) using a bogus Return-Path (7eb.ckc) to some other gmail address (strredw...@gmail.com <mailto:strredw...@gmail.com>).
I replied directly with more details.TL;DR: It looks like something running on tocs-devices.loveatomic.com (2a01:4f8:151:4061:ed1d:9de7:f8b0:95c8) received the message from the original Gmail mailbox, med.abattouy+f...@gmail.com, and then forwarded the message to the second Gmail mailbox, strredw...@gmail.com.
Maybe its late and I'm missing something, but I can't put together a reasonable story from this header. Would appreciate any insights.
The biggest clue for me was the gap in time stamps, as if something was periodically polling the original Gmail mailbox.
Received: from tocs-devices.loveatomic.com (tocs-devices.loveatomic.com.
[2a01:4f8:151:4061:ed1d:9de7:f8b0:95c8])
by mx.google.com with ESMTP id 68si2589689wmh.87.2017.09.16.05.09.30
for <strredw...@gmail.com>;
Sat, 16 Sep 2017 05:09:30 -0700 (PDT)
I'd be curious to know what you find out. -- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
