Quando l’MX è indeciso…

Quando l’MX è indeciso…

Ho un piccolo hosting su AwardSpace, comprato più per provare il servizio che per altro. Oggi così per curiosità ho dato un occhio agli headers di una mail in entrata. Sono rimasto O_O (è difficile descrivere a parole).

Return-Path: <donotreply@akismet.com>
X-Original-To: giorgio@FAKEDOMAIN.COM
received: from mx2.runhosting.com (mx2.runhosting.com [82.197.130.202])by mbox2.runhosting.com (Postfix) with ESMTP id 4B1F3607F34Efor <giorgio@FAKEDOMAIN.COM>; Sat, 22 Jan 2011 16:03:26 +0000 (UTC)
received: from mx2.runhosting.com (in2.defender.mail [82.197.130.203])by mx2.runhosting.com (Postfix) with ESMTP id B26D850600for <giorgio@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:07:07 +0000 (UTC)
received: by mx2.runhosting.com (Postfix, from userid 65534)id A426C50615; Sun, 23 Jan 2011 00:07:07 +0000 (UTC)
received: from mail2.runhosting.com (mail2.runhosting.com [82.197.130.204])by mx2.runhosting.com (Postfix) with ESMTP id 6390C50600for <giorgio@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:07:06 +0000 (UTC)
received: from mail2.runhosting.com (unknown [82.197.130.206])by mail2.runhosting.com (Postfix) with ESMTP id 965413EADCfor <giorgio@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:07:06 +0000 (UTC)
received: by mail2.runhosting.com (Postfix, from userid 65534)id 7D3163F708; Sun, 23 Jan 2011 00:07:06 +0000 (UTC)
received: from mbox2.runhosting.com (mbox2.runhosting.com [82.197.130.207])(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))(No client certificate requested)by mail2.runhosting.com (Postfix) with ESMTPS id 088E63EADCfor <giorgio@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:07:05 +0000 (UTC)
received: from mx2.runhosting.com (mx2.runhosting.com [82.197.130.202])by mbox2.runhosting.com (Postfix) with ESMTP id 8F221607F34Efor <admin@FAKEDOMAIN.COM>; Sat, 22 Jan 2011 16:02:54 +0000 (UTC)
received: from mx2.runhosting.com (in2.defender.mail [82.197.130.203])by mx2.runhosting.com (Postfix) with ESMTP id 14FC850600for <admin@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:06:36 +0000 (UTC)
received: by mx2.runhosting.com (Postfix, from userid 65534)id F17CC50615; Sun, 23 Jan 2011 00:06:35 +0000 (UTC)
received: from smtp1.sat.wordpress.com (smtp1.sat.wordpress.com [76.74.254.15])by mx2.runhosting.com (Postfix) with ESMTP id 192E950600for <admin@FAKEDOMAIN.COM>; Sun, 23 Jan 2011 00:06:33 +0000 (UTC)
received: from smtp1.sat.wordpress.com (localhost.localdomain [127.0.0.1])by smtp1.sat.wordpress.com (Postfix) with ESMTP id 02EC4241C198for <admin@FAKEDOMAIN.COM>; Sat, 22 Jan 2011 16:02:57 +0000 (UTC)
received: from _ (c6.sat.akismet.com [66.135.58.48])by smtp1.sat.wordpress.com (Postfix) with ESMTP id E7883241C18Afor <admin@FAKEDOMAIN.COM>; Sat, 22 Jan 2011 16:02:56 +0000 (UTC)
X-Spam-Score: -2.0
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on in2.defender.mail
X-Spam-Level:
X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL autolearn=disabledversion=3.2.5
Dkim-Signature: v=1; a=rsa-sha1; c=relaxed; d=akismet.com; h=date:to:from:subject:message-id:reply-to:mime-version:content-transfer-encoding:content-type; s=my3; bh=CC4iVqFNhHYEprW6wy8MS/KCPqo=; b=l28OC3lmyUmdoLIK+8ts7rfM9RV81WUySnA3O6aDa55rCS00aSTV8Cp70ziz0e6mrbOuoRwPPanQC77Xm/agtA==
Domainkey-Signature: a=rsa-sha1; c=nofws; d=akismet.com; h=date:to:from:subject:message-id:reply-to:mime-version:content-transfer-encoding:content-type; q=dns; s=my3; b=weli02Y9jlA0+tE5g8DpzJAwO+PFYAPGqC4iAOw7AYXthPs3m2Rx//oJ2iN2kkL6/Ixa1Ba9raPhtNxoNlqYtg==
Date: Sat, 22 Jan 2011 16:02:56 +0000
To: admin@FAKEDOMAIN.COM
From: Akismet Support <support@akismet.com>
Subject: Your new Akismet API key
Message-Id: <2c88cc629485167f7c160c4737027367@_>
X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.4]
Reply-To: support@akismet.com
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=”UTF-8″
x-virus-scanned: ClamAV using ClamSMTP (in2.defender.mail(82.197.130.203), client: 82.197.130.202)
x-virus-scanned: ClamAV using ClamSMTP (out2.defender.mail(82.197.130.206), client: 82.197.130.204)
x-virus-scanned: ClamAV using ClamSMTP (in2.defender.mail(82.197.130.203), client: 82.197.130.202)

E’ spaventoso. C’è un forwarding che per qualche motivo a me sconosciuto non viene effettuato in locale pur essendo parte dello stesso dominio (probabilmente un doppio check antispam sulle mail in uscita). Si notano poi continui rimbalzi altrettanto inspiegabili (le mail tornano ad un certo nodo dopo che le ha buttate fuori lui stesso).

Chiederò spiegazioni al supporto.

UPDATE: @cxunix ha definito il fenomeno come “Il giro della posta in 80 MX”. Ci facciamo un film?

Leave a Reply

%d bloggers like this: