- dovecot - dovecot.org

Re: [Dovecot] Squirrelmail Problem with 1.1 Beta 3
by Jeff Grossman 16 Oct '07

16 Oct '07

> > On Tue, 2007-10-16 at 11:47 -0700, Jeff Grossman wrote: >> I just installed 1.1 beta 3 and noticed a problem when sending an e-mail >> with Squirrelmail. When I hit send, I get the following error in my >> log: >>=20 >> Oct 16 11:35:54 apple dovecot: IMAP(jeff): Disconnected: EOF while >> appending bytes=3D1851/5926 > > Hmh. I did change things related to saving mails, but since it worked > with my stress testing and with Evolution, I thought I had fixed it. I > guess I'll need to test more. > That error went away after I deleted by index files. Once they were rebuilt I never saw the above error again. >> Oct 16 11:44:45 apple dovecot: IMAP(jeff): Cache file >> /home/jeff/.maildir/.Sent >> Items/dovecot.index.cache: Newly added field got lost unexpectedly > > I see this too, but since it happens only once I didn't bother fixing it > yet. OK Jeff

1 0

[Dovecot] namespace prefix issue with avelsieve and dovecot v1.1beta2
by Martin Konopka 16 Oct '07

16 Oct '07

Hi, I have installed dovecot v1.1.beta2 with the sieve plugin v.1.1.2. I have configured the following namespace: namespace: type: private separator: . prefix: INBOX. location: inbox: yes hidden: no list: yes When I create a rule which should move messages into the subfolder "Junk", Dovecot's deliver seems to ignore the namespace and creates a new folder .INBOX.Junk . I think I read somewhere that in Dovecot v1.1+ deliver supports namespaces? Or have I misconfigured something? Thank you! Martin dovecot -n output: # 1.1.beta2: /usr/local/etc/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/certs/server.crt ssl_key_file: /etc/ssl/certs/server.key verbose_ssl: yes login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: fs

2 1

[Dovecot] Error: net_connect(/var/run/dovecot/auth-master) failed: Resource temporarily unavailable
by Maykel Moya 16 Oct '07

16 Oct '07

I'm using deliver (1.0.5) with Postfix (2.1.6). I made a test for a few minutes in a moderated busy server. While most mails was delivered, a lot of them failed with this error: deliver(userfoo): Oct 15 09:58:31 Error: net_connect(/var/run/dovecot/auth-master) failed: Resource temporarily unavailable Sounds to me something like not enough auth-master to answer every concurrent deliver. Any hint? Regards, maykel PD: If there any other info I could give let me know.

2 2

[Dovecot] assertion failure when appending
by Johannes Berg 15 Oct '07

15 Oct '07

I get this assertion failure: file maildir-save.c: line 456 (maildir_save_finish): assertion failed: (ctx->seq != 0) once a while when I APPEND messages to a folder. My plugin doesn't touch the ctx, especially not the internal maildir one, but I have no idea where to start looking. Any hints? johannes

2 5

[Dovecot] (no subject)
by LDB 12 Oct '07

12 Oct '07

Version: 1.0.beta8 Is it possible to listen on just specific IP addresses as opposed a single IP or just all IPs on the same server? Thanks, LDB

3 2

[Dovecot] dovecot 1.1beta2 and dovecot-sieve 1.1.2 - crash in LDA
by Bernhard Schmidt 12 Oct '07

12 Oct '07

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] -> /usr/local/libexec/dovecot/deliver [0x470eac] -> /usr/local/libexec/dovecot/deliver [0x47929b] -> /usr/local/libexec/dovecot/deliver [0x46f3e3] -> /usr/local/libexec/dovecot/deliver(buffer_write+0x9d) [0x46f70d] -> /usr/local/libexec/dovecot/deliver [0x469aaf] -> /usr/local/libexec/dovecot/deliver(message_header_decode+0x104) [0x469c14] -> /usr/local/libexec/dovecot/deliver(message_header_decode_utf8+0x4b) [0x469d4b] -> /usr/local/libexec/dovecot/deliver [0x43f3eb] -> /usr/local /libexec/dovecot/deliver(index_mail_get_headers+0x42) [0x4401c2] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df67d87] -> /usr/local/lib /dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df716e8] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x395) [0x2b662df72665] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xfa) [0x2b662df77daa] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x318) [0x2b662df689b8] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df66d96] -> /usr/local/libexec/dovecot/deliver(main+0xe74) [0x417d24] -> /lib/libc.so.6(__libc_start_main+0xf4) [0x2b662da15b44] -> /usr/local/libexec/dovecot/deliver [0x416079] All other mails work fine, so there is probably something corner case here. Timo, I'll send you the mail in private. Regards, Bernhard Schmidt

