From: Alexandros V. <av...@no...> - 2005-08-06 22:01:49
|
I'm following up on Squirrelmail-plugins, if you wouldn't mind. Original post: Jason Self wrote: "My plan is to implement the plugin on a machine running Mac OS X Server version 10.4. Sieve is somewhat broken in 10.4. http://www.afp548.com/article.php?story=2005051020271724 Now, I don't expect you to fix the problem, of course... That's something different entirely. A work around has been discussed, which seems to work. http://www.afp548.com/comment.php?mode=display&order=ASC&pid=1711 " <snip> Paul Lesneiwski wrote: > I can't really give you an estimate of the difficulty of this "fix" until > I look at the plugin and understand just how different I'd have to make > things, but I'd rather give Alexandros the chance to respond first, since > he will be in a much better position to offer a fix or a workaround (much > more quickly). He'll also probably have some opinions about the problem > and the workaround. I've cc'd him here. >From what I understand, in OSX the Sieve functionality is there, because underneath it all there is a Cyrus, but there is no timsieved, daemon which listens for upload/download/management of scripts. So the OSX people do these hacks/workarounds and in the end find out it works perfectly. I've had similar requests about Exim filters, which also do not have transport mechanism. You could probably give me some time to design wrappers and abstraction layers for different backends - MANAGESIEVE (timsieved, existing), fopen()/fwrite(), FTP or whatever. When I do, I will let the OSX people hack their own backend. I'll be away for two days, and when I come back I will try to sort this out. BTW, I had this correspondence from before about OSX. They provide information about OSX quirks. From: Chris Pepper To: Alexandros Vellis Subject: avelsieve on Mac OS X (Tiger) Server Alexandros, I've been unable to use avelsieve under Mac OS X 10.4.1 Server. <http://www.afp548.com/article.php?story=2005051020271724&query=sieve> implies this is because Apple's timsieved doesn't advertise the authentications it supports. SquirrelMail's configtest.php confirms what I've set in Server Admin, which is "AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5", so I think if avelsieve supported a "force authentication" option we might be okay, until Apple fixes it on their end. Interestingly, I see avelsieve.mo & avelsieve.po files in Apple's SquirrelMail installation, but not avelsieve itself. They also have a bunch of sieve man pages without the described programs. Hopefully they'll fix this soon. <snip> >pepper@www:~$ telnet localhost sieve >Trying 127.0.0.1... >Connected to localhost. >Escape character is '^]'. >"IMPLEMENTATION" "Cyrus timsieved v2.2.12-OS X 10.4.0" >" >"SIEVE" "fileinto reject envelope vacation imapflags notify >subaddress relational comparator-i;ascii-numeric regex" >"STARTTLS" >OK >CAPABILITY >"IMPLEMENTATION" "Cyrus timsieved v2.2.12-OS X 10.4.0" >" >"SIEVE" "fileinto reject envelope vacation imapflags notify >subaddress relational comparator-i;ascii-numeric regex" >"STARTTLS" >OK >LOGOUT >OK "Logout Complete" >Connection closed by foreign host. |