similar to: 1.0 RC7 released

Displaying 20 results from an estimated 20000 matches similar to: "1.0 RC7 released"

2006 Oct 04
3
(mail_cache_add): assertion
Hi, I currently use rc2 on FreeBSD AMD64. Are there any news regarding this Bug: mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size)? I read that access to an 64bit-machine could help you. Feel free to contact me. Greetings from germany, Daniel -- GMX DSL-Flatrate 0,- Euro* - ?berall, wo DSL verf?gbar ist! NEU: Jetzt
2006 Aug 17
2
kqueue rewrite testing, try #3
So, apparently the original kqueue code was working fine after all, although it was much more complex than it really needed to be. So, this time there's a really simple and pretty kqueue implementation: http://dovecot.org/nightly/dovecot-latest.tar.gz Tested that it seems to work with FreeBSD. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc
2007 Jan 11
1
RC16 is a lot slower that RC7
I tried RC16 from RC7 and like other releases since RC7 it is significantly slower. I'm still trying to figure out why. But I have again switched back. Do new version take up a lot more ram perhaps? I'm running with a gig of ram, and I'm running a few other apps. It's not a fast computer, just an old 754 pin semptron. But the point is that RC7 runs a lot faster than RC16.
2006 Sep 28
2
which e-mail client can work with recent dovecot?
Hi, I'm trying to use dovecot-1.0.rc7. Before I've used dovecot-1.0 from nightly cvs build of August 08, 2006. It worked perfectly, on Linux 64-bit, you can see spec and patches at http://www.sisyphus.ru/srpm/dovecot/ When I tried to upgrade to rc7 and to recent nightly cvs builds with the same configuration and patches (provided necessary adaptations), it builds O.K, but can not move
2006 Sep 21
7
Big sites using Dovecot
Hi, Are there any big Dovecot sites (say 50,000-100,000) users on this list? What sort of hardware do you use. What sort of problems do you see? Many thanks, Jonathan.
2006 Aug 03
2
(no subject)
On Thu, August 3, 2006 15:28, David Jonas wrote: > On Thu, 2006-08-03 at 15:07 -0400, Scott Zahn wrote: >> Hey everyone, I'm trying version 1.0rc2, via the rpm at ATrpms. I'm running on CentOS >> 4.3 on an Opteron system. I have this running stably on a 32 bit system, but I'm >> crashing constantly on a 64 bit system. >> >> Here's what I'm
2006 Oct 24
3
"Real" users AND Virtual users
Dear all, How can I use dovecot for both "real" users and virtual users? I could configure dovecot for real users, by using these lines in /etc/dovecot.conf: default_mail_env = maildir:%h/Maildir auth default { passdb pam { } userdb passwd { } } To accept virtual users, I used these lines: default_mail_env = maildir:/usr/local/virtual/%u/ auth default { passdb sql {
2006 Oct 02
3
Dovecot as LDA
FreeBSD 6.1-RELEASE-p8 postfix-current-2.4.20060903,3 dovecot-1.0.r7 I am experiencing a problem with dovecot as an LDA. It will not deliver mail unless the mail directory is chmod'd to 1777. Below is an example of the log file output. The dovecot.log file had over a hundred entries similar to this: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1123.cd38cd4d82e1368f)
2006 Sep 06
1
Strange log entry???
Although everything appears to be working fine, I see the following entry in my log file each time someone logs on via the IMAPS service (all other services are disables: POP, IMAP, etc.): ========== Sep 6 02:57:00 mgw1 dovecot: Logins with login process UID xxxx (user someone at example.com) not permitted (see login_user in config file). ========== Any idea what this log entry means and is
2006 Oct 15
1
Dovecot rc9 error
Hi Am getting this error with Dovecot rc9 on a imap account. Oct 15 10:55:28 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:28 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:28 bajor dovecot:
2006 Sep 22
3
Rotating Dovecot's logfile
Any *BSD user on this list already having a means of rotating the dovecot logfile? What signal number do I need to send to the daemon to reopen its logfile? -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington
2006 Nov 02
3
v1.0 plans, rc11 tomorrow
As you can probably guess from my today's burst of activity, I'm no longer extremely busy. Actually it looks like for the next 3-4 weeks I don't have anything especially time consuming to do. So it's time to get Dovecot v1.0 released :) I've now read all the mails from this list again, and it looks like pretty much the only problems with rc10 was the mbox assert crash, which
2006 Aug 03
3
(no subject)
Hey everyone, I'm trying version 1.0rc2, via the rpm at ATrpms. I'm running on CentOS 4.3 on an Opteron system. I have this running stably on a 32 bit system, but I'm crashing constantly on a 64 bit system. Here's what I'm getting in my mail logs when I try to log in via IMAP: Aug 3 15:01:21 lisa dovecot: imap-login: Login: user=<scottz>, method=PLAIN,
2006 Oct 13
1
default_mail_env renaming
I was thinking about renaming default_mail_env to something that is more understandable. I'll keep it working for backwards compatibility anyway. How about: # Location for users' mailboxes. This is the same as the old default_mail_env # setting. The default is empty, which means that Dovecot tries to find the # mailboxes automatically. This won't work if the user doesn't have any
2005 Nov 19
1
Multiple authentication databases and storage locations
Hello Everyone, I am playing with the $subject matter using 1.0alpha4, and thanks to the archives, I lifted this one from Alexander Shikoff off and used it in my setup. auth default { mechanisms = plain user = root passdb pam { args = pop3 } passdb sql { args = /usr/local/dovecot/etc/dovecot-mysql.conf }
2006 May 08
1
kevent error (1.0.b7) - Is this a FreeBSD-only problem?
Hello everyone, The problem below has been reported, but I did not see any response! <cut> | | I'm also seeing this bug while testing the forthcoming 1.0.b7 FreeBSD | | port under 6.1-PRERELEASE: | | | | Info: imap-login: Login: user=<wibble>, method=PLAIN, rip=10.0.0.2, | | lip=10.0.0.2, TLS | | dovecot: Error: IMAP(isometry): Unrecognized event: kevent {.ident = | |
2006 Apr 10
2
Test version for production servers for shared folders
Dear List, Is the latest test version suitable for production systems? Our current servers use 0.99 on FC4 and we would like to add shared folders via the test version. Has anyone migrated this way before? Thanks, Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E ghenry at suretecsystems.com Open Source. Open
2007 Jun 03
3
Dovecot Authentication Problem - Help pls!
Hello List, This is dovecot 1.0.0 on FreeBSD 4.11-STABLE. I did not provide this information before:-) I am back again and I think I am edging closer to getting a solution. I have done some modifications and now dovecot gives me a different error message than before.... Here is what I have for the password_query and user_query password_query = SELECT popbox.cleartext AS password FROM
2007 Apr 21
6
Mixing MBOX and Maildir?
Is it possible to have some folders be mbox and some be maildir format? Why you might ask? Sometime for diagnostics I have the Exim MTA archive certain messages in MBOX format and then I want to copy them into an imao folder to look at them with Thunderbird. When I used MBOX all I had to do was copy the file into a folder and it worked. So what I'd like to do is have a folder with a
2006 Oct 12
2
1.0rc8: another problem? Possibly 64-bit index?
Yesterday I gave a status report about 10.rc8 in production, which mentioned a problem about "Login process died too early..." Timo suggested a patch for logging error messages. I've applied this. Others suggested increasing "login_max_processes_count". That was already way above our likely maximum, but I've doubled it anyway. Today, I've just repeated the