Changing From SquirrelMail To Atmail Open With ISPConfig 3

http://www.howtoforge.com/changing-from-squirrelmail-to-atmail-open-with-ispconfig-3


Step 1 - Create A Database

First we need to create a database for Atmail.

* Open up ISPConfig and go to Sites.
* Select Database from the sub-navigation menu on the left.
* Click on Add new Database
* Create a Database name, Database user and a Database password


Step 2 - Backup Squirrelmail

Just in case it all goes wrong - we need to backup Squirrelmail.

cd /usr/share
mv squirrelmail squirrelmail.bak
mkdir squirrelmail


Step 3 -Download, Unpack And Remove Unnecessary Files

I was unable to get the latest version of Atmail open to work with my setup. For the purpose of this tutorial; we will be using v1.01 - Please feel free to let me know if you find a way to get the latest version working.

cd squirrelmail
wget http://downloads.sourceforge.net/atmailopen/atmailopen-1.01.tgz
tar xvfz atmailopen-1.01.tgz
cd atmailopen
mv * ../
cd ../
rm –r atmailopen
rm atmailopen-1.01.tgz


Step 4 - Make Atmail Open Writeable For Apache

chown –R [Apache-user] /usr/share/squirrelmail

Please note: On Debian systems, replace [Apache-user] with www-data. The Apache user on other Linux distributions might be different.


Step 5 - Install Atmail Open To Your Server

In your preferred browser, go to http://yourdomain.tld/webmail. You'll be required to read the on-screen instructions and read the licence agreement. Providing you accept you can continue!

Step 6 - Connect To The Database

In Step 1 we created a database in ISPConfig and we're now need to enter the details into the AtMail Open...

Step 7 - Define The SMTP Host

Enter the SMTP Host (in this example we assume it is localhost). Whether or not you require Authentication (e.g. if you need to use a mail relayer to send e-mail) and an Administrator E-mail Address.

Step 8 - Import Data From SquirrelMail (Or Another Webmail System)

At this step, you have the possibility to import data from other popular webmail systems. Should you decide to do this, please select Squirremail and enter the database connetion settings and click 'Continue'

Step 9 - All done! Log In To Atmail Open

You can now log in to your new Atmail Open Webmail system! It's all good to go from here but if you like, follow Step 10 to customise your login screen.

Step 10 - Customise The Login Screen

In this step we will cover how to remove the Mailserver, Language and Protocol fields from the login screen and define default settings so we don't need to input them manually everytime we login.

vi /usr/share/squirrelmail/html/login-light.html

Find the lines below and edit accordingly...

Login Header / Title text

< td >Webmail Access< /td >

Instructions to login / Custom Message

< td >< div id="AuthStatus" class="logintext" style="padding-left: 4px;" >Please provide your username and password.< /div >< /td >

Hide 'Mailserver; field from login page and set default to 'localhost'

Find...

< tr id="mailserver" >

And change to...

< tr id="mailserver" style="display:none;" >

Find...

< td align="left" >< input name="MailServer" type="text" class="logininput" id="MailServer">< /td >

And change to...

< td align="left" >< input name="MailServer" type="text" class="logininput" id="MailServer" value="localhost" >< /td >

Hide protocol from login page

Find...

< tr id="protocol" >

And change to...

< tr id="protocol" style="display:none;" >

Hide Language from login page

Find...

< tr >
< td > < /td >
< td colspan="2" align="right" >Language:< /td >

And change the < tr > tag to...

< tr style="display:none;" >

Please let me know if you have any suggestions to improve this tutorial... Enjoy!

Out of range trong linux

- step 1: log on root ---> init 3

- step 2: sax2 start

- step 3: reboot server one time

Loi khong start duoc graphic trong linux

- Ko the start dc graphic trong linux: Sax2 -m O=vesa

Crack root password for SLES

1. Boot server from the installation CD.
2. Then select any installation method or Rescue System.
3. At the first installation screen when selecting language, press ctrl-alt-f2 to open a virtual console.

Note: If you selected Rescue System, select your keyboard language and then a Rescue Login prompt should appear. Login as root.
4. Type
fdisk -l
to list the partitions. Locate the Linux root partition.
5. Type
mount /dev/sda4 /mnt
(replace sda4 with the device name for the Linux root partition identified in the previous step).
6. Run
mount -o bind /dev /mnt/dev
to make the device files available (this is needed for access to the urandom device which may be used by the passwd command below).
7. Enter
chroot /mnt
8. Now enter
passwd root
and reset the root password.
9. Type
exit
to leave the chroot environment.
10. Unmount the filesystem with
umount /mnt
11. Reboot the system.

Zentyal Error when disable interfaces automatically

- Disable Wan Failover

- Nang ti le % len 90%

Authentication Token Manipulation Error when Changing User Passwords in Zentyal Linux

Vo LDAP setting ----> Unmarked Enable PAM

HOWTO - OpenVPN + LDAP authentication in pfSense 1.2.2

http://forum.pfsense.org/index.php/topic,14946.0.html


Here's a quick and dirty guide on getting OpenVPN to authenticate against LDAP in pfSense 1.2.2. This may not work for every install, but it worked on a bare install for me. I suggest you have a functional OpenVPN server instance before making these changes:

On the pfsense box:

1. User pkg_add -r to install the following packages: openvpn-auth-ldap, gcc43, gmake, texinfo
- texinfo and gmake are not explicitly needed for this install, but some FreebSD 7.0 ports fail on installation without them

2. Under VPN -> OpenVPN -> Server, add plugin /usr/local/lib/openvpn-auth-ldap.so /usr/local/etc/auth-ldap.conf to the Custom Options field of the server instance which will be tying to LDAP.

3. Paste the openvpn-auth-ldap configuration template from http://code.google.com/p/openvpn-auth-ldap/wiki/Configuration into /usr/local/etc/opencpn-auth-ldap.conf (or whichever location you would like to use, just make sure that the line in your openvpn Custom Options from step 2 matches this location). Edit this configuration to your liking.

4. Symlink /usr/local/lib/gcc-4.3.0/libobjc.so.2 to /usr/local/lib/libobjc.so.3

5. Restart the OpenVPN service with killall -HUP openvpn, or by clicking Save on the WebGUI configuration page.

On clients

The only change that need to be made on connecting client configurations is the addition of the auth-user-pass directive. Upon connecting, the client will ask for a username and password which will be forwarded to the server for authentication, and the server will be checking those supplied credentials against the LDAP server specified in the openvpn-auth-ldap configuration file.

** NOTES **

If anyone has a clean way to solve the missing libobjc.so.3 library, throw it up here. If that gets solved, then this whole setup could be included as a viable option in the normal pfSense releases.