similar to: Crash of 1.0rc7

Hi, I'm having a really really strange problem. After upgrading from 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect to the services using IPv4 anymore. dovecot happily binds to the IPv6 wildcard socket which should accept IPv4 connections as well. root at vs02:~# netstat -lnp --tcp | grep dovecot tcp6 0 0 :::993 :::*

Hi, I've upgraded to dovecot 1.1beta2 and the latest dovecot-sieve release yesterday and have one single mail that cannot be delivered repeatedly. Log (reformatted): Oct 12 15:19:19 vs02 deliver(bernilrz): pool_data_stack_realloc(): stack frame changed Oct 12 15:19:19 vs02 deliver(bernilrz): Raw backtrace: /usr/local/libexec/dovecot/deliver(i_syslog_panic_handler+0x1e) [0x47117e] ->

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

Hi, I'm trying to use the new IDLE support in Mail.app on Mac OS 10.5, and it works sort of, but it seems to miss some notifications. My guess is the IDLE support in Mail.app is implemented such that it sets up a connection for IDLE notifications and then checks the mail via another connection, and because of that the "IDLE-connection" gets disconnected for inactivity after

Hi, I just installed dovecot 1.0 beta 7 and I have these errors: May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=::ffff:xx.xx.xx.6, lip=::ffff:xx.xx.xx.1 May 5 09:21:27 mail dovecot: POP3(user2): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user3>, method=PLAIN,

I just launched a new mailserver that is using dovecot. My previous mailserver used courier-mail. I am expecting better things with this new server, but I was use to some login information in logwatch that I am not seeing now. For example I would get: [IMAPd] Logout stats: ==================== User | Logouts | Downloaded | Mbox Size

I have a Samba PDC with LDAP (samba version 3.0.21c with Openldap 2.3.19). where i have all the users. I have configured sendmail on another system with dovecot as IMAP and POP3 server. I wanted to enable user authentication from LDAP server which is on samba PDC. So configured /etc/dovecot.conf ################################################################ protocols = pop3 imap imap_listen

I'm using logcheck for log reporting on Debian Etch, and am currently getting a lot of log entries from Syslog falling through the standard logcheck regex filters. I'm running Dovecot 1.0beta8. The filters follow: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ (imap|pop3)-login: Login: [.[:alnum:]@-]+ \[(::ffff:)?[:0-9a-f.]+\]$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ (dovecot: )?(imap|pop3)-login:

First off, sorry if this has been asked before - I have looked, honest. Is it possible to get dovecot to authenticate users against active directory, treating the AD as a plain ldap server? I have this working with cyrus saslauthd. Currentlt I get a long delay (30 seconds or so) then * BYE Disconnected for inactivity. All I get in the maillog is imap-login: Disconnected: Inactivity

Fellow dove-users, Just a note to say that Dovecot 1.0rc7 is working very well indeed, supplying SPOP3, regular POP3, and TLS/SASL services on FreeBSD 6.1 Production, in conjunction with Postfix 2.3.2. I have authentication methods PAM and passwd in use. Keep the peace(es). -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies --

To avoid having some stupid new problems with 1.0rc7, could you test this night's snapshot once it arrives in a couple of hours: http://dovecot.org/nightly/dovecot-20060811.tar.gz Especially people who had compiling problems with 1.0rc6. Also everyone who are still experiencing hangs could you try the suggestions in this mail and tell me what happened:

Hello, Have been to dovecot website but could not find information on what I need to check before I upgrade from the current 1.0rc7 which I am using on a FreeBSD 6.2 system. Will the old conf (virtual users, no ssl) file work with upgraded dovecot? Many thanks! -- Zbigniew Szalbot

Dear Tim Schafer, Take a look at my sample dovecot-ldap.conf hosts = localhost dn = cn=root,dc=ceylonlinux,dc=com dnpass = secret ldap_version = 3 base = dc=ceylonlinux,dc=com deref = never scope = subtree user_attrs = mail,homeDirectory=mailMessageStore,uidNumber=1003,gidNumber=1003 user_filter = (&(objectClass=user)(mail=%u)) pass_attrs = mail=user,userPassword=password pass_filter =

Hi, Folks, I recently migrated from courier-imapd to dovecot when I migrated a machine from rh9 to fc5. I managed to hit a snag with the 1.0b8 version of dovecot that's currently in fc5. With AppleMail 1.3 I was seeing most of my incoming mail go missing. To make a long story short, AppleMail was applying mail filters inappropriately (walking right past a 'stop processing'

I did a few more changes and it seems to be working with FreeBSD. I didn't before realize that event filters weren't bitmasks so that broke things. Anyway, a bit more "real world testing" would be better than my test program and telnet localhost -tests :) I'll release 1.0rc7 in any case today before I go to sleep (so, max. 6 hours or so).

I am configuring dovecot 1.0rc7 to authenticate users (system users) in /etc/passwd. Is it possible to use a different auth mechanism, other than "plain", when the encrypted password is in /etc/master.passwd (BSD style)? -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php --

Hi, I just upgraded a 0.99 installation to 1.0rc7 (going from mbox to maildir along the way, but that's another story), and I'm seeing a rather fast fd quick; I already had to restart dovecot once, after a few hours. What is leaked are pipes, left open on the master dovecot process while the other end is long gone. I can't tell right now if it happens for every single login process

Thinking that the issue with libssl is an artifact of the unstable branch, I've just tried, a reproduced the problem with, v10.rc7. Thank you. Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://dovecot.org/pipermail/dovecot/attachments/20060818/bf07a60b/attachment-0002.html>

Today I switched one of our servers from Courier (deployed 3-4y ago) to DCrc7. Everything seemed very nice (system load dropped significantly). Unfortunately after some time and ~8000 pop3-logins the main DC loop just quit without _any_ notice. Some pop3-login childs still showed up in the processlist, but the main listener on port 110 was gone. The above described scenario has been observed 2

Hello: Not sure if this is 1.0rc7 specific or not, but everything was working great until Dovecot died completely with this information in the log: Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.11 Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.4 Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: