[rhn-users] imap question(s)

[Riley, Liz (ACHE)]

You should have some errors in your logfiles showing connection. Have
you configured xinetd to be listening for imap? And also checked that
hosts.allow is permitting your box on the interface its using (eg either
127.0.0.1 or <IP>)

-----Original Message-----
From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com]
On Behalf Of dlederer at hilltowncharter.org
Sent: 07 March 2006 14:47
To: Red Hat Network Users List
Subject: [rhn-users] imap question(s)

Hi,
part 1) Im trying to setup squirrelmail, and when I try to connect I get
a "error connecting to localhost, connection refused".
I assume this is a newbie related problem, Ive never configured any of
this stuff before.
Ive read so many help pages abnd tutorials, my head is spinning..


part2) Im migrating from a debian version a friend set up for me.
Can I move user home directories over to avoid losing mail, or do I have
to have everybody pop thier mail
1st before I crank up squirrel mail. Currently we're using horde/imp if
that makes a difference.

thanks for any help!!
Dan Lederer

_______________________________________________
rhn-users mailing list
rhn-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-users

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************