Jump to content

DWD

Members
  • Posts

    295
  • Joined

  • Last visited

Contact Methods

  • Website URL
    http://www.danzfamily.com

Profile Information

  • Gender
    Male
  • Location
    Tulsa, Oklahoma

DWD's Achievements

Community Regular

Community Regular (8/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I replied to the original setup email from TCH and requested assistance. Tina responded immediately and fixed the problem with the nospam.TCH password reset email no getting through. TCH support is the reason I remain a customer!!!
  2. Signed up, now wife isn't getting email relating to kid's school, scouts, PTA, etc. Went to nospam.totalchoicehosting.com and did the lost password option but neither of us ever received a password reset email. Tried a gmail address associated with TCH and at least it recognized this was not an email address associated with the spam filter. Where is the "button" you speak of and all the quarantined emails? In the nospam.TCH site? I'm sure its all no-brainer simply, but right now the wife and I just can't figure it out...and I'm catching flack from my better half. Thanks in advance for your assistance.
  3. I hate to disagree with you since I barely understand this stuff, but after much more trial and error and additional research, I think the following is what is needed to clear up the new archive folder error: >#==== NEW DEFAULT FOLDER PERMISSION ===== DirUmask 0022 First note spelling of "DirUmask" and, second, note that the perms command works differently than the mask command, in short, it works backwards. Anyway, the above code is what worked for me.
  4. And or those of you coming to this thread with Movable Type problems, I just posted the below in the MT forum: When the upgrade hit my server, my Movable Type blog developed multiple problems namely a lot of "Error 500 Internal server error." The following is what I learned the hard way as to how to fix the problems. Maybe it will save someone the hours I spend figuring it out. First, you need to change the file permissions on all of your Movable Type files that end in ".cgi" to 755. For me, most of the .cgi files were found in public_html/cgi-bin/mt4 folder and I found one straggler elsewhere. Second, long...oh, so very long...story short, the MT default, at least for version 4.x, is to assign permission 666 to all files it creates. This causes problems with the new PHP upgrades. Additionally, manually tweaking the permissions will only provide a temporary fix as MT will change the permission back the next time it creates the file. I was able fix the errors by making MT assign permission 644 to all files it creates. I accomplished this by adding the following at the very end of my mt-config.cgi file: >#==== NEW DEFAULT FILE PERMISSION == HTMLPerms 0644 Since making these changes, everything has worked fine.
  5. Recently TCH began upgrading PHP on their many servers as discussed here. When the upgrade hit my server, my Movable Type blog developed multiple problems namely a lot of "Error 500 Internal server error." The following is what I learned the hard way as to how to fix the problems. Maybe it will save someone the hours I spend figuring it out. First, you need to change the file permissions on all of your Movable Type files that end in ".cgi" to 755. For me, most of the .cgi files were found in public_html/cgi-bin/mt4 folder and I found one straggler elsewhere. Second, long...oh, so very long...story short, the MT default, at least for version 4.x, is to assign permission 666 to all files it creates. This causes problems with the new PHP upgrades. Additionally, manually tweaking the permissions will only provide a temporary fix as MT will change the permission back the next time it creates the file. I was able fix the errors by making MT assign permission 644 to all files it creates. I accomplished this by adding the following at the very end of my mt-config.cgi file: >#==== NEW DEFAULT FILE PERMISSION == HTMLPerms 0644 Since making these changes, everything has worked fine.
  6. Is this online status indicator service still being provided by TCH?
  7. It's not just an illusion. Each year becomes a smaller fraction of our lives, so with the measuring stick by which we compare each year constantly changing, each year does indeed become shorter as we grow older. In grade school, summers lasted an eternity. By high school they were shorter and by college shorter yet. In my forties, last year I bought a bunch of mulch in the spring to spread around in my flower gardens during the summer. Summer came and went before I realized I hadn't opened a bag. Kids growing up so fast. The realization that we are only on this earth a short time. Make today count, there aren't enough tomorrows.
  8. TCH Blog Looks like posts went up starting on February 4, 2008, and ended 8 days later on the 12th. Dead project?
  9. Grrrr... Yes, I want to do the correct, official, recommended, approved, proper, not-a-work-around, way to access SquirrelMail both securely and insecurely (two links). Surprisingly, this is not a simple question. 1) Can I access Squirrelmail in the recommend manner which won't go away soon directly, without first going through WebMail and then Selecting SquirrelMail? 2) Does your comment refer to both links I posted in bold or only to the secure link? 3) I can't access WHM (WebHostManagement) to alter ports such as 465 and 995 and proxy settings because I don't have a reseller account, correct? _____________________________ In other words, for evryone's benefit, what are the six official direct links that TCH customers should use to access Horde/SquirrelMail/RoundQube both securely and insecurely???
  10. I submitted a ticket and the awesome TCH folks fixed it right up for me. All is working well, and for anyone who come across this later, here are the secure and insecure links for SquirrelMail: E-mail (Secure) https://felucia.tchmachines.com/sqmail/ E-mail (Insecure) http://www.domain-name.ext/sqmail/
  11. I tried the link and got the following error message: I'll submit a help ticket and report back. Thanks.
  12. And...we just stepped outside my area of understanding. Where and how do I make these settings? I'm really ignorant about everything "ports" related. Does some have a good reference source on the topic?
  13. I successfully allowed the exception but I get the following error message when I go to address:
  14. I tried that and I get the following error message:
  15. I know this has been covered elsewhere, but it has been covered different ways under different circumstances that I'm not sure what now applies since I just got the server update. For my non-secure SquirrelMail, I now use: http://domain-name.com:2095/3rdparty/squirrelmail/index.php What do I use for secure https SquirrelMail access (directly without going through webmail first)? Or can I not do that without my own SSL (?) certificate? Thanks.
×
×
  • Create New...