There is now a bundle available [1] for Mail.app which makes it work with imap's IDLE function (where the server contacts the client when new mail arrives, rather than being polled by the client at whatever interval). Here is a bit of installation info [2]:
You may wish to enable IMAP_CHECK_ALL_FOLDERS if you filter new mail into folders other than your regular inbox. You can enable the IMAP_ENHANCEDIDLE option. Enhanced idle mode notifies all clients immediately when any changes to a folder occur. Ordinarily, a client may not be aware of a change to a folder until it is refreshed. You must install the fam package for it to work, as it relies on the File Access Monitor daemon
I assume that this is not already part of our courier setup... is anyone else interested?
File Access Monitor http://www.courier-mta.org/FAQ.html#fam
.
You also may or may not find this useful as well:
. http://osdir.com/ml/mail.qmail.qmr/2005-07/msg00147.html
.
Quoted from above "the problem is that famd works inside of portmapper, and portmapper
has historically been a massive source of security holes. i refuse to
use portmapper on any machine which is not protected by a hardware
firewll device of some kind, which obviously means i won't run it on
my own server."
.
BTW why doesn't <br> work??
18 Oct 2006
I assume that this is not already part of our courier setup... is anyone else interested?
Dave
[1] http://fivepoundsflax.blogspot.com/2006/10/imap-idle-plugin-version-104html
[2] http://edseek.com/~jasonb/articles/exim4_courier/courierimap.html
18 Oct 2006
http://popfile.sourceforge.net/cgi-bin/wiki.pl?ImapServers
29 Apr 2007
Any news on this? It appears Courier-IMAP needs FAM for this, has anyone succeeded in compiling FAM on OSX?
02 May 2007
Call me stupid but what is FAM ?
03 May 2007
File Access Monitor
http://www.courier-mta.org/FAQ.html#fam
.
You also may or may not find this useful as well:
.
http://osdir.com/ml/mail.qmail.qmr/2005-07/msg00147.html
.
Quoted from above "the problem is that famd works inside of portmapper, and portmapper
has historically been a massive source of security holes. i refuse to
use portmapper on any machine which is not protected by a hardware
firewll device of some kind, which obviously means i won't run it on
my own server."
.
BTW why doesn't <br> work??
06 May 2007
Thanks for the explanation on FAM, don't know why <br> doesn't work. I'll look into it...