Was transferring a domain today. It was set up to have as the admin contact an email box at sonic.net that luckily kept the messages. For some reason, the notification of unlocked emails, authorization codes, and all emails after the transfer was initiated were forwarded from the sonic inbox, but NOT the repeat emails requesting a transfer initiation. This was so bizarre I didn't even log-in to check on this until the last step as I had such confidence in sonic of all the other services involved.
Transferring from Godaddy (they have messed with transfer requests in the past, so I was looking for that), to Namesilo (their like the sonic of domain name registrars, everyone should use them), with the admin contact on a non-private (public, since it's .us and privacy is not allowed) whois listing as a sonic.net email address, forwarding to a hotmail account.
All channels were working surrounding these emails and everything fired perfectly as intended to get around DNS/NS/Godaddy etc. problems by setting things up this way based on past experience and obvious best practices for example not using your admin contact as the email address you are attempting to transfer a domain with attached to that domain...
How/Why did this happen? Do I have to change what I thought was a pretty bullet proof system again? I've grabbed the header of these emails and I don't see a reason they weren't forwarded, here it is:
Would a spam score of 1.1 meet a rule not to forward, but not to fire other actions? That's my best guess...
But, I can't find this in the members panel for the master user of that account.
Transferring from Godaddy (they have messed with transfer requests in the past, so I was looking for that), to Namesilo (their like the sonic of domain name registrars, everyone should use them), with the admin contact on a non-private (public, since it's .us and privacy is not allowed) whois listing as a sonic.net email address, forwarding to a hotmail account.
All channels were working surrounding these emails and everything fired perfectly as intended to get around DNS/NS/Godaddy etc. problems by setting things up this way based on past experience and obvious best practices for example not using your admin contact as the email address you are attempting to transfer a domain with attached to that domain...
How/Why did this happen? Do I have to change what I thought was a pretty bullet proof system again? I've grabbed the header of these emails and I don't see a reason they weren't forwarded, here it is:
Code: Select all
Return-Path: <bounce+a72a9e.7bbab-MYSONICINBOXUSER=sonic.net@namesilo.com>
X-Spam-Checker-Version: SpamAssassin 3.4.3 (2019-12-06) on h.spam.sonic.net
X-Spam-Level:
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
HTML_MESSAGE,MIME_HTML_ONLY,RCVD_IN_DNSWL_NONE,SNF4SA,SPF_HELO_NONE
autolearn=disabled version=3.4.3
X-Spam-SNF-Result: 0 (Standard White Rules)
X-Spam-MessageSniffer-Scan-Result:
X-Spam-MessageSniffer-Rules:
0-0-0-6044-c
X-Spam-GBUdb-Analysis: 0, 157.131.224.145, Ugly c=1 p=-0.513545 Source Normal
Received: from b.mx.sonic.net (a.spam-proxy.sonic.net [157.131.224.145])
by b.local-delivery (8.14.7/8.14.7) with ESMTP id 00C1AQ7W022149
(version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT)
for <MYSONICINBOXUSER@lds.sonic.net>; Sat, 11 Jan 2020 17:10:26 -0800
Received: from so254-58.mailgun.net (so254-58.mailgun.net [198.61.254.58])
by b.mx.sonic.net (8.14.7/8.14.7) with ESMTP id 00C1AOZ7077206
(version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT)
for <MYSONICINBOXUSER@sonic.net>; Sat, 11 Jan 2020 17:10:25 -0800
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=namesilo.com; q=dns/txt;
s=krs; t=1578791425; h=Content-Transfer-Encoding: Content-Type:
Reply-To: From: MIME-Version: Subject: To: Message-Id: Date: Sender;
bh=eEl7racOOx/1AyGgj/w+8ARfFCoTRjASGFUbCbNeh78=; b=C5E5gN372NB9wtVy3bjGvotlPk+ibObwq/TyeiMi6LEW+WOs8VQ2rC7LOCE0Gcw04LsIdUW6
OcJOqOc2rhVnk6OHohrxghzl3yJ8XHlDDIDfKIcXpaaoKRC/zk4c6aeeqlOq81/sU0Pvhtze
AgshM05LcuIMvkAx0ZZaH3PXlvE=
X-Mailgun-Sending-Ip: 198.61.254.58
X-Mailgun-Sid: WyJkNzFjMSIsICJ2b2RkZXJkb21haW5zQHNvbmljLm5ldCIsICI3YmJhYiJd
Sender: support@namesilo.com
Received: from m2.emailowl.com (m2.emailowl.com [198.199.111.6])
by mxa.mailgun.org with ESMTP id 5e1a71ff.7ff5607a3df8-smtp-out-n01;
Sun, 12 Jan 2020 01:10:23 -0000 (UTC)
Received: (qmail 2459 invoked by uid 99); 12 Jan 2020 01:10:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=namesilo.com; s=dkim;
t=1578791422; bh=kGyA6jDxfWDeUywbQiD5gTqYhWXFjzfzTkCRrjvx9WM=;
h=Date:To:Subject:From:Reply-To;
b=gqPxDuHuSaqyAEIuVUvKuEwByWe9FR4XtqdKoVy5H58Nee4/jiRw2QjoDP13oQ9Oo
pN6cwXduXWUlPqtfDkDTuQw1bHXUwcDU626v7KwbQKBKQ16k5holQskkwt37U5ikV/
ieRDRhYaJDZ/HW9RiubOr35kmcOtRCc4eSL38/4c=
Date: 12 Jan 2020 01:10:21 -0000
Message-Id: <20200112011021.2458.qmail@m.emailowl.com>
To: MYSONICINBOXUSER@sonic.net
Subject: Confirm Domain Transfer for MYTRANSFERRINGDOMAIN.us
X-Accept-Language: en-us, en
MIME-Version: 1.0
From: "NameSilo.com" <support@namesilo.com>
Reply-To: support@namesilo.com
X-NSID: ZmtmAmZ0ZmZmZt==q3q167sr1orn56707383n0r30s77r3pp
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Orthrus: tar=0 grey=no co=US os=Linux/3.11 and newer/1 spf=pass dkim=pass
But, I can't find this in the members panel for the master user of that account.