search for: mail_loc

...e that the mail location has failed as follows: ========= Jan 16 14:18:16 myservername dovecot: pop3-login: Login: user=<userA>, method=PLAIN, rip=aaa.bbb.ccc.ddd, lip=www.xxx.yyy.zzz, mpid=1360, TLS Jan 16 14:18:16 myservername dovecot: pop3(userA): Error: user molla: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/userA Jan 16 14:18:16 myservername dovecot: pop3(userA): Error: Invalid user settings. Refer to server log for more information. ========= Yet my config also come out strangely as below: ========= root at guy...

mail_location setting has started becoming a bit bloaty. I'm not actually even sure why I've kept adding more parameters to it rather than just adding new settings. It's also caused confusion, because people try things like: mail_location = mbox:/var/mail/%u mail_location = mbox:INBOX=/var/mail...

Okay, Let's try this a different way. I've been able to configure past dovecot to have a different mail_location setting for the same user, but with different protocols. When the user requests POP3S, I adjusted the mail_location to /var/mail/$USER (with mbox in use). When that *same* user requested IMAPS protocol, the required mail_location is the Maildir folder. This allows for independent two mail...

...still need to inspect the mailbox ... thank you, > > yes > :) Well, although I am able to issue a mailbox status command regardless, the implication was that the command displayed an empty string (nothing useful), and thus a working example using files not in the locations specified by mail_location would be useful. In my configuration mail_locations is defined as: mail_location = mdbox:~/mail:INDEX=/var/dovecot/index/%u So a command of the form ?doveadm mailbox status -u userName all INBOX? uses mail_location as defined in dovecot.conf to locate the mail and index files, and displays...

Hi, I plan on upgrading from 1.1.13 to 1.2.4 using an RPM. I have read the wiki [1] and have a question about the mail_location variable. Currently, in 1.1.13, I use: mail_location = maildir:/var/spool/virtual_mailboxes/%h with virtual mailboxes. However, I am planning to change it to use: home=/var/spool/virtual_mailboxes mail_location = maildir:%h as part of the new configuration. Is that correct or have I mis...

hi, my mail_location looks like: mail_location = maildir:/imap/spool/%d/%1n/%n:INDEX=/imap/spool/% d/indexes/%1n/%n for example: /imap/spool/domain.foo/a/anton/new The problem is, that the user log in with only the username and no domainpart. So, Dovecot looks into: /imap/spool/a/anton/new what isn't co...

On 16.10.2017 13:30, Mar?a Arrea wrote: > El 16/10/17 a las 12:25, Aki Tuomi escribi?: >> ITERINDEX is a flag, it's not supposed to have any value. >> >> Aki > So ITERINDEX=yes should be the right value? This is the right > mail_location settings? > > mail_location=mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:ITERINDEX=yes:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n > > > Precisely correct value is just INTERINDEX. No yes or no. Aki > > >> &g...

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

hi.... i have virtual users stored in ldap server and i must to do some modifications that requiere to chage mail_location value... the solution comes to use the "uid" value stored in ldap server for users on mail_location parameter... i can see in http://wiki.dovecot.org/Variables that i can't do them (i uses sasl authentication) so.. ?exist any way to get a value from ldap server and use them in ma...

...; ??? I have a question about the new setting ITERINDEX. This is my >> filesystem layout >> >> ??? /indices_dovecot : 8 x Fast SSD drives >> ??? /buzones : 32x SAS 10k rpm disks >> ??? /buzones/alternativo : 24 x SAS 7.2k rpm slow disks >> >> ??? This is my mail_location: >> >> mail_location = >> mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n >> >> >> >> ??? What should I write in mail_location with the new ITERINDEX setti...

On 14-2-20 13:39, Aki Tuomi wrote: > This is why you put mail_location=driver:~/Mail and ensure the mails are > under there, instead of mail_location=driver:~/ Yes, that is what I thought; when I use that setting, I get this error: Feb 14 14:32:15 xxxx dovecot[8549]: imap(jos)<8739><5ErUO4meZthSsH9H>: Initializing mail storage from mail_locatio...

Hi all I've mounted a cluster ACTIVE-PASIVE, with the mailbox in a SAN. The user's home are: /Correo/mail/foo/home I use: Postfix, dovecot and dovecot_lda. The folder /san/mail is only show in the active node (switch the virtual ip, filesystem and daemons). How i configure dovecot mail_location?? Now i have: mail_location: maildir:/Correo/mail/%n The problem is that the admin mails in pasive node are in enqueued and not arrive. I need a user with mail_location in /var/spool/mail/foo (in aliases, root: foo)and the rest users in /Correo/mail/ I have seen override mail_executable,...

...passwordless sudo between them), but I guess they could use same uid/gid and just have separate entries in passwd/shadow. Anyway at the moment I'm not concerned about getting the authentication part working, but whether there's something in dovecot that will bite my sitting muscles if mail_location is the same for two users. I'm aware of the shared folders functionality mentioned by Marcus and that will probably be my fallback, if sharing a mail_location is not viable. Same mail_location would just be simpler. Tapio On 24.9.2017 0:34, Peter Chiochetti wrote: > Hello Tapia,...

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 meaningful value for 'homedir' (via password_query's userdb_home), or I can simple return empty...

...'t get the expectet result, still get wrong permissions on new mailboxes. Aki did you also try with %u ? > In /etc/dovecot/conf.d/10-mail.conf follow options are set: > mail_gid = mail > mail_privileged_group = mail > mail_access_groups = mail > mail_location = mdbox:/var/spool/mail/%u On 15.05.2018 13:06, Aki Tuomi wrote: > I have to correct myself. I tested with sdbox now too, and it seems that > using > > mail_location=sdbox:~/Mail > > produces the expected behaviour. mdbox uses same code as sdbox for this, > so it should...

...not set for user. Can't expand ~/ for mail root dir in: ~/ > > Sep 13 11:55:49 imap(a.meyer at nimmini.de): Error: Invalid user > > settings. Refer to server log for more information. > > i see an error here "Error: Invalid user settings" relating to the users > mail_location direcory. > > Is "mail_location" (and not so important "mail_home") defined? In dovecot.conf mail_location = maildir:~/ is set. This works with the system-users defined in the passwd file. I think the query-string f?r MySQL would overwrite this mail_location, right...

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...

Hello, Will I be breaking something if I have two users share the same home and/or mail_location (maildir format) in dovecot? Mail will only be delivered to the primary user, the other would be used every now and then to login via imap (webmail). This would be on a CentOS 7 box running dovecot from the packaging system, i.e. dovecot-2.2.10-8.el7 currently. The reason I'd like to d...

...tem. ?I can send and receive mail using Pine & Mutt. ?But I cannot seem to get dovecot to work with the maildir. ?So I can't check for mail using Dovecot. This is what I'm using for reference: https://help.ubuntu.com/community/Dovecot I believe (not sure actually) the answer is in the mail_location variable for Dovecot. ?This is what I've tried so far: #mail_location = mbox:~/mail:INBOX=/var/mail/%u#mail_location = maildir:/var/mail/%u/Maildir#mail_location = maildir:~/Maildir:INDEX=/var/mail/%umail_location = maildir:/var/mail/%u/Maildir Mail is being delivered and I can send mail o...

IMAP logins via fetchmail are failing on my mailserver root at grelber:/home/esr# tail -f /var/log/mail.err Nov 24 16:56:48 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy Nov 24 16:56:48 grelber dovecot: IMAP(cathy): Fatal: Namespace initialization failed Nov 24 16:57:39 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetectio...