similar to: v1.0.5 released

Hello users, package *easycsv* version 1.0.5 is now available on CRAN < https://cran.r-project.org/package=usmap>. this update contains some upgrades and a new *choose_dir* function for Linux and Mac OSX users, for windows users, it's still implemented with utils::choose.dir. The full change log is available on Github: https://github.com/bogind/easycsv/releases/tag/v1.0.5 __

Hello users, package *easycsv* version 1.0.5 is now available on CRAN < https://cran.r-project.org/package=usmap>. this update contains some upgrades and a new *choose_dir* function for Linux and Mac OSX users, for windows users, it's still implemented with utils::choose.dir. The full change log is available on Github: https://github.com/bogind/easycsv/releases/tag/v1.0.5 __

I am running dovecot 0.99. Everything works great; however, now I am looking at several different tools to convert mbox to Maildir. It seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what they claim; however, when the messages are converted and they are stored in Maildir/cur, the email clients download these messages as new. This typically wouldn't be a problem;

http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig v1.0.8 and v1.0.9 were a bit bad releases. Hopefully one day I've managed to have written a proper test suite which can be run before doing any releases.. * Security hole with LDAP+auth cache: If base setting contained %variables they weren't included in auth cache key,

http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig v1.0.8 and v1.0.9 were a bit bad releases. Hopefully one day I've managed to have written a proper test suite which can be run before doing any releases.. * Security hole with LDAP+auth cache: If base setting contained %variables they weren't included in auth cache key,

Hi, I recently upgraded from stable v1.0.2 to v1.0.5. I'm seeing a bug when retransmitting my invite for proxy authentication. Essentially, when I retransmit the request with the proxy auth, the "From" number becomes the "To" number in the SIP message. Here is an example (with ambiguous numbers): Reliably Transmitting: INVITE sip:1234@10.0.0.2 SIP/2.0 Via: SIP/2.0/UDP

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked).

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked).

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.2/dovecot-1.2.16.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.16.tar.gz.sig Just some small fixes. - imap: Fixed SELECT QRESYNC not to crash on mailbox close if a lot of changes were being sent. - pop3: Fixed a potential hang - mbox: Creating new mailboxes should base permissions on mail root dir, not always use 0600. - auth: Disable auth caching

http://dovecot.org/releases/1.2/dovecot-1.2.16.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.16.tar.gz.sig Just some small fixes. - imap: Fixed SELECT QRESYNC not to crash on mailbox close if a lot of changes were being sent. - pop3: Fixed a potential hang - mbox: Creating new mailboxes should base permissions on mail root dir, not always use 0600. - auth: Disable auth caching

Heya, I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on Solaris 10 gcc 3.4.3. On both systems the compiling fails with: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2

Haven't seen a thread discussing forcing rebuilding of indexes / cache, so the question is, if these files in a users home directory were deleted... -rw------- 1 bb admin 80 May 17 15:05 dovecot-keywords -rw------- 1 bb admin 85449 Jul 2 06:15 dovecot-uidlist -rw------- 1 bb admin 6832 Jul 2 06:15 dovecot.index -rw------- 1 bb admin 752640 Jul 2 06:19

On Jan 20, 2008, at 12:15 PM, dovecot-request at dovecot.org wrote: > > Message: 5 > Date: Sun, 20 Jan 2008 15:48:09 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta14 released > To: dovecot at dovecot.org > Message-ID: <1200836889.12450.99.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >

Timo, Running v1.1.1 on OS X. What is dovecot trying to tell me here? Jun 24 15:03:50 G518X2 dovecot: IMAP(jjohnson): Sort IDs 4 broken in mailbox INBOX, reseting Thank you! G518X2:~ root# dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count

Read this in the dovecot sieve wiki: "The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver." Is "-d" still a valid deliver switch? When I configure postfix's main.cf like so... mailbox_command = /usr/local/libexec/dovecot/deliver -d -e ..it sqwaks with, "Jun 18 18:44:50

Hello, Just confirmed this on my end, because of the massive changes that have been made to callerID handling in asterisk 1.0.5 many of the features of the astGUIclient suite will not work on this new version. The latest stable version recommended is Asterisk 1.0.3. We will work on trying to find ways around the new callerID rules that the asterisk developers have put in place and hope to have

I will be deploying Dovecot on OS X shortly. I am looking for clarification on the limits imposed by OS X and sysctl [kern.maxproc]. I understand that it is defaulting to 532, but can be raised to 2500. I believe the OS uses around 100 or so, plus I will have other processes and shells at times. Does Dovecot use one process per user logged in? I find Apple Mail uses about 4 IMAP