I could be experiencing more than one problem, but it looks like mail is not being forwarded to protected addresses from neverbox addresses, in my case, since approximately 2023-01-17 03:00 and still not working now. I see mails going into spamgourmet and being processed, as the counter for various addresses is decrementing, but nothing is being delivered to the protected addresses (this applies to more than one account).
Furthermore, (Tests now on 2023-01-27 at about 08:30 UTC) if I send a message to a new neverbox address, the address is (auto)created, and I can see that as far as spamgourmet is concerned, the message has been forwarded/processed as the message counter is decremented, but nothing arrives at the protected address.
A subsequent message to the same address shows the same behaviour - the message counter is decremented, but nothing arrives at the protected address.
If I use the feature that allows me to send a message that appears to come from the spamgourmet neverbox address, it does not appear to be processed, and the message counter is not decremented.
If I subsequently send a normal message the message counter is decremented, but nothing arrives at the protected address.
I don't run my own mail server, so I can't contribute more to diagnosis and testing. Sorry about that. I hope the problem is identified and resolved soon.
Edit to add:
If I need to contact the email provider of the protected address to advise that they need to make some configuration changes, please put a notice in this thread.
Edit to further add:
I don't know if this is correct. It looks a bit inconsistent.
- Code: Select all
$ 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
All of the above have gourmet7.spamgourmet.com as their MX record.
- Code: Select all
dig @1.1.1.1 +noall +answer gourmet7.spamgourmet.com
gourmet7.spamgourmet.com. 1800 IN A 216.75.62.102
Edit further again to add:
Used
https://dnschecker.org/ for convenience, but presenting salient results from dig
- Code: Select all
$ 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"
//Comment: 216.75.62.81 is gourmet8.spamgourmet.com , 216.75.62.102 is gourmet7.spamgourmet.com , and not listed is 216.75.62.100 which is gourmet9.spamgourmet.com
look at gourmet7
- Code: Select all
$ dig @one.one.one.one -t MX +noall +answer gourmet7.spamgourmet.com
<blank>
look at gourmet8
- Code: Select all
$ dig @one.one.one.one -t MX +noall +answer gourmet8.spamgourmet.com
gourmet8.spamgourmet.com. 1799 IN MX 10 gourmet8.spamgourmet.com.
So gourmet 7 has no MX record, but gourmet 8 has.
look at gourmet7
- Code: Select all
$ dig @one.one.one.one -t TXT +noall +answer gourmet7.spamgourmet.com
look at gourmet8
- Code: Select all
$ 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"
So gourmet 7 has no TXT-SPF record, but gourmet8 has. And note that gourmet 8's TXT-SPF record lists three host ip addresses: those of gourmet7 (216.75.62.102), gourmet8 (216.75.62.81) and gourmet9 (216.75.62.100)
So, for completeness, look at gourmet9
- Code: Select 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>
I am no expert. At all. But it does look a little inconsistent.
Note that the last email I received via spamgourmet came from gourmet8 - from the header
- Code: Select all
Received-SPF: pass client-ip=216.75.62.102; helo=gourmet8.spamgourmet.com
Is the issue that the DNS MX and TXT-SPF records are missing for gourmet7 and gourmet9?
Reverse lookups
- Code: Select all
$ 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.
...and gourmet.spamgourmet.com
- Code: Select all
$ 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>