- dovecot - dovecot.org

Re: [Dovecot] Shared Mailboxes with VirtualUsers and mail_location retrieved from ldap
by mailing lists 08 Sep '11

08 Sep '11

Hello, On 09/07/2011 07:22 PM, Timo Sirainen wrote: > On 6.9.2011, at 14.27, mailing lists wrote: >> 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 = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home > > Are home dirs and mail dirs related in any way? The only way you can get it working is by using home dirs, e.g.: > > user_attrs = mailbox=home=/var/maildir/%$ yes, my virtual users have separate directories for home and mail. Their locations are stored in ldap attributes (with random generated paths), so a flat scheme like /var/maildr/%%u isn't valid. for typical (virtual) users the location returned looks like: Sep 8 12:48:33 imap1 dovecot: auth: Debug: ldap(user012,::1): result: mailbox(mail=maildir:/var/maildir/%$)=vol06/1/15/user012 homeFilter(home)=/var/mailfilter/vol06/1/15/user012 ... Sep 8 12:54:50 imap1 dovecot: imap(user012): Debug: maildir++: root=/var/maildir/vol06/1/15/user012, index=, control=, inbox=/var/maildir/vol06/1/15/user012, alt= > Then in dovecot.conf: > > mail_location = maildir:~/ > >> namespace { >> type = shared >> separator = / >> prefix = shared/%%u/ >> subscriptions = no >> list = children > > location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u this is that I see in logs and not shared folders are seen by imap clients: Sep 8 12:57:11 imap1 dovecot: imap(user012): Debug: Namespace : type=shared, prefix=shared.%u., sep=., inbox=no, hidden=no, list=children, subscriptions=no location=maildir:%h/Maildir:INDEX=~/Maildir/shared/%u Sep 8 12:57:11 imap1 dovecot: imap(user012): Debug: shared: root=/var/run/dovecot/, index=, control=, inbox=, alt= Sep 8 12:57:11 imap1 dovecot: imap(user012): Debug: acl: initializing backend with data: vfile I fail to understand how %%u is retrieved from ldap... /----------/ # dovecot -n # 2.0.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ disable_plaintext_auth = no mail_debug = yes mail_fsync = always mail_gid = 5000 mail_location = maildir:~/ mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes location = prefix = INBOX. separator = . } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared.%%u. separator = . subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/maildir/shared-mailboxes sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap ssl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 100 mail_plugins = acl imap_acl autocreate }

2 1

Re: [Dovecot] is it necessary lmtp and director to avoid index corruption in mail delivery?
by mailing lists 08 Sep '11

08 Sep '11

JF, thank you for the reply. I'm just curious how to big players fix this problem, which seems impact systems with shared storage. Have a nice day. On 09/07/2011 12:59 PM, Jan-Frode Myklebust wrote: > On Wed, Sep 07, 2011 at 11:26:28AM +0100, mailing lists wrote: >> Hello all, >> If I have several postfix/dovecot-lda boxes with shared nfs storage, >> how director helps in this scenario? > > The director can help by directing each unique user to the same backend > server for each delivery, which should give you better performance > (indexes cached in memory on only one machine instead of on all, > inotify will work for IMAP NOTIFY), and also avoid some apparent race > conditions that has lead to index corruption when several nodes are > writing to the same mailbox at the same time. > >> is it necesary to use lmtp instead of dovecot-lda? > > Yes. > > >> With postfix/dovecot-lda boxes incoming mail happens at the smtp layer >> but director redirects are working in the lmtp/imap/pop3 layer. > > Right. > > With LMTP you can have dovecot listening on the network (port 24/tcp) > for incoming mail. No need for postfix on the backend mailstorage > servers. > > Our setups has been: > > Mailgw[1-14] ---smtp--> dovecot-server[1-5] (postfix + dovecot/lda) > > and used MX priorities to make all deliveries go to the same > dovecot-server with the others as backup. > > $ dig mx deliver.example.com +short > 10 dove2.example.com. > 15 dove3.example.com. > 20 dove4.example.com. > 25 dove5.example.com. > 5 dove1.example.com. > > > Now I'm moving towards: > > Mailgw[1-14] ---lmtp--> dovecot-server[1-5] (dovecot/lmtp) > > but worry that the index corruption might hit me again.. Ideally > I want: > > Mailgw[1-14] ---lmtp--> directors --lmtp--> dovecot-server[1-5] (dovecot/lmtp) > > but lmtp-proxying seems to have bugs (ref: my latest mails to this > list). > > > -jf

