skullys

Working Now.....Thanks for the quick fix!!

None of those should have been the primary domain I've been using for hosting or logging in

ecubaseball.com ecubasketball.com ecupirates.net skullypirate.com skullyspiratewear.com My user id is skully.... Thank You!

On going Since Yesterday... Plesk Control Panel shows domain IP address : [removed]

Login To HelioHost No response from server. Try again in a bit.

Absolutely delete those subdomains... I never really understood why they were there (after the switch to Plesk)

Please Add The Following Two Domains 1. professionalpetart.com 2. rkives-art.com user name is skully... Thanks!

Account Suspended.... Krydos, Sorry for being the one behind the server IP Blacklisting... especially after all your hard work to bring Heliohost & Tommy back to life! Will I be permitted to log back in to this account to update all passwords... hopefully to prevent this from happening again?

Here's more from the header... Authentication-Results: tommy2.heliohost.org; dmarc=none (p=NONE sp=NONE) smtp.from= header.from=tommy2.heliohost.org (Mail Delivery System) X-Spam-Level: Auto-Submitted: auto-replied Mime-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="1C2FF40950E9.1653669696/tommy2.heliohost.org" X-Spam-Status: No, score=-1.9 required=2.0 tests=BAYES_00,HTML_MESSAGE, NO_RELAYS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tommy2.heliohost.org Return-Path: <MAILER-DAEMON> X-Original-To: skully@thepiratestore.com Received: by tommy2.heliohost.org (Postfix) id 1A0B14094BF3; Fri, 27 May 2022 16:41:36 +0000 (UTC) Delivered-To: skully@thepiratestore.com Message-Id: <20220527164136.1A0B14094BF3@tommy2.heliohost.org> Undelivered Mail Returned to Sender

Re: Skully@thepiratestore.com -- I've received over 1500 of these rejected/bounced email responses just this morning.... Nothing that I've actually sent but coming from my email address.... Any way other than taking that email address off line to stop this? This is the mail system at host tommy2.heliohost.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <fhj.heintz@gmail.com>: host gmail-smtp-in.l.google.com[142.250.141.26] said: 550-5.7.26 This message does not have authentication information or fails to 550-5.7.26 pass authentication checks. To best protect our users from spam, the 550-5.7.26 message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. e20-20020a056808149400b003261af3133esi6526770oiw.96 - gsmtp (in reply to end of DATA command) <mrmac969@gmail.com>: host gmail-smtp-in.l.google.com[142.250.141.26] said: 550-5.7.26 This message does not have authentication information or fails to 550-5.7.26 pass authentication checks. To best protect our users from spam, the 550-5.7.26 message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. e20-20020a056808149400b003261af3133esi6526770oiw.96 - gsmtp (in reply to end of DATA command) Reporting-MTA: dns; tommy2.heliohost.org X-Postfix-Queue-ID: EB9974073B9C X-Postfix-Sender: rfc822; skully@thepiratestore.com Arrival-Date: Fri, 27 May 2022 16:02:18 +0000 (UTC) Final-Recipient: rfc822; fhj.heintz@gmail.com Original-Recipient: rfc822;fhj.heintz@gmail.com Action: failed Status: 5.7.26 Remote-MTA: dns; gmail-smtp-in.l.google.com Diagnostic-Code: smtp; 550-5.7.26 This message does not have authentication information or fails to 550-5.7.26 pass authentication checks. To best protect our users from spam, the 550-5.7.26 message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. e20-20020a056808149400b003261af3133esi6526770oiw.96 - gsmtp Final-Recipient: rfc822; mrmac969@gmail.com Original-Recipient: rfc822;mrmac969@gmail.com Action: failed Status: 5.7.26 Remote-MTA: dns; gmail-smtp-in.l.google.com Diagnostic-Code: smtp; 550-5.7.26 This message does not have authentication information or fails to 550-5.7.26 pass authentication checks. To best protect our users from spam, the 550-5.7.26 message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. e20-20020a056808149400b003261af3133esi6526770oiw.96 - gsmtp

Thanks.... We're Good Now!

none really just wanting to get rid of the 500 server error page on this domain and others if possible

How do I fix this.... [core:alert] /home/skullyspirategear.com/public_html/.htaccess: Options not allowed here

Try This... skullyspirategear@gmail.com

Plesk ETA page says I should have received email for transfer but have not... skullythepirate@suddenlink.net is the address it should go to Thanks!

Krydos, Great to hear Heliohost is emerging from its zombie state and beginning to transfer accounts.... Quick question, Plesk ETA indicates a rate of 1 account per day being moved, is that accurate? Thanks for your sacrifice, hard work and relentless drive... it was absolutely necessary to get us to this point. We do in fact appreciate what you have accomplished!

If Possible....Why not just let each account holder decide whether it's better, because of the issues you mentioned, to wait for the complete Plesk code to be rewritten, or if they aren't needing to address such issues, would simply be happy to start from scratch? At this point in time, an option such as this would be preferable to the uncertainty we now face. I'm sure many would agree...

A brief followup to my original question... If Heliohost is unable to produce a working Plesk transfer code that is compatible with current accounts & backups, Is it not possible to simply scrap the idea of a rewrite and basically start from scratch for each Heliohost account utilizing whatever code and resources that Plesk currently uses for new accounts & set up? While I'm sure no one likes the prospect of losing the full range of service and functionality previously provided by Heliohost,... after 7+ months without c-panel, that functionality has essentially already been lost. While I appreciate the commitment of Heliohost to it's account holders and it's effort to satisfactorily resolve this unfortunate situation, it may now be time to look at less than ideal solutions to get Heliohost back up and running. Thanks again for providing years of outstanding service and looking forward to many more!

I understand there's no firm date to begin account / file transfers but any estimate / update on progress so far... Krydos, assuming you don't have to start from scratch each time you run into problems while building this beast, % estimate on current status regarding where you've successfully gotten us so far on this project? 10% there...25%...etc. Thanks for being the point man on this deal....

Do You Anticipate Beginning Account Transfers Before The End Of January?

Do you anticipate beginning account transfers before the end of January?

Any Tech / Coding Support From Plesk Or Is Krydos Basically Flying Solo?

We're Good...Thanks!

Then I Got This Message... The IP address 75.110.162.66 has been blocked for trying to log in to IMAP with the wrong password too many times. To prevent this from happening again in the future please make sure your email client username and password are correct. You won't be able to continue to cPanel until an admin unblocks you. To request that your IP be unblocked please visit

Let's see what happens this morning... Please unblock IP address 75.110.162.66