On Wed, 2006-05-24 at 11:40 +0200, Simon Matter wrote: > While trying to build updated rpms of 2.3.4 I found the lmtpproxyd is now > created as a hardlink to lmtpd. The same applies to pop3proxyd which is > linked to pop3d. In the past the rpm shipped without the hardlinked > pop3proxyd because it was not really used. My question is now what is the > correct way to handle those links. Is there a good reason to include them > in the package or are they just there for those using old config files? As of 2.3.3 proxy functionality was incorporated into daemons. As of 2.3.3 you don't need separate frontends and backends - same daemon can serve or proxy depend whether it has mailbox locally or not. M. -- Miroslaw "Psyborg" Jaworski GCS/IT d- s+:+ a C++$ UBI++++$ P+++$ L- E--- W++(+++)$ N++ o+ K- w-- O- M- V- PS+ PE++ Y+ PGP t 5? X+ R++ !tv b++(+++) DI++ D+ G e* h++ r+++ y? ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
