similar to: v1.0.9 released

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'm running two boxes side by side, identical specs and setup but with differing dialplans. Both are on ast/zap/libpri versions 1.0.9. Both boxes share the same folder for voicemail, exported via NFS from another file server. Everything was working fine for an extended period of time, until just recently when someone rebooted Box A. Now when I dial an extension associated with a SIP

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

http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz.sig * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. - mbox: Dropped some of the physical size

http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz.sig * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. - mbox: Dropped some of the physical size

I know this is an old conversation, but I just thought I'd mention that I installed the version of Wine you mentioned, and it worked perfectly :) So yes, Asus Aspire One, Wine - Red Hat version, job done!

which one should I download?

No bug reports since rc4, so here it is. v0.99.10 2003-06-26 Timo Sirainen <tss at iki.fi> * Default PAM service name changed to "dovecot". This means that if you're using PAM, you most likely have to do mv /etc/pam.d/imap /etc/pam.d/dovecot If you wish to keep using imap, see doc/auth.txt. * ~/rawlog directory changed to ~/dovecot.rawlog + Faster and better

Hello, I am in the process of migrating a hosting setup from UW-IMAP to Dovecot. The protocols available to mail clients are IMAP and POP3 both before and after migration. I also wanted to change the mail storage format from MBOX to Maildir. However, at this point I hit a major snag with Dovecot and POP3 UIDL (unique identification listing for POP3 mailboxes). Several of the customers connecting

I've been having a problem with a crashing Dovecot the last couple of months where it crashes after a couple of weeks of uptime. Been a bit difficult to diagnose. Anyway, we're now running 1.0.9 on a Sun Fire T1000 running Solaris 10. Any good ideas on how to pin-point the problem? - Peter Here's the output from syslog when the last crash happened: May 14 11:46:50 ifm.liu.se

My dovecot server seems to randomly begin giving errors to pop3 users who try to fetch their email. Once this begins, they see no more new mail, though the mail is in cur. Running: dovecot-stable 20050501, Mac OS X 10.3.9 Log entries like this: May 2 19:35:18 caddy dovecot: pop3-login: Login: kim [24.22.16.169] May 2 19:35:18 caddy dovecot: POP3(kim): rename(/Users/kim/Maildir/

I have a few clients that have more than one user in the same mailbox. I have my setup using fctrl for mailbox and index locking. My mail is stored on a network file system (gluster) and my indexes are stored on the local drive. I have a few issues: - My users mailboxes have issues where messages will be mixed up (you go to open a message and it gets a different message) - messages will

We have a user that is using Thunderbird on Windows to read mail over IMAP and it works ok, except for downloading mail with "large" attachment.. When opening a mail with a attachment with a size of 14-15MB, TB downloads the attachment seemingly ok, but TB stops when reaching 99%. After TB has stopped, if the user tries to select another mail, TB just hangs and it has to be closed and

http://dovecot.org/releases/1.0/dovecot-1.0.8.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.8.tar.gz.sig + Authentication: Added "password_noscheme" field that can be used instead of "password". "password" treats "{prefix}" as a password scheme while "password_noscheme" treats it as part of the password itself. So

http://dovecot.org/releases/1.0/dovecot-1.0.8.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.8.tar.gz.sig + Authentication: Added "password_noscheme" field that can be used instead of "password". "password" treats "{prefix}" as a password scheme while "password_noscheme" treats it as part of the password itself. So

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock

Hi, We have just recently switched from Courier to Dovecot for both IMAAP and POP access for our shared hosting platform, and while the issues we have been seeing with Courier have gone away a new one has popped up. Unfortunately googling for an answer is difficult as it falls into the ownership and permissions category which people seem to have all the time. But in those cases it always

Hi all I am using * to trunk calls to a number of customers. This is proving unreliable - I set qualify=yes on all the trunks: [customer] type=friend host=customer.dyndns.org username=hewlett secret=******* context=int_calls trunk=yes nat=yes qualify=yes All Internet links are ADSL. I am running 1.0.9. I get a no. of symptoms: - every now and again i get a message that