[Dovecot] Why : dovecot_destination_recipient_limit = 1 ?
Hi all, I'm trying to activate sieve. In all tutorials I have seen I need to set dovecot_destination_recipient_limit = 1 in Postfix's main.cf. Can anyone explain why ? I like to know because when I set this and the dovecot transport in Postfix, I'm having problems when aliasses are used that map to different recipients, i.e. i...@... results in us...@..., us...@..., etc. The problems are an error from Postfix : Oct 30 09:25:19 lace3 postfix/pipe[19729]: 8A77E2D5B5B: to=some.b...@some.where.org, relay=dovecot, delay=2390, delays=2390/0.04/0/0.01, dsn=4.3.5, status=deferred (mail system configuration error) Oct 30 09:25:19 lace3 postfix/pipe[19729]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1 Thanks for any info. Regards, Koenraad Lelong.
Re: [Dovecot] Why : dovecot_destination_recipient_limit = 1 ?
Koenraad Lelong: I'm trying to activate sieve. In all tutorials I have seen I need to set dovecot_destination_recipient_limit = 1 in Postfix's main.cf. Can anyone explain why ? I like to know because when I set this and the dovecot transport in Postfix, I'm having problems when aliasses are used that map to different recipients, i.e. i...@... results in us...@..., us...@..., etc. The problems are an error from Postfix : Oct 30 09:25:19 lace3 postfix/pipe[19729]: 8A77E2D5B5B: to=some.b...@some.where.org, relay=dovecot, delay=2390, delays=2390/0.04/0/0.01, dsn=4.3.5, status=deferred (mail system configuration error) Oct 30 09:25:19 lace3 postfix/pipe[19729]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1 Well, the last message says it all: you've instructed postifx' pipe to add a Delivered-To header field to the message. And this obviously can't work when delivering one message to multiple recipients in one pass. See also: http://www.postfix.org/pipe.8.html -- Regards mks
[Dovecot] X.509 certificate based IMAP login
Hello list,
The dovecot version is 1.2.6 running on Solaris x86 11 (nv-b91).
The relevant configuration lines are:
passdb ldap { # LDAP database (doc/wiki/AuthDatabase.LDAP.txt.)
args = /pfx/etc/dovecot/dovecot-ldap.conf
}
The file dovecot-ldap.conf is correct and LDAP authentication is
working well.
We would like to make it possible for users with a X.509 client
certificate to log in without providing LDAP or any other
credentials. Is there something like:
passdb x509 {
args = /pfx/etc/dovecot/dovecot-caroots.pem
nopwd = yes
}
...avaibable, or is there another solution?
Thanks,
Brian
Re: [Dovecot] Another 2.0.alpha2 panic
Fri Oct 30 21:08:16 server dovecot[27407]: lda(pid 27407 user userW): Panic: file istream.c: line 104 (i_stream_read): assertion failed: ((size_t)ret+old_size == _stream-pos - _stream-skip) i.e. was the input stream seekable? Postfix's pipe process invoked dovecot-lda so no, the input stream was not seekable. I'll try your patches. Thanks.
[Dovecot] Unable to create imap nested dirs.
Hi all, I'm trying to config a dovecot server on a debian-lenny box but I'm experiencing a problem that serveral users have on the net, but I haven't found any solution. I'm trying to create nested dirs with my thunderbird 2.0.0.23 client but without any luck :( I can create dir in the root, but not subdirs. have you any ideas? here you can you see the small config and attached my full config dovecot -n # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd # dovecot -a # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: mail protocols: imaps listen: * ssl_listen: ssl: yes ssl_ca_file: ssl_cert_file: /etc/ssl/certs/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.pem ssl_key_password: ssl_parameters_regenerate: 168 ssl_cipher_list: ssl_cert_username_field: commonName ssl_verify_client_cert: no disable_plaintext_auth: yes verbose_ssl: no shutdown_clients: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=%u method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_trusted_networks: login_process_size: 64 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 512 mail_max_userip_connections: 10 verbose_proctitle: no first_valid_uid: 500 last_valid_uid: 0 first_valid_gid: 1 last_valid_gid: 0 mail_access_groups: mail_privileged_group: mail mail_uid: mail_gid: mail_location: mail_cache_fields: mail_never_cache_fields: imap.envelope mail_cache_min_mail_count: 0 mailbox_idle_check_interval: 30 mail_debug: no mail_full_filesystem_access: no mail_max_keyword_length: 50 mail_save_crlf: no mmap_disable: no dotlock_use_excl: yes fsync_disable: no mail_nfs_storage: no mail_nfs_index: no mailbox_list_index_disable: yes lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: no maildir_very_dirty_syncs: no mbox_read_locks: fcntl mbox_write_locks: fcntl dotlock mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/imap mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/imap mail_log_prefix: %Us(%u): mail_log_max_lines_per_sec: 10 imap_max_line_length: 65536 imap_capability: imap_client_workarounds: imap_logout_format: bytes=%i/%o imap_id_send: imap_id_log: imap_idle_notify_interval: 120 pop3_no_flag_updates: no pop3_enable_last: no pop3_reuse_xuidl: no pop3_lock_session: no pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s dict_db_config: dict_process_count: 1 managesieve_max_line_length: 65536 managesieve_logout_format: bytes=%i/%o managesieve_implementation_string: dovecot auth default: mechanisms: plain realms: default_realm: cache_size: 0 cache_ttl: 3600 cache_negative_ttl: 3600 executable: /usr/lib/dovecot/dovecot-auth user: root chroot: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: username_format: master_user_separator: anonymous_username: anonymous krb5_keytab: gssapi_hostname: winbind_helper_path: /usr/bin/ntlm_auth failure_delay: 2 verbose: no debug: no debug_passwords: no ssl_require_client_cert: no ssl_username_from_cert: no use_winbind: no count: 1 worker_max_count: 30 process_size: 256 passdb: driver: pam args: deny: no pass: no master: no userdb: driver: passwd args:
Re: [Dovecot] Unable to create imap nested dirs.
On 11/01/2009 01:41 AM Leo wrote: Hi all, I'm trying to config a dovecot server on a debian-lenny box but I'm experiencing a problem that serveral users have on the net, but I haven't found any solution. I'm trying to create nested dirs with my thunderbird 2.0.0.23 client but without any luck :( I can create dir in the root, but not subdirs. have you any ideas? Follow this thread: http://dovecot.org/list/dovecot/2009-November/044169.html Regards, Pascal -- The trapper recommends today: c01dcofe.0930...@localdomain.org
Re: [Dovecot] Unable to create imap nested dirs. [linux/debian/lenny]
Leo pippo1...@gmail.com wrote: I'm trying to config a dovecot server on a debian-lenny box but I'm experiencing a problem that serveral users have on the net, but I haven't found any solution. I'm trying to create nested dirs with my thunderbird 2.0.0.23 client but without any luck :( I can create dir in the root, but not subdirs. have you any ideas? here you can you see the small config and attached my full config dovecot -n # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd # dovecot -a [...] mail_location: [...] 0) You are the socond person asking such question. 1) http://wiki.dovecot.org/MailLocation quote By default the mail_location setting is empty, which means that Dovecot attempts to locate automatically where your mails are. This is done by looking at ~/Maildir, /var/mail/username, ~/mail and ~/Mail in that order. It's usually a good idea to explicitly specify where the mails are, even if the autodetection happens to work. Autodetection commonly fails for new users who don't have the mail directory created yet. /quote -- [plen: Andrew] Andrzej Adam Filip : a...@onet.eu It's the best thing since professional golfers on 'ludes. -- Rick Obidiah
Re: [Dovecot] Unable to create imap nested dirs. [linux/debian/lenny]
On 11/02/2009 07:49 PM Andrzej Adam Filip wrote: 0) You are the socond person asking such question. *lol*. No, it's the same person. I'm also blundered in. He has sent his mail on Sun, 01 Nov 2009 01:41:21 +0100, when you check the header, you will see: X-Mailman-Approved-At: Mon, 02 Nov 2009 19:37:12 +0200 Regards, Pascal -- The trapper recommends today: c01dcofe.0930...@localdomain.org
[Dovecot] Related 2.0.alpha2 issue
Just saw this new twist to an issue I reported last week with dovecot-2.0.alpha2. I logged into an IMAP account using telnet to port 143. After 30 seconds dovecot closed the connection. Mon Nov 2 16:00:07 server dovecot[52355]: imap: dup2(-1, 5) failed: Bad file descriptor Mon Nov 2 16:00:07 server dovecot[52355]: imap: service(imap): dup2s failed Mon Nov 2 16:00:07 server dovecot[52355]: imap-login: Login: user=userV, method=PLAIN, rip=192.168.1.10, lip=192.168.1.7, pid=59521 Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): Initial status notification not received in 30 seconds, killing the process Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): child 59521 killed with signal 9 Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): command startup failed, throttling
[Dovecot] dovecot-1.2.6: Panic: pool_data_stack_realloc(): stack frame changed
When playing with large numbers of IMAP keywords on dovecot-1.2.6 imap crashed: Panic: pool_data_stack_realloc(): stack frame changed Looks like either maildir_file_do() shouldn't T_BEGIN/T_END or the keywords array should start larger. 0 libSystem.B.dylib 0x7fff875f4eba __kill + 10 1 libSystem.B.dylib 0x7fff875f4eac kill + 14 2 libSystem.B.dylib 0x7fff87683519 raise + 25 3 libSystem.B.dylib 0x7fff876a4e12 abort + 90 4 imap 0x00010008022f default_fatal_finish + 69 5 imap 0x00010007f4b4 i_internal_error_handler + 0 6 imap0x00010007fa36 i_info + 0 7 imap 0x00010008987e pool_data_stack_realloc + 150 8 imap0x00010007d77c buffer_alloc + 60 9 imap 0x00010007d947 buffer_check_limits + 113 10 imap0x00010007dde8 buffer_append + 38 11 imap 0x000100060c50 mail_index_sync_keywords_apply + 88 12 imap 0x000100043f20 index_sync_changes_apply + 184 13 imap 0x000100026b6d maildir_sync_flags + 131 14 imap 0x00010002a7c6 maildir_file_do_try + 334 15 imap 0x00010002a34e maildir_file_do + 58 16 imap 0x0001000263c4 maildir_sync_index + 1102 17 imap 0x00010002588e maildir_sync_context + 806 18 imap 0x000100025aa4 maildir_storage_sync_init + 92 19 imap 0x00010004ad9c mailbox_sync_init + 16 20 imap 0x0001ebc8 imap_sync_init + 98 21 imap 0x0001fd29 cmd_sync_delayed + 425 22 imap 0x0001814c client_handle_input + 442 23 imap0x000174ea client_input + 104 24 imap 0x000100087c20 io_loop_handler_run + 246 25 imap0x000100086f16 io_loop_run + 56 26 imap0x00010001063b main + 1629 27 imap0x000110b8 start + 52 also 0 libSystem.B.dylib 0x7fff875f4eba __kill + 10 1 libSystem.B.dylib 0x7fff875f4eac kill + 14 2 libSystem.B.dylib 0x7fff87683519 raise + 25 3 libSystem.B.dylib 0x7fff876a4e12 abort + 90 4 imap 0x00010008022f default_fatal_finish + 69 5 imap 0x00010007f4b4 i_internal_error_handler + 0 6 imap0x00010007fa36 i_info + 0 7 imap 0x00010008987e pool_data_stack_realloc + 150 8 imap0x00010007d77c buffer_alloc + 60 9 imap 0x00010007d947 buffer_check_limits + 113 10 imap0x00010007dde8 buffer_append + 38 11 imap 0x000100060c50 mail_index_sync_keywords_apply + 88 12 imap 0x000100043f20 index_sync_changes_apply + 184 13 imap 0x000100026b6d maildir_sync_flags + 131 14 imap 0x00010002a7c6 maildir_file_do_try + 334 15 imap 0x00010002a34e maildir_file_do + 58 16 imap 0x0001000263c4 maildir_sync_index + 1102 17 imap 0x00010002588e maildir_sync_context + 806 18 imap 0x000100025aa4 maildir_storage_sync_init + 92 19 imap 0x00010004ad9c mailbox_sync_init + 16 20 imap0x00010004ade0 mailbox_sync + 48 21 imap 0x000158b8 cmd_select_full + 1748 22 imap0x00015d9b cmd_select + 11 23 imap 0x00017de6 client_command_input + 36 24 imap 0x00017f17 client_command_input + 341 25 imap 0x00018086 client_handle_input + 244 26 imap0x000174ea client_input + 104 27 imap 0x000100087c20 io_loop_handler_run + 246 28 imap0x000100086f16 io_loop_run + 56 29 imap0x00010001063b main + 1629 30 imap0x000110b8 start + 52
Re: [Dovecot] dovecot-1.2.6: Panic: pool_data_stack_realloc(): stack frame changed
On Mon, 2009-11-02 at 16:35 -0600, Mike Abbott wrote: When playing with large numbers of IMAP keywords on dovecot-1.2.6 imap crashed: Panic: pool_data_stack_realloc(): stack frame changed Looks like either maildir_file_do() shouldn't T_BEGIN/T_END or the keywords array should start larger. Or 3) don't use data stack for them at all: http://hg.dovecot.org/dovecot-1.2/rev/939edf3ed09b signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.6: Panic: pool_data_stack_realloc(): stack frame changed
Or 3) don't use data stack for them at all: http://hg.dovecot.org/dovecot-1.2/rev/939edf3ed09b Yeah, that works too :). Thanks.
