Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by rayners

  1. It can be anywhere you want it to be. That's what the $data_dir variable in config/config.php is for. I think the default value is data/ in your SquirrelMail directory.
  2. It may not be the perfect solution, but it should work. You could change data/ to 666.
  3. Did you use 'user' and 'database' or 'tchaccountname_user' and 'tchaccountname_database'?
  4. What were the error messages in the bounced email?
  5. Actually, Lianna, mod_gzip is a module for Apache. What it allows you to do is compress pages on their way out to reduce bandwidth. The pages are then uncompressed in compatible browsers. More info here.
  6. I still seem to be getting the error with my test script on server4, but I'll give it a shot anyway. Update: Talking to Bill, they just haven't gotten to server4 yet. I can wait a few minutes. Thanks a bunch for getting this worked out Alan.
  7. rayners


    http://www.******/cgi-bin/mail.cgi is the correct location. You are getting a server error because the script exited with an error.
  8. Hey, I've got a vested interest in seeing this working. So don't pretend there is any form of altruism involved here.
  9. Just submit a help desk ticket and they should fix you right up.
  10. Okay, here's what I found. I found a definate error within the library, and that is why Image::Magick is not working at the moment. It may be the case that the ImageMagick library, which Image::Magick uses, may be in need of an upgrade/rebuild. I'll have to get in touch with Bill to okay it. I'll let you know if that solves the problems on my server. Update: Talked to Bill, and sent all the information I gathered to Alan to work things out. Keep your fingers crossed.
  11. Whoops, seems my initial look through the documentation was faulty. I got a function name wrong, and that's what was generating the error. Time to do some more testing and investigation.
  12. Well, after playing around with it for a couple minutes on rayners.org's server, I think I may have found the problem. It seems that the perl module Image::Magick may not be fully installed, or it's installed in non-standard place. I'll try and catch up with Bill and let you know if I find out anything else. More on this later. Edit: Perhaps I was wrong. I am getting the exact same errors on my own machine at home. This is getting weird. Time to read some documentation.
  13. CPanel does not use port 8080 at all. It uses 2082, if memory serves me right. Other people have had problems connecting to CPanel through a work firewall.
  14. I guess I won't have to forward you the BugTraq posting then, Bill.
  15. After taking a quick look at it, I'm not sure. You can certainly add as many users as you want to the database, but access to the default PhpMyAdmin through CPanel, like CPanel itself, requires your main account name and password. You might be able to setup PhpMyAdmin yourself on your site and let your friends login through there. I don't see any reason why that shouldn't work. Would that be kosher, Bill?
  16. After tinkering with things in my account, it looks like using that script may not be possible. Mailman's config files for each list are readable by Mailman only. Which is probably safest anyway. If anybody could read those files, they could run dumpdb on them and get all the users' passwords. I'll have to see if I can come up with a way "around" that. No promises though. I'm glad to hear I could be of service, Todd. I have had a couple issues trying to run Image::Magick. I'm sure I can probably work them out, I just haven't yet sat down to do it because NetPBM works well enough for me at the moment.
  17. As far as I can tell from reading the docs and looking at my own mailing lists just now, they are stored in a file that only mailman can access. So perhaps the method described in the FAQ won't work.
  18. Here's something I found in the Mailman FAQ that you might find useful: 3.7. Setting up Web access using MM list passwords - for Apache The scripts there might require a little modification, but I imagine that should accomplish what you're looking for.
  19. I'm not exactly sure I follow what you want to do. Are you looking for each person to have a common username/password that can be used throughout your site? Is that the basic idea here?
  20. There's a number of software packages that come with that option now. I guess that's because a number of other hosts limit you to only one database.
  21. As far as I know, it is allowed. As for installing it, download the .tar.gz archive and upload it to your site. You can unpack the archive through the file manager in CPanel (or you could download and unpack the .zip archive on your own machine and upload the files yourself). After that, just follow the instructions in the INSTALL file, starting with step 3. To configure it, just copy the config/config_default.php file to config/config.php and edit that manually. Then you're off and running.
  22. The prefix is only necessary if you need to run more than one seperate version of the software in the same database. It should be unnecessary.
  23. You can also use CPanel to generate a private/public key-pair, which would allow you to do everything a private key does (e.g. ditigal signatures, decryption, etc) locally on TCH. Things like that could come in handy if you're using webmail on the system (do any webmail clients support PGP-like functions?) or if you're doing any crypto-type stuff in scripts (like some of the email <-> blog scripts I've been writing, though I've only needed public keys for that).
  24. Accessing your TCH mail through the "official" webmail clients requires use of port 2095. You can, however, install something like SquirrelMail on your site, and it will operate like any other part of your site (i.e. on port 80).
  • Create New...