Hi
I successfully installed cyrus + postfix on my centos 4.2 box. When trying to make imap idle working, I noticed that there is no idled executable in the rpm.
Do I have to recompile cyrus from source to get idled working?
Thanks
Am Fr, den 30.12.2005 schrieb sophana um 0:32:
I successfully installed cyrus + postfix on my centos 4.2 box. When trying to make imap idle working, I noticed that there is no idled executable in the rpm.
Do I have to recompile cyrus from source to get idled working?
Yes.
Alexander
Ok thanks. I did bring the source with apt-get source cyrus-imapd Then I rebuilt the rpmsource with rpmbuild -ba --define='IDLED 1' --define='SEEN_DB skiplist' cyrus-imapd.spec
Now Idled works just fine. My emails now appear instantly.
But my question is: Why idled is disabled by default? It seems to be working great. Does anybody knows if there are drawbacks in using idled?
Thanks again
Alexander Dalloz wrote:
Am Fr, den 30.12.2005 schrieb sophana um 0:32:
I successfully installed cyrus + postfix on my centos 4.2 box. When trying to make imap idle working, I noticed that there is no idled executable in the rpm.
Do I have to recompile cyrus from source to get idled working?
Yes.
Alexander
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, 2005-12-30 at 10:19 +0100, sophana wrote:
Ok thanks. I did bring the source with apt-get source cyrus-imapd Then I rebuilt the rpmsource with rpmbuild -ba --define='IDLED 1' --define='SEEN_DB skiplist' cyrus-imapd.spec
Now Idled works just fine. My emails now appear instantly.
But my question is: Why idled is disabled by default? It seems to be working great.
In CentOS, the why question is easy :)
We build it exactly as is comes from the upstream provider so as to maintain the packages like they are in the upstream product ... even if those are not the best options.
Does anybody knows if there are drawbacks in using idled?
That I am not sure about ... taking a look, I found this in the change log:
----------------------------------- Mon Nov 25 13:00:00 2002 Simon Matter - changed default build option for IDLED to off - included some useful info in README.*
Thu Nov 21 13:00:00 2002 Simon Matter - added build time option for IDLED, thank you Roland Pope -----------------------------------
SO ... that decision is upstream of RedHat as well (as to IDLED being not enabled in the default build). I can't find any reason why it is that way, as far as negative issues are concerned.
Johnny Hughes wrote:
On Fri, 2005-12-30 at 10:19 +0100, sophana wrote:
That I am not sure about ... taking a look, I found this in the change log:
Mon Nov 25 13:00:00 2002 Simon Matter
- changed default build option for IDLED to off
- included some useful info in README.*
Thu Nov 21 13:00:00 2002 Simon Matter
- added build time option for IDLED, thank you Roland Pope
SO ... that decision is upstream of RedHat as well (as to IDLED being not enabled in the default build). I can't find any reason why it is that way, as far as negative issues are concerned.
I googled a bit and found that it has been rechanged in jan 2005 to ON in fedora core. It seems that the rhel4 cyrus package does only have one update since mid 2004. I will try the latest source rpm from invoca.ch. It seems that it has interesting changes... http://www.invoca.ch/pub/packages/cyrus-imapd/cyrus-imapd-2.2.12-15.src.rpm
* Thu Jan 6 2005 Simon Matter ... - changed default build option for IDLED to on
On Fri, 2005-12-30 at 06:23 -0600, Johnny Hughes wrote:
On Fri, 2005-12-30 at 10:19 +0100, sophana wrote:
Ok thanks. I did bring the source with apt-get source cyrus-imapd Then I rebuilt the rpmsource with rpmbuild -ba --define='IDLED 1' --define='SEEN_DB skiplist' cyrus-imapd.spec
Now Idled works just fine. My emails now appear instantly.
But my question is: Why idled is disabled by default? It seems to be working great.
In CentOS, the why question is easy :)
We build it exactly as is comes from the upstream provider so as to maintain the packages like they are in the upstream product ... even if those are not the best options.
Does anybody knows if there are drawbacks in using idled?
That I am not sure about ... taking a look, I found this in the change log:
Mon Nov 25 13:00:00 2002 Simon Matter
- changed default build option for IDLED to off
- included some useful info in README.*
Thu Nov 21 13:00:00 2002 Simon Matter
- added build time option for IDLED, thank you Roland Pope
SO ... that decision is upstream of RedHat as well (as to IDLED being not enabled in the default build). I can't find any reason why it is that way, as far as negative issues are concerned.
---- cyrus-imapd is one of the few packages that I go out of band to get and use Simon's SRPM's directly from Simon (available from here) http://www.invoca.ch/pub/packages/cyrus-imapd/
because he incorporates a much wider array of the 'auto' patches such as autosieve (which I find especially useful) - patches are described here... http://email.uoa.gr/projects/cyrus/
and yes, I knew that idled was working in his rpms. Apparently at the time that Red Hat embraced his rpms, different decisions reigned.
Craig
Quoting sophana sophana@zizi.ath.cx:
Ok thanks. I did bring the source with apt-get source cyrus-imapd Then I rebuilt the rpmsource with rpmbuild -ba --define='IDLED 1' --define='SEEN_DB skiplist' cyrus-imapd.spec
Now Idled works just fine. My emails now appear instantly.
But my question is: Why idled is disabled by default? It seems to be working great. Does anybody knows if there are drawbacks in using idled?
Hmmm... Recently there was this email on Cyrus Announce mailing list:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.cyrus-announce&am...
It's announcement for version 2.3.1. Quoting: "IDLE now works with idled". So I guess there might have been some problems with it in previous version(s), if it "now works" in the most recent version. I guess cyrus-info mailing list would be the best place to inquire what was wrong with idled in previous versions (if there was something wrong with it in 2.2.x).
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.