Here is an example of a real configuration file for vpopmail backend, just adapt for your needs:

dovecot.conf

base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no syslog_facility = mail ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem login_greeting = Server is ready. mail_location = maildir:~/Maildir mail_uid = 89 mail_gid = 89 first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 protocol imap { } protocol pop3 { } auth default { mechanisms = plain login digest-md5 cram-md5 passdb vpopmail { } userdb vpopmail { } user = root }

On Fri, Nov 28, 2008 at 2:49 PM, Yacoubi Mohamed myacoubi@euro-web.fr wrote:

Hello,

Thank you for this link, but this is not what I want. Dovecot is only used for imap.

Currently, authentication works fine, but new fields are created in a subdirectory. Example: /var/vpopmail/domains/0/domain.com

Once authenticated, I just want to be in chroot /var/vpopmail/domains/0/domain.com/user and not in /var/vpopmail/domains/domain.com/user

You don't need to worry about where vpopmail stored domain's and user's folders, dovecot will find it.

I explained that vpopmail which manages the creation of areas and I can not influence the subdirectory.

Sincerely,

-- Mohamed YACOUBI

-- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"