1 1

[Dovecot] Logging client commands (patch)
by Zach Bagnall 12 Oct '07

12 Oct '07

This might be useful to someone so I'll throw it out there. Patch against 1.0.5 adds support for two new configuration params: pop3_debug_client_commands = TOP, RETR, DELE imap_debug_client_commands = FETCH, DELETE Obviously add in whichever ones you're interested in, or none, or comment them out completely. It'll log the appropriate events: Oct 12 18:30:18 kea dovecot: IMAP(zach): Client command: FETCH The parameters are included for POP3 events. Wasn't sure quite how to do the same for IMAP and for my purposes it's not too important so imap command parameters aren't logged. Running smoothly here with a few dozen IMAP and POP3 users. Not suggesting this gets added to the codebase - I just needed it to help debug some other IMAP software and thought it might be useful. Zach.

1 0

[Dovecot] UIDL format for old UW pop3
by Oliver Hookins 11 Oct '07

11 Oct '07

Hi, we're trying to migrate from UW imap 2001a-10, which doesn't seem to use the UIDL format documented in the wiki. It seems to use a 16 character long MD5 hash of something. I've tried configuring Dovecot to do the same but the value comes out differently. The main thing that I can see is getting in the way is that the UIDL format is not documented sufficiently. There is no description of using numbers to restrict the length of the output, and no documentation of special features like X or M. Can someone shed some light on these? -- Regards, Oliver

2 1

[Dovecot] Quota Display with Horde / IMP ( WebMail Client )
by edwardspl＠ita.org.mo 11 Oct '07

11 Oct '07

Dear All, For the Dovecot.conf : protocol imap { mail_plugins = quota imap_quota mail_plugin_dir = /usr/lib/dovecot/imap } plugin { quota = maildir } For /var/spool/mail : -rw------- 1 root root 7168 Sep 24 23:02 aquota.group -rw------- 1 root root 8192 Sep 24 18:05 aquota.user -rw------- 1 edward mail 301709 Sep 24 23:27 edward But the Quota display is un-limited status... So, what mistake about the config ? Mine is FC6 System ! Thanks ! Edward.

3 2

[Dovecot] GSSAPI Cross-Realm Patch
by Zachary Kotlarek 11 Oct '07

11 Oct '07

I've written a GSSAPI cross-realm auth patch for people not lucky enough to have the __gss_userok function, though it should apply pretty cleanly with that patch in place as well. The patch is available at: http://zinux.cynicbytrade.com/svn/servers/dovecot/cross-realm.diff.bz2 It works for me on MIT-kerb, and I tested compilation against heimdal, but I don't have a cross-realm setup to test functionality under heimdal (though I also have no reason to think it wouldn't work). Since neither MIT nor heimdal provide a gss_userok() function, I used the krb5_userok() function. So if you're using a mechanism other than krb5 this won't work. But it's the same thing that OpenSSH and the apps distributed with heimdal do, so it seemed relatively safe. I also choose to append the krb5_userok() check rather than replace the gss_compare_name() check -- that way same-realm auth works for non-krb5 mechanisms, and my new code doesn't get called unless the same-realm check fails. If you don't care about other mechanisms it would be faster to bypass the gss_compare_name() check entirely. If this is something you'd like to mainline I'd be happy to standardize the coding style -- just point me to a style definition document. And if it doesn't hit the mainline I expect to maintain it for the foreseeable future, with updates at the same URL. Zach

1 0