1 0

[Dovecot] limit number of simultaneous lmtp deliveries ?
by Jan-Frode Myklebust 08 Sep '11

08 Sep '11

We have quite a few frontend mail gateways that deliver incoming email trough our dovecot director (lmtp proxy) to the backend lmtp servers, and are seeing this logged on the frontend mail gateways: Sep 5 10:51:56 mailgw1 postfix/lmtp[23443]: 0E2F41C01A: to=<me(a)example.com>, relay=loadbalancers.example.com[192.168.42.15]:24, delay=61, delays=0.02/0.3/31/30, dsn=4.4.0, status=deferred (host loadbalancers.example.com[192.168.42.15] said: 451 4.4.0 Remote server not answering (DATA output timeout) (in reply to end of DATA command)) It's a bit unclear to me if this leads to duplicate deliveries, or just delayed deliveries, but -- is there any way to limit the number of simultanous deliveries on either the dovecot director or the backend lmtp-servers ? Will "process_limit=10" work for "service lmtp"? -jf

2 4

[Dovecot] test
by Adrian Stoica 08 Sep '11

08 Sep '11

Hello i use dovecot 2.0.14 , with exim 4.76 using dovecot-lda. We have the following problem: when I receive mail from the site http://www.transfer.ro, which is a file transfer site, most emails appear to be empty. Empty rows appear in email body slipped through the existing, and this makemy mail client to show me an empty mail. You can see the content only by viewing the message source. instead of "- np4e68592849da7 Content-type: text / plain, charset = utf-8 " appear "- np4e68592849da7 Content-type: text / plain, charset = utf-8 " , and that blank line spoil everything. You can check if there is somethingwrong ?

2 2

[Dovecot] ManageSieve with SSL/TLS only
by Karol Babioch 08 Sep '11

08 Sep '11

Hi, I'm quite new to Dovecot and ManageSieve, so probably I've missed something, although I couldn't find any hints in the wiki. I'm interested in running ManageSieve with SSL/TLS only. So is there any way to reject any non encrypted connections? I couldn't find any parameter for this purpose. I'm currently using dovecot 1.2.15 provided with Debian Squeeze, but I couldn't find any parameter in the 2.0 branch neither. Best regards, Karol Babioch

2 1

[Dovecot] Shared Mailboxes with VirtualUsers and mail_location retrieved from ldap
by mailing lists 07 Sep '11

