similar to: specifying home/sieve/sieve_dir relative to mail_location

Hello all, I have set up two servers with dovecot and replication. The mail location is mail_location = sdbox:/var/spool/mail/%u Everything works fine when I override the homedirectories userdb { driver = passwd override_fields = home=/var/spool/mail/%u } But, when I do not override the homedirectories, replication does not work, and the following error is logged: Oct 24 14:40:45

Hi list, I'm new on this mailing list and I'm kind of stucked at the moment. I managed to get Postfix and Dovecot working together with Amavis, OpenLDAP und SASL on Ubuntu Linux Release "Dapper Drake". The Dovecot version shipped with Dapper is 1.0-beta3 (at least, that's what the package database tells me), I also tried this with a Debian Backport of version 1.0-rc15.

I am running version 1.1.1 with mail_location: maildir:~/Maildir. This is working great as all our users have UNIX accounts with nologin shells. New domains (and their users) are about to come online and we would like to migrate to a setup with virtual mailboxes/users. From the wiki and comments within dovecot.conf, I see it is possible to do this piecemeal so both local and virtual users

Am 06.03.2017 um 09:06 schrieb chaouche yacine: > Hi Chris, > >> I have since learned that mail_home and mail_location should be > >> different. I plan to use this: > > I'm interested about any sources for this ? http://wiki.dovecot.org/VirtualUsers/Home "Home directory shouldn't be the same as mail directory with mbox or Maildir formats (but with

Hello, I spend a couple of days configurating a new installation of dovecot 2.0.14 with virtual accounts and NFS storage for maildir home/mail directories. At this point I need shared mailboxes but since user mail/home locations are ldap attributes, how is it supposed I must configure this for shared mailboxes? for the users' mail/home directories I set this line: user_attrs =

We have used the great managesieve you have merged together, with sieve, to create pigeonhole. However, when a user creates a custom script through a GUI of ours, the default, as we expected, would be ignored. Maybe you could add a retain_sieve_global=yes|no setting OR be more complex by having the sieve_global_dir copied to the users sieve_dir on first managesieve script save, if another

Hi Stephan, I've compiled the latest managesieve code from Sun May 17th 2009. ManageSieve had created the sieve directory with 0770 permissions, but the user's home directory has only 0700 permissions. With dovecot-1.{0,1}-managesieve the permissions was set properly. Regards, Pascal -- The trapper recommends today: cafebabe.0916419 at localdomain.org

Hello everybody, As explained in the topic, i have troubles with authentication of my users. First of all, sorry for my poor english... I'm running dovecot v1.2.15 on a Debian 6 64bits server up to date. My users database is an Active Directory 2003 (it's important to know that because Active Directory can't retrieve users passwords, you have to bind LDAP with a domain administrator).

I'm in the process of moving from LDA to LMTP (Postfix upstream) prior to a transition off `nix accounts to virtual accounts and am stumped by LMTP reporting ??? dovecot: lmtp(10019, jeff at example.com): Error: Relative home directory paths not supported: 0 LDA does /not /have any problems with PAM or passwd-file passdb/userdb and the ubiquitous definition of ??? mail_location =

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64

Hello people, I used primarily mutt and sendmail for many years. (And elm before mutt.) All my mail was saved into ~/Mail. Messages from, say, smith at foo.ber were stored in ~/Mail/smith; all mail from smith was catenated into one file, and if I wanted to find something that smith had written, I would just cd to ~/Mail and grep or egrep on a likely word or phrase. Is there a script

On 20.11.2017 16:12, Jeff Kletsky wrote: > I'm in the process of moving from LDA to LMTP (Postfix upstream) prior > to a transition off `nix accounts to virtual accounts and am stumped > by LMTP reporting > > ??? dovecot: lmtp(10019, jeff at example.com): Error: Relative home > directory paths not supported: 0 > > LDA does /not /have any problems with PAM or passwd-file

On 20.11.2017 16:20, Jeff Kletsky wrote: > On 11/20/17 6:15 AM, Aki Tuomi wrote: >> >> On 20.11.2017 16:12, Jeff Kletsky wrote: >>> I'm in the process of moving from LDA to LMTP (Postfix upstream) prior >>> to a transition off `nix accounts to virtual accounts and am stumped >>> by LMTP reporting >>> >>> ???? dovecot: lmtp(10019, jeff

I'd like to store all of my mail in maildir, but I want to store the inbox and indices on fast storage and everything else on deep storage. Does the following configuration value for mail_location accomplish this? mail_location = maildir:/data/deep/%Ld/mail/%Ln:INBOX=/data/fast/%Ld/mail/%Ln:INDEX=/data/fast/%Ld/indices/%Ln

On 11/20/17 6:15 AM, Aki Tuomi wrote: > > On 20.11.2017 16:12, Jeff Kletsky wrote: >> I'm in the process of moving from LDA to LMTP (Postfix upstream) prior >> to a transition off `nix accounts to virtual accounts and am stumped >> by LMTP reporting >> >> ??? dovecot: lmtp(10019, jeff at example.com): Error: Relative home >> directory paths not

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 17/05/2020 12:34 Laura Smith <<a href="mailto:n5d9xq3ti233xiyif2vp@protonmail.ch">n5d9xq3ti233xiyif2vp@protonmail.ch</a>> wrote:

Short version: What is the correct way to configure the mail_location option for Mailidr format? I've long had it setup this way: mail_location = maildir:/var/vmail/%d/%n based on this guide: https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-mysql Is that correct? Longer version: After upgrading from Dovecot v2.0.x to v2.2.x yesterday I'm coming

I?m considering moving from maildir to mdbox, but don?t quite see how I should do the conversion with minimal downtime. Our userdb is ldap, and the we use this setting to point to the users maildirectory: user_attrs = mailMessageStore=mail=maildir:%$:INDEX=/indexes/%1u/%1.1u/%u,mailQuota=quota_rule=*:storage=%$ i.e. every user has a "mailMessageStore" attribute in LDAP that points to

Hello, I use Dovecot for rather long time, but I'm still in doubt for some small things. Here they are: 1. The homedir value points to the place where everything for the user stored at, while mail_location is something (some place) where mail stored at. if I deal with pure virtual users (all users are in sql tables and no system homes for them at all), should I ever care for returning

In using mysql, in the configuration file we need to specify, in the user query, '/path/ as home, yet but in dovecot.conf, we also are setting mail_location, the same thing is it not, so unless I've missed something, do we still need to use the path as home in the user query? Do we only need set that if it differs from mail_location? Thanks