That means SG addresses are still broken on 3 of the most notable privacy friendly mail providers (Protonmail, Tutanota, Riseup).
Can anyone explain why this seems to be resolved for some email providers and not others?
$ dig @1.1.1.1 +noall +answer 0sg.net
0sg.net. 1800 IN A 216.75.62.102
$ dig @1.1.1.1 +noall +answer neverbox.com
neverbox.com. 1800 IN A 216.75.62.100
$ dig @1.1.1.1 +noall +answer xoxy.net
xoxy.net. 1795 IN A 216.75.62.100
dig @1.1.1.1 +noall +answer spamgourmet.com
spamgourmet.com. 1800 IN A 216.75.62.102
$ dig @1.1.1.1 +noall +answer 9ox.net
9ox.net. 1800 IN A 216.75.62.100
$ dig @1.1.1.1 +noall +answer dfgh.net
<blank>
dig @1.1.1.1 +noall +answer antichef.com
antichef.com. 1800 IN A 216.75.62.100
dig @1.1.1.1 +noall +answer recursor.net
recursor.net. 1800 IN A 216.75.62.100
dig @1.1.1.1 +noall +answer gourmet7.spamgourmet.com
gourmet7.spamgourmet.com. 1800 IN A 216.75.62.102
$ dig @one.one.one.one -t A +noall +answer neverbox.com
neverbox.com. 1800 IN A 216.75.62.100
$ dig @one.one.one.one -t MX +noall +answer neverbox.com
neverbox.com. 1800 IN MX 10 gourmet7.spamgourmet.com.
$ dig @one.one.one.one -t PTR +noall +answer neverbox.com
<blank>
$ dig @one.one.one.one -t TXT +noall +answer neverbox.com
neverbox.com. 1800 IN TXT "v=spf1 mx ip4:216.75.62.81 ip4:216.75.62.102 -all"
$ dig @one.one.one.one -t MX +noall +answer gourmet7.spamgourmet.com
<blank>
$ dig @one.one.one.one -t MX +noall +answer gourmet8.spamgourmet.com
gourmet8.spamgourmet.com. 1799 IN MX 10 gourmet8.spamgourmet.com.
$ dig @one.one.one.one -t TXT +noall +answer gourmet7.spamgourmet.com
$ dig @one.one.one.one -t TXT +noall +answer gourmet8.spamgourmet.com
gourmet8.spamgourmet.com. 1800 IN TXT "v=spf1 mx ip4:216.75.62.102 ip4:216.75.62.81 ip4:216.75.62.100 -all"
$ dig @one.one.one.one -t MX +noall +answer gourmet9.spamgourmet.com
<blank>
dig @one.one.one.one -t TXT +noall +answer gourmet9.spamgourmet.com
<blank>
Received-SPF: pass client-ip=216.75.62.102; helo=gourmet8.spamgourmet.com
$ dig @1.1.1.1 +noall +answer -x 216.75.62.102 //IP address of gourmet7
102.62.75.216.in-addr.arpa. 43200 IN PTR gourmet.spamgourmet.com.
$ dig @1.1.1.1 +noall +answer -x 216.75.62.81 //IP address of gourmet8
81.62.75.216.in-addr.arpa. 43200 IN PTR gourmet8.spamgourmet.com.
$ dig @1.1.1.1 +noall +answer -x 216.75.62.100 //IP address of gourmet9
100.62.75.216.in-addr.arpa. 43200 IN PTR gourmet.spamgourmet.com.
$ dig @1.1.1.1 -t A +noall +answer gourmet.spamgourmet.com
gourmet.spamgourmet.com. 1800 IN A 216.75.62.102 //Same IP as gourmet7
$ dig @1.1.1.1 -t MX +noall +answer gourmet.spamgourmet.com
<blank>
$ dig @1.1.1.1 -t TXT +noall +answer gourmet.spamgourmet.com
<blank>
facetto wrote:[...] I now changed the forwarding adress to gmail and contacted protommail for support.
Clewby wrote:[...] and changed my protected address to the new provider..
From reading around this forum, it looks like Spamgourmet is not currently working with
protonmail
tutanota
riseup
freenet.de
[...]
how could you change to the new forwarding address? you have to confirm a link in an email to the old/actual address. this email gets lost (again). is there a switch where you can cancel this security option?
Clewby wrote:The confirmation of change of protected address gets sent to the new address.
Received: from w4.tutanota.de ([192.168.1.165])
by tutadb.w10.tutanota.de
with SMTP (SubEthaSMTP 3.1.7)
Mon, 30 Jan 2023 16:39:19 +0100 (CET)
Received: from gourmet8.spamgourmet.com (gourmet.spamgourmet.com [216.75.62.102])
by w4.tutanota.de (Postfix) with ESMTPS
Mon, 30 Jan 2023 15:39:19 +0000 (UTC)
Received: from spamgourmet by gourmet7.spamgourmet.com with local (Exim 4.94.2)
(envelope-from <board@bbs.spamgourmet.com>)
id 1pME2n-0006bS-IO
Sun, 29 Jan 2023 20:12:53 +0000
Received: from server322-5.web-hosting.com ([198.54.116.172])
by gourmet7.spamgourmet.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <board@bbs.spamgourmet.com>)
Sun, 29 Jan 2023 20:12:53 +0000
Received: from [::1] (port=60834 helo=server322.web-hosting.com)
by server322.web-hosting.com with esmtp (Exim 4.95)
(envelope-from <board@bbs.spamgourmet.com>)
Sun, 29 Jan 2023 15:12:52 -0500
The following is a summary of the two (Spamgourmet bbs) articles you provided.
1. Spamgourmet refused to forward some original emails due to a PTR error (a "Reverse DNS lookup" error).
MEANING:
(1) Those emails were never forwarded to the final recipient. Spamgourmet refused to forward those emails.
(2) Spamgourmet refused to forward those emails because Spamgourmet considered them from spammers. Spamgourmet even refused to forward emails from Gmail.
(3) A Spamgourmet user said the original sender server did have set up the PTR record, and this could be a tech issue with Spamgourmet. Spamgourmet's tech team should look into this issue.
2. The problem was/is with Spamgourmet's official domains (0sg.net / neverbox.com / spamgourmet.com).
3. This could be a DNS issue with Spamgourmet's service provider, Namecheap. Namecheap's DNS server did not provide the correct (lateset) PTR results.
4. This could be a TLS cert-checking issue on Spamgourmet. Spamgourmet did not seem to accept all common TLS certs.
The situation you described is consistent with the issues mentioned in those articles. It seems to be a technical issue with Spamgourmet.
We (Proton) also checked our ban list. Spamgourmet [216.75.62.102] is not on our ban list. We do not reject emails from Spamgourmet.
Certificate chain
0 s:CN = protonmail.com
i:C = US, O = Let's Encrypt, CN = R3
a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
v:NotBefore: Dec 27 13:13:08 2022 GMT; NotAfter: Mar 27 13:13:07 2023 GMT
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
v:NotBefore: Sep 4 00:00:00 2020 GMT; NotAfter: Sep 15 16:00:00 2025 GMT
Return to Support / Hilfe / ayuda / ondersteuning / ...
Users browsing this forum: No registered users and 149 guests