07 Sep '11

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 = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home creating a namespace like the below one for shared mbx throw a lot of errors: namespace { type = shared separator = / prefix = shared/%%u/ subscriptions = no list = children #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u location = mailbox=mail=maildir:/var/maildir/%$ } I would like to hear if anyone has this configuration running. Thank you. /--------------/ uris = ldap://ldap.example.com dn = cn=user,ou=People,dc=example,dc=com dnpass = secret sasl_bind = no tls = no auth_bind = yes ldap_version = 3 base = dc=example,dc=com deref = never scope = subtree user_attrs = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home user_filter = (&(objectClass=CourierMailAccount)(uid=%u)) pass_filter = (&(objectClass=CourierMailAccount)(uid=%u)) # dovecot -n # 2.0.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ disable_plaintext_auth = no mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { list = children location = mailbox=mail=maildir:/var/maildir/%$ prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace { inbox = yes location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap ssl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 100 mail_plugins = acl imap_acl autocreate }

2 1

[Dovecot] Quota fs (ignore mount)
by Peter Ignatov 07 Sep '11

07 Sep '11

Hi, I set "quota: fs:INBOX:noenforcing:mount=/var/spool/mail", but receive: "fs quota add storage dir = /home/pit/mail"... Why ? In fstab: /dev/mapper/mpath1p1 /var/spool/mail ext2 usrquota 0 0 In dovecot.log: Sep 06 15:02:00 pop3-login: Info: Login: user=<pit>, method=PLAIN, rip=192.168.3.10, lip=192.168.6.3, TLS Sep 06 15:02:00 POP3(pit): Info: Loading modules from directory: /usr/lib64/dovecot/pop3 Sep 06 15:02:00 POP3(pit): Info: Module loaded: /usr/lib64/dovecot/pop3/lib10_quota_plugin.so Sep 06 15:02:00 POP3(pit): Info: Effective uid=500, gid=500, home=/home/pit Sep 06 15:02:00 POP3(pit): Info: Quota root: name=INBOX backend=fs args=noenforcing:mount=/var/spool/mail Sep 06 15:02:00 POP3(pit): Info: Quota rule: root=INBOX mailbox=* bytes=10485760 messages=0 Sep 06 15:02:00 POP3(pit): Info: Quota warning: bytes=9961472 (95%) messages=0 command=/usr/local/bin/quota-warning.sh 95 Sep 06 15:02:00 POP3(pit): Info: mbox: data=~/mail:INBOX=/var/spool/mail/pit Sep 06 15:02:00 POP3(pit): Info: fs: root=/home/pit/mail, index=, control=, inbox=/var/spool/mail/pit Sep 06 15:02:00 POP3(pit): Info: fs quota add storage dir = /home/pit/mail Sep 06 15:02:00 POP3(pit): Info: fs quota block device = /dev/cciss/c0d0p3 Sep 06 15:02:00 POP3(pit): Info: fs quota mount point = / Sep 06 15:02:00 POP3(pit): Info: fs quota mount type = ext3 Sep 06 15:02:01 POP3(pit): Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/2, size=1249 dovecot --version 1.2.17 dovecot -n # 1.2.17: /etc/dovecot.conf # OS: Linux 2.6.18-274.el5.asp121 x86_64 Red Hat Enterprise Linux Server release 5.6 (Tikanga) log_path: /var/log/dovecot.log protocols: pop3 pop3s listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login verbose_proctitle: yes mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mail_debug: yes mail_executable: /usr/libexec/dovecot/pop3 mail_plugins: quota mail_plugin_dir: /usr/lib64/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: fs:INBOX:noenforcing:mount=/var/spool/mail quota_rule: *:storage=10240 quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95

2 1

[Dovecot] Sieve "header :value" test does not work
by Tom Hendrikx 07 Sep '11

07 Sep '11

hi, After following some examples and searching for sieve samples in this ml history, I'm quite sure that the following sieve snippet should give no surprises: if header :value "ge" :comparator "i;ascii-numeric" "X-Header-Name" "0.99" { /* do something */ } However the Pigeonhole Sieve 0.2.3 on dovecot 2.0.14 gives me following error: test: line 3: error: unknown tagged argument ':value' for the header test (reported only once at first occurence). test: error: validation failed. What obvious mistake am I failing to see here? -- Tom

2 5

[Dovecot] is it necessary lmtp and director to avoid index corruption in mail delivery?
by mailing lists 07 Sep '11

07 Sep '11

Hello all, If I have several postfix/dovecot-lda boxes with shared nfs storage, how director helps in this scenario? is it necesary to use lmtp instead of dovecot-lda? With postfix/dovecot-lda boxes incoming mail happens at the smtp layer but director redirects are working in the lmtp/imap/pop3 layer.

2 1

Re: [Dovecot] error in logs, but system appears to work
by Joseph Tam 07 Sep '11

07 Sep '11

Chris Hoogendyk writes: > So, looking at my other system that has been running dovecot for over a > year, I see that the entries are mostly 0600, but there are a few 0660. > The system I was just implementing has mostly 0660, but some 0600. We > had seen occasional similar errors on the other system. Been there, done that. Timo already gave an explanation of why 0600 gets rid of the problem. I'll add a reminder that you'll need to track down the reason why mailboxes are created user:mail/0660 in the first place. It's usually done by the LDA when creating a brand new mailbox (for example, Solaris's mail.local). If you've replaced your LDA with Dovecot's deliver, then this won't be a problem anymore. You may also have to scour your userbase's personal mail collection for mailboxes that has 1) mode 0660, and 2) group membership the user is not a part of, and fix up the permissions. Such a thing could happen if you've reassigned a user's GID. Joseph Tam <jtam.home(a)gmail.com>

1 0