PLEASE NOTE: If you had an account with the previous forum, it has been ported to the new Genetry website!
You will need to reset the password to access the new forum. Click Log In → Forgot Password → enter your username or forum email address → click Email Reset Link.
It's been a long time coming, but the new Genetry website and forums are now live.
We will be working to fix any issues that come up (including here in the forums!)
Please note that last month's posts (June-July 2023) will be missing until Invision Communities coughs up our forum data--that is, data they promised they wouldn't hold hostage. Right....!
The ecommerce store is currently not accessible; we are working on getting that functioning properly & tested, and then it will be available to everyone. Thank you for your patience!
Glad to see it coming together. Good luck over there.
Progress update: we're still getting hiccups sorted out. It has come to our attention that the "Reset Password" email function wasn't working; that should hopefully be sorted today! Sorry for the inconvenience.
It's pretty involved to basically move a website--and that's what we did when we moved the new site from a staging URL to the real URL. A lot of certs and internal pointers need updated before everything will work in the new "location".
MY password reset no problem .
@steve Perfect. We just got the certs back in order earlier...so now things should be behaving properly. Looking forwards!
FYI, to help avoid site emails being interpreted as spam:
X-Spam-Status: No, score=1.4 required=5.0 tests=HTML_MESSAGE,MIME_HTML_ONLY, RDNS_NONE,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS * -0.0 T_SCC_BODY_TEXT_LINE No description available.
It did pretty well, but would be a good idea to resolve that RDNS_NONE flag.
FYI, to help avoid site emails being interpreted as spam:
X-Spam-Status: No, score=1.4 required=5.0 tests=HTML_MESSAGE,MIME_HTML_ONLY, RDNS_NONE,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS * -0.0 T_SCC_BODY_TEXT_LINE No description available.It did pretty well, but would be a good idea to resolve that RDNS_NONE flag.
Thanks for the info! (We're aware that the DMARCS record isn't quite up-to-par at the moment.)
The issue that was causing customers issues likely had to do with the SSL certs not lining up when we moved the site from a "staging" path to the real path...plus then not having the necessary DNS records set up.
Trying to figure out how to resolve rDNS at the moment. Looks like it could be a bit...erm...challenging.
@notmario Got the reverse-DNS set and propagated...does the site pass the mail spam test better?
It will probably take a day or two for the caches to clear.
% Logic is a pretty flower that smells bad. owner$ nslookup mail.genetrysolar.com Server: 172.16.1.21 Address: 172.16.1.21#53 Non-authoritative answer: Name: mail.genetrysolar.com Address: 206.72.204.171 owner$ nslookup 206.72.204.171 171.204.72.206.in-addr.arpa name = server.chalspace.com. Authoritative answers can be found from: owner$ nslookup server.chalspace.com Server: 172.16.1.21 Address: 172.16.1.21#53 ** server can't find server.chalspace.com: NXDOMAIN
The @ notification emails result in this:
X-Spam-Report: * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -0.0 SPF_PASS SPF: sender matches SPF record * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS * 0.6 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML * tag
yeah, I see the "chalspace.com" which is what the rDNS was set to before I corrected it. A "dig" on my end showed the proper "genetrysolar.com" this morning:
Copied the "nslookup" and got the same "genetrysolar.com"; evidently the new news hasn't propagated all the way across the country!
~$ nslookup 206.72.204.171 171.204.72.206.in-addr.arpa name = genetrysolar.com. Authoritative answers can be found from:
On the dashboard I'm unable to register inverters
The text box works, but I don't have a submit button