[Dovecot] question about /var/spool/mail/xxx
this is Redhat 6.3 I installed sendmail and dovecot. but sendmail can continue send mail as MTA all mails go to /var/spool/mail this is problem for dovecot. dovecot cannot get it goto dovecot inbox. if setup mailbox poing to /var/spool/mail/%u, it is workable but if set up maildir to somewhere else ,I cannot receive mail by dovecot.
[Dovecot] quota with imapc
Dear dovecot team,
I have set up my mail system with a mail gateway connecting to mail server
using imapc.
Now I need my web mail client to show up the quota info.
I enabled quota plugins in dovecot.conf.
The problem is since all mails reside in the server, the web mail which is
in mail gateway always shows the quota as 0.
Is there any way the plugin will get quota info from the mail server?
I am attaching my conf
## Dovecot configuration file in
mail_uid = imapproxy
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
protocols = imap
##
## imapc settings
##
imapc_host = mailserver.example.com
imapc_port = 143
imapc_ssl = starttls
imapc_ssl_ca_dir = /etc/postfix/certs
##
## auth settings
##
auth_mechanisms = plain login
passdb {
driver = imap
args = host=mailserver.example.com ssl=starttls
ssl_ca_dir=/etc/postfix/certs
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
ssl=starttls
}
userdb {
driver = prefetch
}
mail_plugins = $mail_plugins quota
plugin {
quota = maildir:User quota
quota_rule = *:storage=200M
}
protocol imap {
# Space separated list of plugins to load (default is global
mail_plugins).
mail_plugins = $mail_plugins imap_quota
}
##
## SSL settings
##
ssl = required
disable_plaintext_auth = yes
#verbose_ssl = yes
ssl_cert = /etc/postfix/certs/public_cert.pem
ssl_key = /etc/postfix/certs/private_key.pem
ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL
Greetings.
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/quota-with-imapc-tp42280.html
Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] dovecot 2.2.0 corrupts mailboxes?
On 2013-05-15 9:01 PM, Emmanuel Dreyfus m...@netbsd.org wrote: On Wed, May 15, 2013 at 09:36:54PM +0300, Timo Sirainen wrote: - one of the users was using mutt locally and accessed its mailbox directly without going through dovecot. That shouldn't cause problems if locking was configured the same. I never looked at it, but I assume they both use flock or fcntl Can't help with your actual problem, but... What was it that 'assumption' is supposedly the mother of? ;) -- Best regards, Charles
Re: [Dovecot] Autocreation the home folder
The issue is more with legacy installs being upgraded than with new setups, on the later I might adjust the settings and start using the recoomended layout. On the alternative you suggest, if I understood properly, you are changing the setup to mdbox mail_location = mdbox:%h/mdbox:INDEX=/mail/**indexes/%2Ln/%Ln If there was a method to move automatically the mails (preferibly not moving to mdbox) to a subfolder, I could change to the recommended layout my current install. Otherwise it seems the only current solution is to: 1.- Stop dovecot 2.- Change to recommended layout the config 3.- Via a script move the content to the new location 4.- Start dovecot with the new layout.. Am i right? Joan 2013/5/15 Timo Sirainen t...@iki.fi Dovecot autocreates the mail directory, but apparently it doesn't currently autocreate the home directory if it's located elsewhere. I'm not sure if it's really worth the trouble to change the code to do that. Ideally the mail directory would be under the home directory and this wouldn't be a problem. You could also change your new user creation to trigger mkdiring the user's home. On 15.5.2013, at 15.57, Joan aseq...@gmail.com wrote: Sorry for this bump, but isn't there a better solution to have those folders than to be watching the logs for warnings and recreate them? Regards, Joan 2013/5/14 Joan aseq...@gmail.com Yes, all folder tree has vmail:vmail as the owner, and dovecot can create the folders without issues. I verified that when manually creating those folders, the warnings disappear, the main issue still remains though. When I send the first mail to a user he has this layout: cur dovecot.index.cache dovecot.index.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.5191f7ad maildirsize new tmp Sadly ,there's no home folder, so I've no other option than to create the folder by hand? 2013/5/14 Angel L. Mateo ama...@um.es El 13/05/13 17:50, Steffen Kaiser escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 13 May 2013, Joan wrote: Hi Steffen, that was an error I hadn't spotted (copypasting error). Still after changing mail_home to the proper value (/home/vmail/%d/%n/home) the errors in the logs are the same Am I supposed to create the folders via an external script? Or is there any option to make this automatic. As far as I know, the home directory is not created automatically. You will need to use an external script. I have this config: mail_home = /mail/users/mailboxes/%2Ln/%Ln mail_location = mdbox:%h/mdbox:INDEX=/mail/**indexes/%2Ln/%Ln In my config, mail_home is also auto created (I have dovecot 2.1.16) Do you have any error? Has dovecot user permissions to create direcotories/files under your /var/mail? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 86337
Re: [Dovecot] dovecot 2.2.0 corrupts mailboxes?
On 16.5.2013, at 4.01, Emmanuel Dreyfus m...@netbsd.org wrote: - I experimented dsync replication from another machine that was not accessible through POP/IMAP/SMTP, perhaps this is what caused chaos? That might cause trouble. I tested today and dsync was doing some strange things with mbox. What is the advised setup? Not using mbox, at least with dsync, at least for now.
Re: [Dovecot] quota with imapc
Ok... Thanks for the response. Waiting to see it soon :) -- View this message in context: http://dovecot.2317879.n4.nabble.com/quota-with-imapc-tp42280p42285.html Sent from the Dovecot mailing list archive at Nabble.com.
[Dovecot] [PATCH] example-config: fix to also distribute auth-dict.conf.ext in
Hi, When trying to patch the dovecot 2.2.1 release with latest upstream patches I generated out of the repository, the patch fails to apply, because 'doc/example-config/conf.d/auth-dict.conf.ext' is not distributed within the release tarball. Attached patch should fix the issue. Cheers, Chris From 086de5cf4c7a56cbf3aaa97cedbbea11b403af5e Mon Sep 17 00:00:00 2001 From: Christian Wiese christian.wi...@securepoint.de Date: Thu, 16 May 2013 17:03:37 +0200 Subject: [PATCH] example-config: fix to also distribute auth-dict.conf.ext in releases When trying to patch the dovecot 2.2.1 release with latest upstream patches I generated out of the repository, the patch fails to apply. -%-- patching file doc/example-config/conf.d/auth-deny.conf.ext can't find file to patch at input line 3029 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |diff --git a/doc/example-config/conf.d/auth-dict.conf.ext b/doc/example-config/conf.d/auth-dict.conf.ext |index e6e42db..0be4847 100644 |--- a/doc/example-config/conf.d/auth-dict.conf.ext |+++ b/doc/example-config/conf.d/auth-dict.conf.ext -- No file to patch. Skipping patch. 1 out of 1 hunk ignored -%-- This is related to changeset 16351. see: http://hg.dovecot.org/dovecot-2.2/rev/93bcbf5cabca --- doc/example-config/conf.d/Makefile.am |1 + 1 file changed, 1 insertion(+) diff --git a/doc/example-config/conf.d/Makefile.am b/doc/example-config/conf.d/Makefile.am index 744d202..b7033d4 100644 --- a/doc/example-config/conf.d/Makefile.am +++ b/doc/example-config/conf.d/Makefile.am @@ -4,6 +4,7 @@ exampledir = $(docdir)/example-config/conf.d example_DATA = \ auth-checkpassword.conf.ext \ auth-deny.conf.ext \ + auth-dict.conf.ext \ auth-ldap.conf.ext \ auth-master.conf.ext \ auth-passwdfile.conf.ext \ -- 1.7.10.2
[Dovecot] Ubuntu-12.04-LTS repos with Dovecot-2.2 and Pigeonhole
Hi, I would like to take advantage of new features in Dovecot 2.2 on my servers. But I'm having difficulties to build packages for Ubuntu-12.04-LTS. Does anyone know a repository that has new stable versions for Dovecot and Pigeonhole ? Thanks ! --nbsp; Thiago Henrique adminlinux.com.br
Re: [Dovecot] dovecot 2.2.0 corrupts mailboxes?
On Thu, May 16, 2013 at 06:37:45AM -0400, Charles Marcus wrote: I never looked at it, but I assume they both use flock or fcntl Can't help with your actual problem, but... What was it that 'assumption' is supposedly the mother of? I don't buy that explanation: everything worked fine for years. -- Emmanuel Dreyfus m...@netbsd.org
Re: [Dovecot] dovecot 2.2.0 corrupts mailboxes?
On 2013-05-16 2:25 PM, Emmanuel Dreyfus m...@netbsd.org wrote: On Thu, May 16, 2013 at 06:37:45AM -0400, Charles Marcus wrote: I never looked at it, but I assume they both use flock or fcntl Can't help with your actual problem, but... What was it that 'assumption' is supposedly the mother of? I don't buy that explanation: everything worked fine for years. You miss the point entirely. -- Best regards, Charles
Re: [Dovecot] Quota not working with dict proxy
On Wed, May 15, 2013 9:15 pm, Daniel Parthey wrote:
map {
pattern = priv/quota/storage # dictionary for storage bytes
table = quota # table where to write storage count
username_field = username # username of whom storage should be
counted
value_field = bytes # number of bytes in user mailbox
}
map {
pattern = priv/quota/messages # dictionary for message count
table = quota # table where to write email count
username_field = username # username whose emails should be
counted
value_field = messages# number of messages in user mailbox
}
Regards
Daniel
I think more correctly, value_field is the name of the field in the db.
The 'storage' dictionary will always contain bytes,and the 'messages'
dictionary will always store the number of messages into the db field
named by the 'value_field' parameter.
I would guess that if you changed the pattern to 'shared/quota/messages'
then you could set the shared quota as well.
Re: [Dovecot] question about /var/spool/mail/xxx
Richard Feng@eBay writes: this is Redhat 6.3 I installed sendmail and dovecot. but sendmail can continue send mail as MTA all mails go to /var/spool/mail OK. this is problem for dovecot. dovecot cannot get it goto dovecot inbox. if setup mailbox poing to /var/spool/mail/%u, it is workable I'm guessing that you're sending new mail to mbox formatted files in /var/spool/mail/%u (using dovecot LDA?). but if set up maildir to somewhere else ,I cannot receive mail by dovecot. You lost me. How did you set up maildir to somewhere else? You ought to supply configurations (output of dovecot -n), and log entries of the problem. Joseph Tam jtam.h...@gmail.com
[Dovecot] ACLs - creating new top level folders
Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/curInbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1 /home/mail01/user1/Maildir/.folder1/tmp / ... Assigning an ACL with full access rights for user2 to the folder Inbox works as expected. user2 can create subfolders of Inbox, too. But he can't create a new folder like folder1 parallel to Inbox. Is there a possibility of defining an ACL on the mailbox of user1 itself? Or do we need to create all subfolders beneath Inbox like this is usual with other IMAP servers? Ingo --- /usr/sbin/dovecot -c /etc/dovecot/dovecot-test.conf -n # 1.2.15: /etc/dovecot/dovecot-test.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 base_dir: /var/run/dovecot-test/ log_path(default): /var/log/dovecot-test/error.log log_path(imap): /var/log/dovecot-test/error.log log_path(pop3): /var/log/dovecot-test/error.log log_path(managesieve): /var/log/dovecot-test/managesieve.log info_log_path(default): /var/log/dovecot-test/info.log info_log_path(imap): /var/log/dovecot-test/info.log info_log_path(pop3): /var/log/dovecot-test/info.log info_log_path(managesieve): /var/log/dovecot-test/managesieve.log protocols: imap imaps pop3 pop3s managesieve listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 listen(managesieve): *:12000 ssl_listen(default): *:10943 ssl_listen(imap): *:10943 ssl_listen(pop3): *:10995 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/certs/imap-cert.pem ssl_key_file: /etc/ssl/private/imap-key.pem shutdown_clients: no login_dir: /var/run/dovecot-test//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_max_processes_count: 4096 max_mail_processes: 4096 verbose_proctitle: yes mail_location: maildir:~/Maildir:INDEX=/srv/dovecot/index/%u:CONTROL=/srv/dovecot/control/%u maildir_copy_preserve_filename: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 1024 mail_plugins(default): fts fts_squat acl imap_acl mail_plugins(imap): fts fts_squat acl imap_acl mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_lock_session(managesieve): no pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu pop3_uidl_format(managesieve): %08Xu%08Xv namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: Other Users/%%u/ location: maildir:%%h/Maildir:INDEX=/srv/dovecot/index/%%u:CONTROL=/srv/dovecot/control/%%u list: children lda: postmaster_address: postmaster@... mail_plugins: sieve acl quota_full_tempfail: yes auth_socket_path: /var/run/dovecot-test/auth-master log_path: /var/log/dovecot-test/deliver.log info_log_path: /var/log/dovecot-test/deliver.log auth default: cache_size: 1024 cache_negative_ttl: 0 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@~ master_user_separator: * debug: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd.masterusers pass: yes master: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd passdb: driver: pam userdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd socket: type: listen client: path: /var/run/dovecot-test/auth-client mode: 384 user: vmail master: path: /var/run/dovecot-test/auth-master mode: 384 user: vmail plugin: acl: vfile acl_shared_dict: file:/srv/dovecot/lib/shared-mailboxes sieve: ~/.dovecot.sieve sieve_dir: ~/.pysieved fts: squat fts_squat: partial=4 full=10
