hi,

I did not installed with yum from epel. I downloaded, unpacked, and manual install. Thats should work fine. I agree with creating own rpm packages.

Madal

> Date: Tue, 19 Apr 2011 12:43:14 +0200
> From: peter.schober@univie.ac.at
> To: squirrelmail-imapproxy@lists.sourceforge.net
> Subject: Re: [SM-imapproxy] imapproxy configuration
>
> * madal 30 <madal30@hotmail.com> [2011-04-19 00:17]:
> > Fist time poster here. Just needed bit of more info with imapprxy
> > server. I just installed the imapproxy on my redhat 6 by following
> > README doc .. configure, make and make install. That all worked.
>
> Jfyi, since you're using an RPM-based distribution: Instead of
> `configure && make && make install` you could also simply
> rebuild the current stable release (1.2.7) via
> `rpmbuild -tb squirrelmail-imap_proxy-1.2.7.tar.gz`
> or from an SVN working copy, if you want the very lates code.
> You'll get current software this way, (EPEL only has imapproxy
> 1.2.6 and also has no package for RHEL6 yet) and integrates cleanly
> with your package management system (e.g. for easy upgrades).
> -peter
>
> ------------------------------------------------------------------------------
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> -----
> squirrelmail-imapproxy mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squirrelmail-imapproxy@lists.sourceforge.net
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy