similar to: Discussion of new sending protocol proposal for IMAP

Hello Dovecot community, Below please find a patch that adds support to dovecot-1.2.11 for: - RFC 4467 - IMAP URLAUTH Extension - RFC 4468 - Submission BURL - RFC 4469 - IMAP CATENATE Extension URLAUTH URLAUTH is added as a plugin so it can be disabled to satisfy site security requirements. Each user's URLAUTH keys for all mailboxes are stored in a file named

v2.2 hg now has support for NOTIFY extension. The only thing missing is support for SubscriptionChange events. Now would be a good time for IMAP clients to start implementing and testing it. :) I remember K9 developers at least said they were just waiting for Dovecot to support it first. v2.2 implements some other extensions also: BINARY, CATENATE and MOVE. Stephan has also implemented URLAUTH

Small patch to correct spelling of lemonade. Should ask Sean if he really wanted it to be lemonaid. If not, here''s the patch. On another note... This sample works! Kudos. It is odd that the textbox doesn''t scroll. I suppose I may patch that, too. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

Hello list. I'm planning a new mail servers for our company's customers to replace the oldish Courier-IMAP based one, we already started to deploy some mail accounts on a dovecot-2.0 server as an early test. I'd like to implement the new system with dovecot-2 (I'll probably go straight to dovecot-2.1.x) and I'd like to get it right from the beginning so I'm here asking for

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions

The man page says: --password-file This option allows you to provide a password in a file for accessing an rsync daemon. The file must not be world readable. It should contain just the password as a single line. The trouble with this is that the file then shows up like this in an ls: 2 -rw------- 1 root wheel 9 Jan 24 2007

Hello, I had a similar problem with login scripts. I tracked the problem down to any entries in the login script which change directory. Taking 'cd' out of the login script solved the problem. Looking at M$ technet confirmed that this was a problem with Windows. I hope this helps. Regards, Dave -----Original Message----- From: Werner Maes [mailto:werner.maes@cc.kuleuven.ac.be] Sent: 02

I agree with that fact the same questions get posted, but that problem is compounded by the fact the archives are not really searchable. If the were as lease some users would search. The archives need to be fully indexed. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of steve szmidt Sent: Monday, June 27, 2005

Hello, Can anyone give me arguments that could convince someone to choose for Samba for file and print sharing instead of setting up a NT-server? Performance ? Stability ? Benchmarks ? Tests that someone has done? Things like: "It's free" or "You don't need a powerful machine" are irrelevant to our administrators. I'm looking for answers on questions like:

At 15:58 00-04-17, you wrote: >Date: Mon, 17 Apr 2000 14:45:07 +0200 >From: werner maes <werner.maes@cc.kuleuven.ac.be> >To: samba@samba.org >Subject: SMBD-error: important?? >Message-ID: <38FB0753.B00F2E49@cc.kuleuven.ac.be> >MIME-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Hello, > >When I

add to each share writeable = yes or read-only = no This Helps! Rauno -----Original Message----- From: werner maes [mailto:werner.maes@cc.kuleuven.ac.be] Sent: 11. mai 2004. a. 16:19 To: samba@samba.org Subject: [Samba] BUG: Vfs audit module & samba 3.0.4 ==> share unaccessible Hello Maybe there's a bug in samba-3.0.4. The following configuration does NO longer work. It did

>Message: 14 >Date: Fri, 16 Dec 2005 12:34:38 +0100 >From: Michael Gasch <gasch@eva.mpg.de> >Subject: Re: [Samba] The single WINS problem: question >To: werner maes <werner.maes@cc.kuleuven.be> >Cc: samba@lists.samba.org >Message-ID: <43A2A64E.9030301@eva.mpg.de> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >do you have multiple

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to

hello I tried to compile samba on Redhat AS5U5 but it fails with this message: Install: cannot stat `source3/bin/umount.cifs': No such file or directory. Any solution? kind regards werner maes

This (see below) is what I found in the Samba Introduction Document. Can anyone tell me where I can find the Ziff-Davis benchmark tests? Thanks a lot, Werner Maes KULeuven "The Present Samba 2.0 was released in January 1999. One of the most significant and cool features of the 2.0 release was improved speed. Ziff-Davis Publishing used their Netbench software to benchmark Samba 2.0 on

Hello, I've been trying to add a NT machine to a samba controlled domain following the instructions listed in the HOWTO collection. When I try to add the machine, I get following error: "Unable to add or change accounts on the domain. The account information entered does not grant sufficient privilege to create or change account". I'm logged in as administrator at the NT

The subject says it all. I'm using rocks cluster software to startup a small blade cluster in my lab. The blades I have redboot installed on them. I am able to boot any client that has pxeboot capability using my setup, except for these blades. My thoughs were using redboot commands to do the following: 1. load -v -r -b 0x8000000 -h 10.1.1.1 pxelinux.0 2. start This however caused my

Hello, I think (in fact I'm quite sure) I have found the following bug in Swat. In my configuration I use the global option "invalid users=@class". When I set this option using SWAT, all works fine after "commit changes". Users who belong to the "class" group cannot access the server. But when I erase this value using SWAT and do "commit changes",

If its too hard for them to setup the pop3 catch all, we can probably put some mapping in place to smtp froward mail to their server. This is more complex on our part so would prefer not to do it that way, but its an option and will require not setup on their part other than make sure their server does not accept mail for anyone other than our server. dovecot-request@dovecot.org wrote: >

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and