similar to: Chrooting question

hello all i am new to dovecot and i have a small problem. I use qmail as a pop3 server and dovecot as imap. my rc script is as follows: -----snip----- #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start '|preline procmail' splogger qmai -----end----- thus i deliver mails through procmail so all mails are located to /var/spool/mail. The problem exists when i tested

Hello! Could somebody give some feedback on this configuration: - OpenBSD box with local ssh users. - /home directory mounted with nosuid,noexec. - postfix dropping mail in /home/username/mail/INBOX, with the UID/GID of the user. - dovecot: valid_chroot_dirs = /home default_mail_env = mbox:/home/%u/mail/:INBOX=/home/%u/mail/INBOX Are there any obvious ways for a local user to help

Hello, I've got a dovecot setup using PAM and real system users. In this setup I also use pure-ftpd to give local users ftp access to their $HOMEs. To have pure-ftpd chroot into the user home i replaced /home/user with /home/user/./ in /etc/passwd. Unfortunately this breaks Dovecot this way: Oct 23 18:18:20 localhost dovecot: Invalid chroot directory '/home/foo' (user foo) (see

Greetings, I am configuring a new Dovecot installation, and the way the valid_chroot_dirs and mail_chroot variables affect the mail processes are a bit unclear to me. I was wondering if anyone could provide me with more specific details than the comments in the configuration file do, or maybe even recommend some values given my configuration. We have a Debian GNU/Linux system and a mix of users

Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process

Hi, I think that the wu-ftp style chroot /./ should be a configurable option. In our servers we have some home directories in /chroot-web/./username (where web users can upload their web sites in a chrooted environment) and all imap mail in /mail-disk/username. We are planning a dovecot migration from our modified version of uw-imap and we noticed that the chroot in /chroot-web/ can't be

Recently I've made the post about "double homedir" problem, but I couldn't recreate it later. Here're the exact steps to make it happen (configuration is at the bottom): 1) set configuration as below with passwd-files 2) clean testms dir (not necessary though) 3) reload dovecot (HUP is enough) 4) access the server with any client using testms user (make sure no other

I am setting up dovecot for imap on a new Fedora 3 box. Through SquirrelMail I can access my email - no problem. However my other users are getting this error message: ERROR : Connection dropped by imap-server. Query: CAPABILITY Looking in the maillog file for further error details gives me this: dovecot: chroot directory no included in valid_chroot_dirs: /home/user Looking through the

I'm getting the following error when using dovecot replication: dovecot: imap(foo at bar.com): Error: open(/var/dovecot/replication-notify-fifo) failed: No such file or directory I guess this has something to do with the fact that every user is chrooted in it's own homedir. Does dsync support dsync notification when all users are chrooted? lmtp does not seem to have this problem so new

Hi all, I'm using dovecot v2.0.11 on fedora14 with postfix. This system was migrated from an old UW mbox system, so users already have ~/mail/INBOX.* files. Now for some reason, dovecot is creating ~/mail/mail/INBOX.* files and somehow not seeing the mail_location properly. I've set mail_location to "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u", which has worked on a

I'm not sure if it's even intended to work in this particular case, but there's a problem when chroot is explicitely defined and rawlogging is used. Rawlog respects chroot point, without being actually chrooted. Consider configurtion as below, with two cases (dovecot.rawlog dir is of course created earlier, with appropriate uid/gid). 1) dovecot.userdb:

The sample config file has: # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That

Yep, I agree. Well, what would you prefer? I handle it for you or you handle it yourself? I''m tempted to go with the former because, well, it''s been there for a while now. I can even use strtok to detect if ''\\\\'' is at the beginning of the string and add them only if not found. I''ll have to take a look at delete user - it worked for add_user,

Ok - time for me to patch and update the docs! Thanks for the testing! Dan -----Original Message----- From: Date, Shashank [Non-Employee] [mailto:Shashank.Date@mail.sprint.com] Sent: Monday, March 01, 2004 10:02 AM To: Berger, Daniel Subject: RE: win32etc test failure I like your approach better: allow me to be lazy (so I am not _forced_ to give it) but forgive me if I do ;-) It worked

For delete_user, try this patch: etc.c, line 639: - lpHost = (LPCWSTR)STR2CSTR(rbHost); +lpHost = AllocWideLString(rbHost); Lemme know how it goes. Dan -----Original Message----- From: win32utils-devel-bounces@rubyforge.org [mailto:win32utils-devel-bounces@rubyforge.org] On Behalf Of win32utils-devel@rubyforge.org Sent: Monday, March 01, 2004 10:02 AM To: Date, Shashank [Non-Employee] Cc:

Folks, I've been tasked to find a solution that will create file-transfer-only accounts that are jailed or chrooted to a specific directory. (Not an uncommon task, I think.) Using the OpenSSH server and the OpenSSH scp client program, I can achieve the goal of having a file transfer only account jailed to a specified directory, by using the "scpjail" script (attached) as a

> > The main problem seems to be with the way that debian starts bind > > using > > the script /etc/init.d/bind. I thought it would be really neat to > > just > > change the #!/bin/sh at the top of the script to something like : > > #!/usr/sbin/chroot /chroot-dns/ /bin/sh > > or > > #!/usr/sbin/chroot /chroot-dns/

OS: OpenBSD/i386 dovecot: dovecot-1.0-test68 dovecot can not start, when i chroot "auth process" can i defined the "auth-work.XXX" unix socket path?? mail.log ----------------------------------------- Dovecot v1.0-test68 starting up auth(default): mysql: Connected to (null) (mail) Auth process died too early - shutting down auth(default):

On Tue, 14 Jul 1998, cfb wrote: > The main problem seems to be with the way that debian starts bind using > the script /etc/init.d/bind. I thought it would be really neat to just > change the #!/bin/sh at the top of the script to something like : > #!/usr/sbin/chroot /chroot-dns/ /bin/sh > or > #!/usr/sbin/chroot /chroot-dns/ /chroot-dns/bin/sh try changing

On 24.01.2020 14:01, Christian wrote: > On 23.01.2020 10:26, L.P.H. van Belle via samba wrote: >> Hai Christian, >> >>>>> Thism, this is just strange, Christian, did you already >>> run and if not, can you run it and post the ouputs. : >>>>> net cache flush >>>>> systemctl stop samba winbind >>>>> systemctl