Our out-of-band status information is available via Twitter @EmployeesOrg; bookmark or follow for emergency status updates.
We remind users we do NOT back up user data and the disaster recovery plan is to wipe the system and start anew. If this is not acceptable to you, you may have outgrown what Employees.Org offers and should consider a commercial service
User data on the employees.org Web servers are not backed up. You should maintain copies of your data elsewhere. Disaster recovery for employees.org will consist of reinstalling the system from scratch, without any user files.
Questions / assistance, email: email@example.com
Too many login failures from the same IP address causes that IP address to be blocked for a few minutes. Repeated login failures from that same IP address causes it to be blocked forever. To remove a block, send both your IP address (visit showip.employees.org:81) and Employees.org account name to admin.
All incoming mail is processed by an IronPort spam firewall. It is configured to drop incoming mail that it determines is spam, and to mark messages it suspects are spam. If you would prefer, instead, that it tag and deliver your spam, please email a request to admin.
See also Can't login via SSH or IMAP.
You can configure your email client (Thunderbird, Outlook,
Mail, etc.) to use
See also Can't login via SSH or IMAP.
Configure your mail user agent (Thunderbird, Outlook, etc.) to use mail.employees.org port 25, with TLS and "plain" authentication, using your username and password. Only your username needs to be specified (not @employees.org).
Many ISPs (Earthlink, for one), companies, and some hotels block access to external SMTP server from their networks. This will make it impossible for you to use mail.employees.org as your outbound mail server.
You can test connectivity by doing:
telnet mail.employees.org 25
If connections to tcp/25 are blocked, you can:
Your PATH doesn't include both '/bin' and '/usr/bin'. This wasn't required on Solaris, but is required on FreeBSD.
You can update PATH by editing either '~/.profile' (if you use a shell like bash) or '~/.login' (if you use a shell like csh). If you're not sure, start with .login; we default to csh. The easiest editor to use on UNIX is pico:
Disk quotas have been turned on, with a hard quota of 1GB. If you have more than 1GB in your home area, you will not be allowed to create new files until you have freed up some disk space. You can find out how much disk space you are using by typing the command:
Yes, please email your request to admin
We use the Apache "UserDir" directive to point user URLs to the files. The format for this is to append a Tilde ("~") followed by the account's username to the end of the host URL. Thus the file:
The Apache installation on employees.org is configured to REQUIRE an index.html (or index.php, index.cgi, etc.) in a directory to show a web page for a given URL. This means that users must take deliberate action to expose their data and are less likely to expose data by accident. Yes, this is different from the default settings used in a lot of other Apache installations.
At the bottom of this section are instructions for using webit, which will adjust permissions.
The web server accesses your files using file system ACLs, which is indicated by a "+" in the directory permissions.
This is an explanation of the ideal permissions for the user example. These are the minimal permissions necessary.
Your /users symlink should be owned by you. It doesn't matter what group or permissions:
> ls -lad /users/example
lrwxr-xr-x 1 example example 21 May 31 23:15 /users/example -> /export/homea/example
Your home directory should be owned by you, group owned by you, and at least executable by group, and have an ACL ("+"). Your WWW directory (and SWWW directory, if you have one) should be owned by you, group owned by you, group readable and executable, and have an ACL ("+"). The ACL can be viewed with the getfacl command, and should be the same for both your top-level directory and the WWW directory itself:
> # your home directory
> ls -lad /export/homeaa/example
drwx--x---+ 40 example example 2.5K Jun 14 07:02 /export/homeaa/example
> # your WWW directory
> ls -lad /users/example/WWW
drwxr-x---+ 27 example example 1.5K Jun 8 18:01 WWW/
> getfacl ~/WWW
# file: /home/example
# owner: example
# group: example
If any of these are broken, you can fix it yourself with the webit program located in "/usr/local/bin/". As its parameter, give webit the directory or files you need the permissions and group ownership changed on as an argument to webit. For example, to fix your WWW and SWWW directories, enter the commands:
> /usr/local/bin/webit -R ~/WWW
> /usr/local/bin/webit -R ~/SWWW
We use the suPHP apache module to run PHP as the user. The typical problem is permissions; you can reset the permissions on your account by using webit described above
Make sure your CGI script ends in .cgi and outputs a valid Content-Type: header. Check the files
/var/log/httpd/employees.org-error_log /var/log/httpd/employees.org-access_log /var/log/httpd-suexec.log
AddHandler cgi-script .not-a-cgi
New accounts are now being accepted. The same Operating Policy as used before applies to the accounts. Be sure to read the Operating Policy. Most importantly, the total amount of disk space PER SPONSOR is 1GB.
Create a new account by clicking here.
To request a password reset use the online form at Reset Password and follow the instructions there.
First off - Thank You for not just abandoning the account!
To request an account deletion, send mail to firstname.lastname@example.org from either the Employees.org account or the account's sponsor.
This will be sent to the humans currently handling account deletion. You may be asked to confirm if you really want the account deleted. The nukeme existed before the lost password facility and many folks requesting deletion are unaware of the password reset mechanism. The majority of the deletion requests are rescinded once the users learn of it.
Employees.org currently consists of a single host - clarinet.employees.org. This is the same physical host as mail.employees.org, www.employees.org, etc., as well as the A record for just plain ol' employees.org. If we start splitting services onto more hosts in the future, this situation could change. However, after 10 years the shell host will still be employees.org.
To login, you need an SSH client. Windows 10, all Unix varients, and MacOS all come with a built-in SSH client. Pre-Windows 10 you will need to install Putty.
Use the ssh client to login to employees.org. First time you try logging in, you will be shown our SSH fingerprint, which can be validated by comparing to the fingerprints at the very bottom of this FAQ page.
First, make sure you're using '/usr/local/bin/perl' rather than '/usr/bin/perl'. Then, if the module still doesn't appear to be installed, contact help to request it.
This is untested, but Steve Richey has pointed out the instructions at Macromedia's site.
Mailman is a web-based mailing list management interface.
To administer your mailing list, go to the administration interface found at http://www.employees.org/mailman/admin/*LISTNAME* where *LISTNAME* is the name of your mailing list. Your mailing list subscribers can change their settings at http://www.employees.org/listinfo/*LISTNAME*. These URLs are in List-* headers of each message sent through the list, as well as at the message footer.
Send your request to admin and the human behind it will create the list when they can get to it. No guarantees on how long that may be (could be weeks).
In your email, specify your preferred Mailing List address. It is better if the Mailing List name is over 8 characters in length so it won't accidentally collide with the username space. A good way to do this is to end the list name with "-list", such as "email@example.com".
You also need to say who the "owner" of the list is and this MUST be an @employees.org account. You can add other E-mail addresses to administrate the list after it is created, but we need this information to track who is responsible for what mailing list.
Send E-mail to admin with the name of the list to be deleted. The mailman administrators will check that the request is valid by asking the list administrator of the list in question for confirmation. When confirmation is received, the mailman administrators will then delete the list.
We are now allowing MySQL databases again. To create yourself a database, run the mysqlme located in "/usr/local/bin/". The program will create a MySQL user entry for your userid and then create a database for you with the name of your userid. You can
have more than one database by specifying a database name with the "-db dbname" option. A database will then be created called "userid_dbname".
For example, if userid john wanted to create a second DB for his account to hold recipes, he could type:
/usr/local/bin/mysqlme -db recipes
If you forget your userid's mysql password, you can force a reset of it with the program "mysqlpwr".
There is a mailing list of highly experienced employees.org users that have a broad variety of expertise that can help with your questions. Send mail to firstname.lastname@example.org with as much detail of your question as possible. Note that the list has a limit on the size of mail it will accept. Rather than send long files, such as log entries, you should save them to a file in your personal web space (under WWW/) and mail a link to the file in your message.
256 SHA256:Cr88eesO+JlhsiqCmRZPxSX+fDAH4dXhyiQyo38h2M4 employees.org (ED25519) 2048 SHA256:yS42z7+UHA/nZwyQRM4gCeY2aU/S+sJRhoyaW4Mp0Mc employees.org (RSA) 256 SHA256:xqhiHgo3wFXqRLpouycLtxZxTFybWDsfenqIr0WPvI0 employees.org (ECDSA)