James: What not to do

[Brian J. Sayatovic]

Here's a short list of things NOT TO DO when working with James.  I 
encountered these in my rapid carelessnes in the past couple of days:

1. Do not upgrade your JRE, delete your old JRE, and forget to edit the 
wrapper.conf to point to the newer JRE.

2. Do not forget to update your custom dependent libraries of your 
Mailet when you updates the james.sar.

3. Do not forget to make sure your primary MX record in your dynamic DNS 
is pointed to a valid A record, not an old one you no longer update.

4. Do not use UltimateZip to update james.sar as it seems to corrupt the 
archive from Java's perspective.

5. Do not delete the archive for your James installation so that when 
you corrupt your james.sar, you can just re-extract it from the archive.

6. Do not delete your old James files when installing a new version of 
James (that you had to download since you didn't save the last archive!) 
so that you can port your config files over.

7. Do not do any of these things at the same time you move your 
development environment around breaking all of your old deployment 
scripts slowing down the repair process.

8. Do not expect to quickly hear back on the job opportunities you 
inquired about using the e-mail address hosted on your James server if 
you have managed to FUBAR your server in the meantime.

I don't know if I subconiously wanted to cause pain for myself or what, 
but I did just that!

Regards,
Brian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]