similar to: AMP and version numbers.

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

Hi team, I am beginning on R and I try to install Rmpi library and I have problems, I have installed LAM-MPI on Rocks; [rcnavarro at hpc-cip ~]$ laminfo LAM/MPI: 7.1.1 Prefix: /opt/lam/gnu Architecture: x86_64-unknown-linux-gnu Configured by: root Configured on: Wed Oct 19 18:12:25 EDT 2005 Configure host: rocks-156.sdsc.edu Memory

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

I have it running on my Windows 2000 mahcine using STI products and don't have much of a problem. I would guess that it might be something on the workstations instead of the AstTAPI. Also, might be a little faster, easier, cheaper to just upgrade your existing workstations? Just a thought. Feel free to contact me off list if you would like. Thanks, Dustin -----Original Message-----

Had I have been smart originally I would have done this to start. Some rudimentary documentation above and beyond Asttapi 0.10's poor documentation is available along with the download at http://www.kirkhamsystems.com/asttapi. Clint -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Kerry Garrison Sent:

Hi all We are planning to upgrade Dovecot from production version 1.0.10 to latest version 1.2.9 Users are using maildir style mailboxes with ~20 GB of messages on SLES10 server. Upgrade will be done by installing new server and then migrating mailboxes from old on new server. Since dovecot-uidlist file have new format and index files have changed in v1.1, what must be done to have new

I just read: Certain options to the Dial() statement require that Asterisk is in the media path, and consequently Asterisk will not let go of it: /t/, ''T", "h", "H", "w", "W" or "L" (with multiple arguments). Probably there are more. I had in my memory that "r", "R", "m" would also prevent a

I've been testing the debug version of AstTAPI, which worked for a few calls, then a bit later in the day (and ever since), when the call is hung up, the TAPI client doesn't get notified. Looking at the server logs, The TAPI message that is sent upon hangup, isn't being sent. exten => h,1,UserEvent(TAPI|TAPIEVENT: LINE_CALLSTATE LINECALLSTATE_IDLE) This is in the same context as

I've finished a patched version of asttapi that will work with asterisk 1.2. There were fundamental changes to the Asterisk Management interface between 1.0 and 1.2 that broke asttapi. I think my patched version will work on 1.0 and 1.2 branches, but I have no way of testing since I don't have a 1.0 install nor do I want one :). I'm looking for testers, if anyone's willing to

http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz.sig mbox users really should upgrade, because by sending a message with a huge header you could basically cause a DoS (this problem exists only with v1.2.x, not with v1.0 or v1.1). - mbox: Message header reading was unnecessarily slow. Fetching a huge header could have resulted in

http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz.sig mbox users really should upgrade, because by sending a message with a huge header you could basically cause a DoS (this problem exists only with v1.2.x, not with v1.0 or v1.1). - mbox: Message header reading was unnecessarily slow. Fetching a huge header could have resulted in

Yes, I have the exact same problem. :( -----Original Message----- From: Tomislav Vojvodic [mailto:tomislav@vox-mundi.net] Sent: Thursday, May 11, 2006 5:48 AM To: xytek@hotmail.com; 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: RE: [Asterisk-Users] Asterisk TAPI - Outlook click2dial Hey, thanks for your reply.. ;) I'm also using asttapi from website you posted

Hi, I evaluated asttapi, it fits our needs to dial with asterisk out of windows applications. But we are working with rdesktop on a windows 2000 terminal-server, 3 Users on 1 Machine Whenever a user Sets up asttapi via outlook the configuration changes for all users. For example when I enter sip/340 as my extension, the other users also have sip/340 in their configuration. Do you know a trick

We're encountering a problem with AstTAPI crashing on Windows 2000 Workstations. The program we're using is called Amicus Attorney, it uses a standard TAPI interface to be able to dial our clients, but on the 2 Windows 2000 workstations we've tried it on it has crashed, no errors or anything. When we select the Asterisk TAPI driver, the whole windows just closes/crashes w/ no apparent

Hi, I am 'playing' with asttapi which looks great on a first installation but I must be missing something regarding the source code because I haven't been able to work with it without problems. If you have played with this, you already know that the code to talk to Asterisk is placed in a file called asttapi.tsp which is in your windows/system32 folder. The thing here is, the

http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz.sig Most importantly mbox bugfixes. v1.1 should finally be as stable with mboxes as it was with v1.0. Hopefully we'll also soon have the first v1.2 beta release and the final v1.2.0 somewhat soon after that. - mbox: Several bugfixes. Fixes "next message unexpectedly lost"

http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz.sig Most importantly mbox bugfixes. v1.1 should finally be as stable with mboxes as it was with v1.0. Hopefully we'll also soon have the first v1.2 beta release and the final v1.2.0 somewhat soon after that. - mbox: Several bugfixes. Fixes "next message unexpectedly lost"

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior