search for: login_chroot

...t running chrooted? Not that I know of. However, the option to (apparently) decide this is confusing at best. Here is what I have entered. # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless login_chroot = yes Now, my guts tell me that this WILL make it run chrooted. However, reading the material at this link... http://wiki.dovecot.org/Rootless ...says otherwise, and that setting this to 'no' would be making it run chrooted. For reference, this is the process line from ps -aux|grep d...

...ovecot at dovecot.org Subject: Re: [Dovecot] passwd authentication issues (ATTN: Petar) Hi, Petar, *********** REPLY SEPARATOR *********** On 12-Jul-06 at 08:49 Petar Bogdanovic wrote: >> # wish to run the whole Dovecot without roots. >> # http://wiki.dovecot.org/Rootless >> login_chroot =3D yes > >Hmm, I had chroot(8) on my mind, but AFAIK, this option and chroot(8) >have both something to do with chroot(2). > >I don't fully understand what `login_chroot' is actually doing.=20 >However, >it's not activated in my dovecot.conf. > >$ grep login_...

...g it work within the restrictions of the login process that's more interesting. I have made some changes to the wiki (pending approval) to - enhance the discussion of proxy with LDAP http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy - discuss the implication of this patch w.r.t. the login_chroot configuration parameter: http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy/HostLookup Feedback is appreciated, particulary from a security standpoint. Cheers, -Martin Foster martin_foster at netlog.net dump of wiki info, for the lazy. It will look better if viewed from the URL: ht...

...v zfs base_dir: /zhome/var/run/dovecot log_path: /zhome/var/log/dovecot_main.log info_log_path: /zhome/var/log/dovecot_info.log protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /zhome/var/run/dovecot login_executable: /zhome/dovecot/libexec/dovecot/imap-login login_user: exim login_chroot: no login_max_processes_count: 30 max_mail_processes: 30 first_valid_uid: 1 mail_uid: exim mail_gid: exim mail_location: mbox:/zhome/var/mail:INBOX=/zhome/var/mail/.dead_letters mail_debug: yes mbox_lazy_writes: no auth default: failure_delay: 1 verbose: yes debug: yes worker_max_reques...

...maildir:User quota test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./ dovecot.old.conf # 2.0.beta4 (6891d20929ca): ./dovecot.old.conf doveconf: Warning: Obsolete setting in ./dovecot.old.conf:26: login_dir has been removed doveconf: Warning: Obsolete setting in ./dovecot.old.conf:29: login_chroot has been replaced by service { chroot } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 29: Unknown setting: chroot doveconf: Warning: Obsolete setting in ./dovecot.old.conf:32: login_user has been replaced by service { user } doveconf: Fatal: Error in configuration file ....

...sten(imap): 127.0.0.1:143 listen(pop3): 127.0.0.1:110 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_chroot: no first_valid_uid: 5000 last_valid_uid: 5000 mail_location: mbox:/home/vmail/%d/%u mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/l...

Hi, There is a small typo in src/lib/network.c line 624 return "A non-recovable name server error occurred"; should be return "A non-recoverable name server error occurred"; Sorry about the pedantry. BTW, I am getting this error whenever I am trying to resolve a name from inside dovecot, but I can using the system tools. I am trying to get the proxying code to

I've got dovecot working on imap But when I try to run imaps I get: imap-login: Nove 08 19:11:19 Warning: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [192.168.1.103] Now I'm not sure if theres any difference here, but I don't have string for 'login = imaps' or 'login = pop3s' to match with my protocols string

On Thu, 2004-04-29 at 15:57, Timo Sirainen wrote: > One more reason to make all logging go through dovecot-master process.. > > Temporary fix of course is setting login_chroot = no to config file. Thanks, Timo, that did the trick. Also thanks to Quentin for his reply, though I don't understand any of it. As stated, my knowledge of unix is rather limited... On Thu, 2004-04-29 at 15:48, Quentin Garnier wrote: > It's because the logging process is chrooted,...

...mething? $ ./dovecot --version 1.2.11 $ ./dovecot -n # 1.2.11: /usr/local/etc/dovecot.conf Error: login_user cyg_server (uid 1005) must not be same as auth_user Fatal: Invalid configuration in /usr/local/etc/dovecot.conf Config trying to use: protocols = imap disable_plaintext_auth = no ssl = no login_chroot = no login_user = cyg_server login_process_size = 0 login_max_processes_count = 5 mail_location = maildir:~/Maildir max_mail_processes = 5 mail_process_size = 0 auth_process_size = 0 auth default { mechanisms = plain passdb passwd-file { args = /usr/local/etc/dovecot.users } userdb pass...

...directory '/home/foo' (user foo) (see valid_chroot_dirs in config file) and dovecot.conf says # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = Now if I set valid...

was wondering if anyone else has had problems with dovecot logging to syslog? When I start the server it works fine, then after an hour or so it stops.. restarting the server always makes it work again. -- James L Moser james at powweb.com PowWeb Hosting http://www.powweb.com /(bb|[^b]{2})/, that is the Question. mysql>SELECT * FROM user WHERE clue >

...com/howtos/mailserver/mailserver.html My problem is in starting the dovecot server. I get the following error Starting Dovecot Imap: Error: Error in configuration file /etc/dovecot.conf line 16: Unknown setting: passdb My dovcot.conf file: protocols = imap pop3 login_dir = /var/run/dovecot/login login_chroot = yes disable_plaintext_auth = no login_user = dovecot first_valid_uid = 101 last_valid_uid = 101 first_valid_gid = 101 last_valid_gid = 101 valid_chroot_dirs =/home/vmail/domains default_mail_env = maildir:/home/vmail/domains/%d/%n auth = default auth_mechanisms = plain auth_userdb = ldap /etc/dov...

...SD 6.2-RELEASE i386 base_dir: /var/run/dovecot log_path: /var/log/dovecot_main.log info_log_path: /var/log/dovecot_info.log listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: nobody login_chroot: no login_max_processes_count: 30 max_mail_processes: 30 first_valid_uid: 1 mail_uid: smmsp mail_gid: smmsp mail_location: mbox:%h/Mail:INBOX=/var/mail/%u mail_debug: yes mbox_lazy_writes: no auth default: failure_delay: 1 verbose: yes debug: yes worker_max_request_count: 1 passdb:...

Hello there, I have been trying to make the patch work for libwrap(TCP Wrappers) posted on http://dovecot.org/patches <http://dovecot.org/patches%20Patch%20of%201.1> Patch of 1.1 but could not get it work. Any help will be highly appreciated. After compiling and running it I get error "Error: login_tcp_wrappers can't be used because Dovecot wasn't built with

...8 -0000 1.40 +++ src/master/login-process.c 15 Apr 2003 17:37:27 -0000 @@ -384,7 +384,8 @@ static void login_process_init_env(struc clean_child_process() since it clears environment */ restrict_access_set_env(group->set->user, group->set->uid, set->login_gid, - set->login_chroot ? set->login_dir : NULL); + set->login_chroot ? set->login_dir : NULL, + set->allow_zero_gid); env_put("DOVECOT_MASTER=1"); Index: src/master/mail-process.c =================================================================== RCS file: /home/cvs/dovecot/src/master/m...

...a value of my default realm = casa.cult.cu in this case the default domain where authenticate my users. My configuration in the new version of dovecot: protocols = imap pop3 protocol imap { listen = * } protocol pop3 { listen = * } login_dir = /var/run/dovecot/login login_chroot = yes login_greeting = Dovecot ready. mail_location = maildir:/var/spool/virtualmail/%d/%u mail_debug = yes mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } protocol lda { postmaster_address = postmast...

...ocols = imap imaps managesieve shutdown_clients = yes syslog_facility = mail ssl_cert_file = /etc/ssl/cert ssl_key_file = /etc/ssl/key verbose_ssl = no login_process_per_connection = yes login_processes_count = 2 login_max_processes_count = 10 login_user = dovecot login_dir = /var/run/dovecot/login login_chroot = yes mail_location = maildir:/var/mail/%d/%n mail_extra_groups = postfix mail_full_filesystem_access = no mail_debug = no verbose_proctitle = yes first_valid_uid = 2000 last_valid_uid = 2000 first_valid_gid = 2000 last_valid_uid = 2000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = yes...

...ype == PROCESS_TYPE_IMAP) { env_put(t_strconcat("CAPABILITY_STRING=", --- src/master/master-settings.c.orig 2008-06-21 15:09:16.000000000 +0200 +++ src/master/master-settings.c 2008-07-07 20:28:37.000000000 +0200 @@ -208,6 +208,7 @@ MEMBER(login_process_per_connection) TRUE, MEMBER(login_chroot) TRUE, MEMBER(login_greeting_capability) FALSE, + MEMBER(login_tcp_wrappers) FALSE, MEMBER(login_process_size) 64, MEMBER(login_processes_count) 3, @@ -479,6 +480,7 @@ fix_base_path(auth->parent->defaults, &s->master.path); fix_base_path(auth->parent->defaults, &amp...

...: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-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...