--- Jon Angliss <jon@xxxxxxxxxxxxxxxx> wrote: - snip - > SquirrelMail doesn't "start", it's a web application. You need to > check > up on the configuration of apache to find out if it loaded properly. > ~From what I remember, debian/ubuntu both install an alias in the > apache > configuration directories that make http://yourserver/squirrelmail > available, which might mean you need to restart apache. In fact, the > details on getting that portion running are on the link you provided. > If you're having issues there, you should check your web server log > files for any errors. Hi Jon, I have to provide more info on the network here. Network connection:- Server A (a working LAMP server) - local IP 192.168.0.10 Server B (a LAMP server under testing) - local IP 192.168.0.52 Gateway - 192.168.0.1 No port is forwarded to Server B. Both servers have SquirrelMail running. After stopping Apache2 on Server A, SquirrelMail on Server B can be started on browser of Server A with; https://192.168.0.52/squirrelmail then it prompts to; https://192.168.0.52/squirrelmail/src/login.php But I can't login to any user. $ tail /var/log/mail.log May 26 22:36:07 lampserver cyrus/master[3881]: process 4750 exited, status 0 May 26 22:37:32 lampserver cyrus/master[4753]: about to exec /usr/lib/cyrus/bin/imapd May 26 22:37:32 lampserver cyrus/imap[4753]: executed May 26 22:37:32 lampserver cyrus/imap[4753]: accepted connection May 26 22:37:32 lampserver cyrus/imap[4753]: badlogin: localhost [127.0.0.1] plaintext root SASL(-13): user not found: checkpass failed May 26 22:37:50 lampserver cyrus/imap[4753]: accepted connection May 26 22:37:50 lampserver cyrus/imap[4753]: badlogin: localhost [127.0.0.1] plaintext satimis SASL(-13): user not found: checkpass failed May 26 22:38:15 lampserver cyrus/imap[4753]: accepted connection May 26 22:38:15 lampserver cyrus/imap[4753]: badlogin: localhost [127.0.0.1] plaintext root SASL(-13): user not found: checkpass failed May 26 22:39:18 lampserver cyrus/master[3881]: process 4753 exited, status 0 * end * $ tail /var/log/auth.log May 26 21:30:56 lampserver sshd[4672]: Accepted password for satimis from 192.168.0.10 port 33358 ssh2 May 26 21:30:56 lampserver sshd[4674]: (pam_unix) session opened for user satimis by (uid=0) May 26 21:39:01 lampserver CRON[4695]: (pam_unix) session opened for user root by (uid=0) May 26 21:39:01 lampserver CRON[4695]: (pam_unix) session closed for user root May 26 22:09:01 lampserver CRON[4706]: (pam_unix) session opened for user root by (uid=0) May 26 22:09:01 lampserver CRON[4706]: (pam_unix) session closed for user root May 26 22:17:01 lampserver CRON[4716]: (pam_unix) session opened for user root by (uid=0) May 26 22:17:01 lampserver CRON[4716]: (pam_unix) session closed for user root May 26 22:39:01 lampserver CRON[4755]: (pam_unix) session opened for user root by (uid=0) May 26 22:39:01 lampserver CRON[4755]: (pam_unix) session closed for user root * end * I have been googling around and can't figure out a solution. Please shed me some light. TIA > | On your URL it says it need IMAP server. > > It says you need access to an IMAP server. It doesn't necessarily > say > you have to be the one running it. For example, your ISP might run > one, > or you may want to access one provided by a mail provider (gmail for > example). Noted with thanks. A further thought can I leave out installing IMAP packages? > | I don't have it running on > | this mail server under testing. I'm prepared to install following > | packages; > | > | courier-base - Courier Mail Server - Base system > | courier-imap - Courier Mail Server - IMAP server > | courier-imap-ssl - Courier Mail Server - IMAP over SSL > > Picking your imap server entirely depends on what you want to do with > it. Small scale systems would work okay with uw-imap, then you have > courier/dovecot, and cyrus, for bigger setups. I personally have > used > all of them, but I prefer courier/dovecot on most setups, and I'm > shifting my servers to dovecot now. Noted with thanks. > You'll also need some method of sending mail out, and receiving mail > as > well. This is usually handled by something like Sendmail, Postfix, > or > Exim. My personal preference here is postfix. I've not touched exim > before, and from past experience sendmail can be complex to tweak. > But > again, as I said above, you only need access to a server, you don't > necessarily need to be running it. Server B is also working. I can send and receive mails with port 25 forwarded to its local IP address 192.168.0.52 > What are you trying to achieve? Are you planning on hosting your own > mail server(s)? Do you want to handle the mail coming into and out of > a > domain? Server A is LAMP server working properly. Its users can send/receive mails either as webmail on SM or on Evolution, the mail client. I build Server B for testing SugarCRM. Actually I can skip installing SM. The building of Server B is nearly completed except iptables and some minor setup. My target installing SM is to test "One Time Password" which is a side test, additional to testing SugarCRM, just added to the main test later. B.R. Stephen L Send instant messages to your online friends http://uk.messenger.yahoo.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users