Re: [Dovecot] Dovecot performance under high load (vs. Courier)
Am 27.06.2012 07:44, schrieb Wojciech Puchar: Timo: I'm not sure if you are saying that all client-side caching is wrong. If so, I'm going to disagree with you, especially when dealing with more complex data structures. it is always good - on WAN links. Hi, i dont wanna flame into this thread, cause its heavy tec stuff which i dont really fit in but for some webmail you can use http://imapproxy.org/ its running here fine with squirrelmail and roundcube -- Best Regards MfG Robert Schetterer
Re: [Dovecot] Dovecot performance under high load (vs. Courier)
Hi, i dont wanna flame into this thread, cause its heavy tec stuff which i dont really fit in but for some webmail you can use http://imapproxy.org/ the discussion was about if running proxy at all make sense. Proxies are to reduce traffic or server load by avoiding repetitive requests. With dovecot it's unlikely proxy itself will be faster, so second reason doesn't exist. With same computer or fast lan or virtual lan (==normal way of running webmail) first reason doesn't exist.
Re: [Dovecot] Dovecot performance under high load (vs. Courier)
Am 27.06.2012 09:32, schrieb Wojciech Puchar: Hi, i dont wanna flame into this thread, cause its heavy tec stuff which i dont really fit in but for some webmail you can use http://imapproxy.org/ the discussion was about if running proxy at all make sense. Proxies are to reduce traffic or server load by avoiding repetitive requests. With dovecot it's unlikely proxy itself will be faster, so second reason doesn't exist. With same computer or fast lan or virtual lan (==normal way of running webmail) first reason doesn't exist. Hi, sorry ,only my meaning, beside coding layout questions about dovecot etc which is clearly not my case for questions like: does a proxy make sense there will never be an uni right answer the answer may ever depend on what fits best at your side general setup/layout -- Best Regards MfG Robert Schetterer
[Dovecot] last hope... public namespace and directory structure
hello,
I would like to migrate to dovecot, but I have a problem with a public
namespace declaration:
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-2-amd64 x86_64 Debian wheezy/sid
And here are the relevant parts from the configuration:
namespace {
location = maildir:/var/mail/vhosts/%d/public
prefix = Public.
separator = .
type = public
}
namespace inbox {
prefix =
separator = .
subscriptions = yes
type = private
}
I assume that all folders under ./public/ are public mailboxes. The public
folder itself is not a maildir, but contains
the team mailboxes i.e.
./public/.sales/
./public/.service/
./public/.purchase/
The file passwd for those 3 samples looks like this:
sales@$DOMAIN::5000:5000::/var/mail/vhosts/$DOMAIN/public/.sales
service@$DOMAIN::5000:5000::/var/mail/vhosts/$DOMAIN/public/.service
purchase@$DOMAIN::5000:5000::/var/mail/vhosts/$DOMAIN/public/.purchase
Note: All other users have mail_location /var/mail/vhosts/%d/%n
Now a have the following problem: If I login in as user sales and create a
folder foo and in there a folder bar.
The directory structure is:
./public/. sales /.foo and /public/. sales /.foo.bar
thats exactly what I´m expect.
Now I logon as normal user. I can see the namespace Public with the sales
mailbox
but no subfolder foo or foo.bar.
Now I create also the folders foo and in there bar, but the result is
to
me unexpected ;-):
./public/. sales
./public/. sales.foo
./public/. sales.foo.bar
Looking forward to your comment,
Daniel
Re: [Dovecot] started with dovecot sieve
Am 2012-06-26 22:10, schrieb Daniel Parthey: Rolf wrote: Am 2012-06-25 23:59, schrieb Daniel Parthey: Hi Rolf, Rolf wrote: Jun 25 20:22:54 rolf14 dovecot: lda(rolf): Error: setegid(privileged) failed: Operation not permitted Doesn't lda(rolf) mean it is being executed under user rolf, not root or dovecot? could be. However, following your mail I tried several alternatives for grouping, made the user itself part of mail group, made postfix and dovecot part of the users real group, made all part of roots real group, made the users part of postfix and dovecot real group ... I could have made failures in trying all this combinations but the failure remained in any case. (I switched all back for security reasons, the failure is still there.) How exactly do you invoke lda from your /etc/postfix/master.cf? these are my lines from /etc/postfix/main.cf: #mailbox_command = procmail -a $EXTENSION mailbox_command = /usr/lib/dovecot/deliver if I switch procmail back on the input gets delivered and I can see them using roundcube as a client for dovecot. You might also try to use LMTP via TCP to deliver mails from postfix to dovecot to work around any permission problems. LMTP would be new to me and I fear just other hard-to-understand configuration topics. What I did as a workaround is to have a last rule in each .dovecot.sieve: fileinto rest. It works and this way the INBOX is no longer needed. I have installed dovecot and docecot-sieve by Debians aptitude You don't seem to be the only one with these problems, see Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626130 Do not understand how they have solved the problem. Changing 0660 to 0600 for the /var/mail/user mboxes (with user:mail for user:group) seems not to be a logical solution - have not tried that.
Re: [Dovecot] started with dovecot sieve
Am 2012-06-26 23:47, schrieb Daniel Parthey: Rolf wrote: Jun 25 20:22:54 rolf14 dovecot: lda(rolf): Error: setegid(privileged) failed: Operation not permitted Manual page man 2 setegid states that Yes, thank you Daniel for pointing me to this subjects. Now I got a bit a deeper understanding how a file gets executed. My problem is that I do not exactly know from the error message who is starting what by which effective group id and to what group id it tries to switch. All guessing did not lead to a result. I tried: postfix is starting deliver with the effective group id postfix and wants to set the group id either to mail or to rolf. But no success.
Re: [Dovecot] [PATCH] GSSAPI authorization and virtual users
On Tue, 2012-03-06 at 18:12 +, Sam Morris wrote: On Mon, 2012-03-05 at 20:52 +0200, Timo Sirainen wrote: On 5.3.2012, at 20.45, Sam Morris wrote: 3. The credentials lookup triggers an info log message saying that credentials for GSSAPI were requested, but we have only (e.g.) MD5-CRYPT. The authplugin doesn't actually want the credential, but I think that the only way the authplugin can trigger a passdb lookup is by requesting it. I'll look at the rest more closely later, but this should be an easy fix: request instead of GSSAPI. Thanks for pointing that out. Here's a newer version of the patch with that change. I also realised that the gss_buffer is not required in the code that runs once the passdb lookup is complete, so I removed the code that stashes it in struct gssapi_auth_request. I finally looked into this and did some changes. Does it still work? :) http://hg.dovecot.org/dovecot-2.2/rev/183adc90781c
Re: [Dovecot] Problem with 'doveadm mailbox status -t' reporting cumulative vsizes after upgrading from v2.0.16 to v2.1.7
On Mon, 2012-06-18 at 18:35 +0100, Jase Thew wrote: The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum total of mailboxes sizes for each user, so that vsize just constantly increases as it iterates over each user. Fixed: http://hg.dovecot.org/dovecot-2.1/rev/d8d587bd5a29
Re: [Dovecot] pop3c_master_user
On Tue, 2012-06-19 at 00:41 +0200, Martin Schitter wrote: the configuration keyword pop3c_master_user mentioned in the dsync migration documentation (http://wiki2.dovecot.org/Migration/Dsync) does not work for dovecot 2.1.7. a config line like: pop3c_master_user = cyrus will produce this error: doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 33: Unknown setting: pop3c_master_user Added: http://hg.dovecot.org/dovecot-2.1/rev/06ba409a63d3
Re: [Dovecot] director map and mysql
On Wed, 2012-06-20 at 14:40 +1100, Костырев Александр Алексеевич wrote: but what mechanisms do I have if I want certain user to be always proxied to certain host, but if that host is down, to redirect him to another? You'll have to mark the host down in SQL, and change your SQL query to return something else for the host value when that host is down (either another host or NULL to let director handle it).
Re: [Dovecot] doveadm proxy kick in director setups
On Thu, 2012-06-21 at 10:48 -0400, Tom Pawlowski wrote: Something I noticed on a 2.1.7 director test cluster (two directors, three backends): 'doveadm proxy kick user' will kick all connections for that user on that director only. Any additional connections on other directors will remain active unless the command is run on all directors. Are the proxy and director sub-commands intended to be separate and distinct in their operation? If so, then this makes sense, as a proxy isn't necessarily a director. They are separate, yes. Are there any plans for a proxy kick equivalent that would work across directors? With director it would be possible to kick all users that match the user's 32bit hash. If there are hash collisions then it would kick also other users.. Another possibility would be to create something that allows running the same doveadm command in all directors, but ssh pretty much can do that already. :)
Re: [Dovecot] pop3-throttle
On Sat, 2012-06-23 at 07:04 +0200, Emmanuel Dreyfus wrote:
Hello
I am having a hard time with users using POP while leaving mailboxes
of several gigabyte cumulated. This causes a lot of disk I/O and kills
performancs for everyone. I try to encourage people migrating to
IMAP, but that migration will take some time, and therefore I am looking
for alterantive ways to workaround the problem.
What mailbox format do you use? This shouldn't be a problem with for
example mdbox, probably not with sdbox either and with mbox/maildir
there are settings that can improve this.
Or are you not talking about opening the mailbox, but about clients
redownloading all the mails all the time?
I found pop3-throttle-plugin.c, which seems a smart way to solve the
problem, unfortunately it comes with no documentation. I was able to
build it and load it, bu itsays nothing in the logs. Is there any
doc somewhere? Any advices on how to set it up?
It's about allowing clients to see only X new mails per Y time. But I
don't see how that would help with your problem if that's related to old
mails.
Anyway, quick docs:
touch /etc/dovecot/pop3-throttle-enabled to enable the throttling
plugin {
pop3_throttle_max_msgs = 10
pop3_throttle_max_kbytes = 1024
}
Which allows a single user to see max 10 new messages or max 1 MB of new
messages per 15 minutes, whichever limit comes first. After 15 minutes
more messages become visible again to reach the limit. The 15 minute
limit is configurable by recompiling:
#define POP3_THROTTLE_STATE_RESET_SECS (60*15)
Re: [Dovecot] Maildir Seen Flags not heeded when dovecot-shared present
On 26 Jun 2012, at 21:49, Timo Sirainen wrote: So you don't want shared seen flags? You can simply not create dovecot-shared file nowadays. It's not necessary. The only other purpose for it was as the template for file permissions, but those are nowadays taken from the maildir itself: http://wiki2.dovecot.org/SharedMailboxes/Permissions Timo, Thanks for pointing me in the right direction . . I started with Dovecot back in the pre-v1 days and used dovecot-shared from when it first helped with permissions and things -- never actually minded about seen flags back then. So, I've always thought of dovecot-shared as being primarily about making the permissions work, and hadn't realised things have been steadily changing in that regard. So, I now have Dovecot on both CentOS 5.5 CentOS 6, which means v1 v2 . . unfortunately though, the CentOS 5.5 default package is 1.0.x and that means I miss out on 1.1+ features there, as well as the improved handling of file permissions in 1.2 that I now see after scrutinising the differences . . At least I know exactly where the problems are now, thanks! ~ James.
[Dovecot] Removing specific entry in user/auth cache
Hi, We have dovecot configured with auth cache. Is there any way to remove a specific entry (not all) from this cache? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica_(___V Tfo: 868887590 Fax: 86337
Re: [Dovecot] Hardware infrastructure for email system
On 23/06/2012 13:20, Wojciech Puchar wrote: it is already enormous overshoot in hardware specs. And i do not really catch why you have 4 in parallel servers. And finally i cannot understand this dividing of servers just to merging it back using VMWare. because it is a big difference if you have anything in a single machine or splittet in virtual machines - you can move them at runtime to different hosts and if you run out of ressources ok - for me it is just likes. You have higher change to have the need to move at the first place doing this :) Actually, I'm a huge buyer of virtualisation. There is *no other* way that people should be running their servers right now... (hand waving sweeping generalisation - obviously add context, etc, before taking literally). There are various types of virtualisation solution and they have pros and cons, but I think there is close to zero reason not to use some kind of virtualisation option for all new deployments. Probably he is using something clever like vmware esx - I like the theory there where you can literally fail over a running machine to new hardware, without even stopping it running, very neat. I personally use linux-vservers which are almost identical to running on bare metal server (it's kind of a fancy form of chroot), this means I don't have commercial grade failover, but it only takes 5-15 seconds to reboot each container, so that's an acceptable downtime for my requirements. Good luck! Ed W
Re: [Dovecot] pop3-throttle
On Wed, Jun 27, 2012 at 12:50:20PM +0300, Timo Sirainen wrote: What mailbox format do you use? This shouldn't be a problem with for example mdbox, probably not with sdbox either and with mbox/maildir there are settings that can improve this. This is mbox. Or are you not talking about opening the mailbox, but about clients redownloading all the mails all the time? I don't think the client downloads the whole mailbox each time. It takes so long on a 1 GB mbox that the users would have complained. However, I can see a lot of disk I/O activity for pop daemon operating on the bigger mbox (easy to spot looking at the process uid) -- Emmanuel Dreyfus m...@netbsd.org
Re: [Dovecot] pop3-throttle
On 27.6.2012, at 14.55, Emmanuel Dreyfus wrote: On Wed, Jun 27, 2012 at 12:50:20PM +0300, Timo Sirainen wrote: What mailbox format do you use? This shouldn't be a problem with for example mdbox, probably not with sdbox either and with mbox/maildir there are settings that can improve this. This is mbox. Or are you not talking about opening the mailbox, but about clients redownloading all the mails all the time? I don't think the client downloads the whole mailbox each time. It takes so long on a 1 GB mbox that the users would have complained. However, I can see a lot of disk I/O activity for pop daemon operating on the bigger mbox (easy to spot looking at the process uid) Try mbox_very_dirty_syncs=yes
Re: [Dovecot] Removing specific entry in user/auth cache
On 27.6.2012, at 14.10, Angel L. Mateo wrote: We have dovecot configured with auth cache. Is there any way to remove a specific entry (not all) from this cache? Nope. What do you need it for?
Re: [Dovecot] permissions on auth-userdb
On 23.6.2012, at 13.34, Charles Marcus wrote: It would be nice if there were a wiki page specifically describing how permissions should be set for all of the services/directories that dovecot uses. Even better would be a dovecot/doveconf command that would test the permissions and, if possible, even fix them (like the postfix 'set-permissions' command)... The problem with those is that it depends on the installation. Each user may need different permissions. Many installations don't have a way to list users to even do a userdb lookup. I guess it would be possible to write such a tool for specific installations where it could work, but it wouldn't work everywhere..
Re: [Dovecot] permissions on auth-userdb
On 2012-06-27 8:29 AM, Timo Sirainen t...@iki.fi wrote: On 23.6.2012, at 13.34, Charles Marcus wrote: It would be nice if there were a wiki page specifically describing how permissions should be set for all of the services/directories that dovecot uses. Even better would be a dovecot/doveconf command that would test the permissions and, if possible, even fix them (like the postfix 'set-permissions' command)... The problem with those is that it depends on the installation. Each user may need different permissions. Many installations don't have a way to list users to even do a userdb lookup. I guess it would be possible to write such a tool for specific installations where it could work, but it wouldn't work everywhere. Hmmm... I wonder how postfix does it then... maybe it doesn't have as many potential variations I guess? Is there maybe just a basic/standard set of permissions that can work for many installations, then have a way to detect non-standard installs and just provide a link to a wiki page describing things in more detail? Is there a wiki page for this already? I didn't find one... -- Best regards, Charles
Re: [Dovecot] Mail migration to dovecot with doveadm backup
Hi, if i delete the home directory and all content below an existing account u...@example.org. Then run: /usr/bin/doveadm quota recalc -u u...@example.org and afterwards: /usr/bin/doveadm -o imapc_user=u...@example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -D -v backup -R -f -u u...@example.org imapc: i get the following errors: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_list_backend (this is usually intentional, so just ignore this message) doveadm(u...@example.org): Debug: auth input: u...@example.org home=/mail/dovecot/example.org/user uid=501 gid=123 quota_rule=*:bytes=2000M:messages=0 doveadm(u...@example.org): Debug: Added userdb setting: plugin/quota_rule=*:bytes=2000M:messages=0 doveadm(u...@example.org): Debug: Effective uid=501, gid=123, home=/mail/dovecot/example.org/user doveadm(u...@example.org): Debug: Quota root: name=User quota backend=dict args=:proxy::quota doveadm(u...@example.org): Debug: Quota rule: root=User quota mailbox=* bytes=2097152000 messages=0 doveadm(u...@example.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(u...@example.org): Debug: Quota warning: bytes=1992294400 (95%) messages=0 reverse=no command=quota-warning 95 u...@example.org doveadm(u...@example.org): Debug: Quota warning: bytes=1677721600 (80%) messages=0 reverse=no command=quota-warning 80 u...@example.org doveadm(u...@example.org): Debug: dict quota: user=u...@example.org, uri=proxy::quota, noenforcing=0 doveadm(u...@example.org): Debug: fs: root=/mail/dovecot/example.org/user/mail, index=, control=, inbox=, alt= doveadm(u...@example.org): Debug: Namespace : Using permissions from /mail/dovecot/example.org/user/mail: mode=0700 gid=-1 dsync(u...@example.org): Debug: Effective uid=501, gid=123, home=/mail/dovecot/example.org/user dsync(u...@example.org): Debug: Quota root: name=User quota backend=dict args=:proxy::quota dsync(u...@example.org): Debug: Quota rule: root=User quota mailbox=* bytes=2097152000 messages=0 dsync(u...@example.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 dsync(u...@example.org): Debug: Quota warning: bytes=1992294400 (95%) messages=0 reverse=no command=quota-warning 95 u...@example.org dsync(u...@example.org): Debug: Quota warning: bytes=1677721600 (80%) messages=0 reverse=no command=quota-warning 80 u...@example.org dsync(u...@example.org): Debug: dict quota: user=u...@example.org, uri=proxy::quota, noenforcing=0 dsync(u...@example.org): Debug: imapc: root=, index=, control=, inbox=, alt= dsync(u...@example.org): Debug: imapc(local-mailbox:18143): Looking up IP address dsync(u...@example.org): Debug: imapc(local-mailbox:18143): Connecting to 10.129.3.196:18143 dsync(u...@example.org): Debug: imapc(local-mailbox:18143): Server capabilities: IMAP4 IMAP4rev1 AUTH=LOGIN ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE dsync(u...@example.org): Debug: imapc(local-mailbox:18143): Authenticating as u...@example.org dsync(u...@example.org): Debug: imapc(local-mailbox:18143): Authenticated successfully dsync(u...@example.org): Error: Can't delete mailbox INBOX: INBOX can't be deleted. dsync(u...@example.org): Debug: Namespace : /mail/dovecot/example.org/user/mail/mailboxes/Trash doesn't exist yet, using default permissions dsync(u...@example.org): Debug: Namespace : Using permissions from /mail/dovecot/example.org/user/mail: mode=0700 gid=-1 dsync(u...@example.org): Debug: Namespace : /mail/dovecot/example.org/user/mail/mailboxes/Sent doesn't exist yet, using default permissions dsync(u...@example.org): Debug: Namespace : Using permissions from /mail/dovecot/example.org/user/mail:
Re: [Dovecot] dict Panic after upgrade to 2.1.7
hallo,
after upgrade my mailsystem to dovecot version 2.1.7, dovecot doesn't work
properly. something went wrong in dict service connecting the postgres
backend. that happens not on every connection. the db connection data are
correct, no difference connecting via tcp or linux socket.
dovecot log entries:
Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84
(driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY ||
db-
cur_result == NULL)
Jun 23 23:19:10 mx dovecot: dict: Error: Raw backtrace:
/usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(+0x4478a)
[0x7ffc7d8e578a] -
/usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(+0x447d6)
[0x7ffc7d8e57d6] -
/usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(i_error+0)
[0x7ffc7d8bc5ef] - dovecot/dict() [0x40a9a6] - dovecot/dict() [0x40aa01]
- dovecot/dict() [0x40be43] - dovecot/dict() [0x409474] -
dovecot/dict(sql_db_cache_deinit+0x20) [0x4089d0] -
dovecot/dict(main+0x169) [0x4059f9] -
/lib/libc.so.6(__libc_start_main+0xfd) [0x7ffc7d335c8d] - dovecot/dict()
[0x404b59]
Jun 23 23:19:10 mx dovecot: dict: Fatal: master: service(dict): child 13812
killed with signal 6 (core dumps disabled)
Jun 23 23:23:09 mx dovecot: dict: Error: dict sql iterate failed: Not
connected to database
Jun 23 23:23:09 mx dovecot: pop3(x...@yyy.zz): Error: acl: dict iteration
failed, can't update dict
Jun 23 23:23:09 mx dovecot: dict: Error: dict sql iterate failed: Not
connected to database
Jun 23 23:23:09 mx dovecot: pop3(x...@yyy.zz): Error: acl: dict iteration
failed, can't update dict
Jun 23 23:23:17 mx dovecot: dict: Error: dict sql lookup failed: Not
connected to database
Jun 23 23:23:17 mx dovecot: imap(x...@yyy.zz): Error: Internal quota
calculation error
Jun 23 23:23:19 mx dovecot: dict: Error: dict sql lookup failed: Not
connected to database
Jun 23 23:23:40 mx dovecot: dict: Error: dict sql lookup failed: Not
connected to database
maybe i have missconfigured the dovecot system, but i don't find the
mistake. can anybody give me a hint ?
It seem's, that these errors occcures, if acl support ist activated. i
deactivated acl support last night for a while, and no such errors occured. I
can't make long term test, because that is a produktion system and i switched
back to version 2.0.9, which runs with acl support but without that errors .
bw
Christoph
- doveconf -n
# 2.1.7: /usr/local/dovecot-2.1.7/etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-vserver-amd64 x86_64 Debian 6.0.5 ext3
auth_mechanisms = plain login digest-md5 cram-md5 apop
auth_socket_path = /var/run/dovecot/auth-userdb
auth_username_translation = %@
auth_verbose = yes
auth_verbose_passwords = plain
base_dir = /var/run/dovecot/
dict {
acl = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext
expire = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext
quota = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext
}
disable_plaintext_auth = no
first_valid_gid = 5000
first_valid_uid = 5000
hostname = mx.warenform.de
last_valid_gid = 5000
last_valid_uid = 5000
listen = 178.63.63.151 2a01:4f8:121:c5::2
mail_gid = vmail
mail_location = maildir:/var/vmail/%d/%n/Maildir
mail_plugins = autocreate quota expire acl
mail_uid = vmail
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 ihave
namespace {
list = children
location = maildir:/var/vmail/%%d/%%n/Maildir:INDEX=~/Maildir/shared/%%u
prefix = shared/%%u/
separator = /
subscriptions = no
type = shared
}
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Spam {
special_use = \Junk
}
mailbox Trash {
special_use = \Trash
}
prefix =
separator = /
type = private
}
passdb {
args = /usr/local/dovecot/etc/dovecot/sql-connect.conf.ext
driver = sql
}
plugin {
acl = vfile
acl_shared_dict = proxy::acl
autocreate = Spam
autocreate2 = Sent
autocreate3 = Trash
autocreate4 = Drafts
autosubscribe = Spam
autosubscribe2 = Sent
autosubscribe3 = Trash
autosubscribe4 = Drafts
expire = Trash
expire2 = Trash.*
expire3 = Spam
expire_dict = proxy::expire
quota = dict:User quota::proxy::quota
quota_rule = *:storage=1G
quota_rule2 = Trash:storage=+200M
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
recipient_delimiter =
sieve = ~/.dovecot.sieve
sieve_before = /usr/local/dovecot/etc/dovecot/sieve/move-spam.sieve
sieve_dir = ~/sieve
sieve_global_dir =
Re: [Dovecot] RFE: IMAP LIST Extension for Special-Use Mailboxes
On 26.6.2012, at 18.54, Charles Marcus wrote:
My question (I guess for Timo) is, would it be crazy/possible to implement
some kind of 'alias' conversion in dovecot that would work regardless of
client cooperation?
Ie, in a config file, add a list of 'aliases' for these special use folders
(similar to how it is done now), but where dovecot would then silently
translate/map a request for any of the defined aliases to the defined special
use folder? so, if Outlook wants to save a sent message to 'Sent Items', it
would simply and silently be saved to 'Sent' (or whatever the admin had
defined as the 'real' sent folder). This wouldn't then require anything to be
implemented in a client, it would only require the Admin to know what clients
they want to support and what folders those clients look for by default.
There would be two possibilities:
1) Have aliases where the alias is visible with LIST and all other commands.
Most clients will then show that mailbox duplicated with two names, probably
causing user confusion.
2) Have aliases where the alias isn't visible with LIST, but it would be
possible to APPEND/COPY messages there, or CREATE, SELECT, etc. I have no idea
how different clients would behave with this behavior. Might work with some, or
might not..
You can kind of emulate 2) behavior and see what happens by setting up
namespaces like:
namespace {
prefix =
separator = /
inbox = yes
list = no
hidden = no
}
namespace {
prefix = RealMails/
separator = /
list = no
hidden = yes
}
# I think there needs to be one list=yes namespace:
namespace {
prefix = something/
separator = /
list = yes
hidden = yes
location = mbox:/var/lib/dovecot/empty
}
Anyway you could see if clients show the Drafts/Sent etc. mailboxes that they
create and allows actually accessing them.
Re: [Dovecot] Setting up mixed mbox and maildir
On 27.6.2012, at 0.19, Jonathan Ryshpan wrote:
If you are working with 2.0 or later dovecot, you should be at
http://wiki2.dovecot.org/Namespaces
I am using 2.1.7 . I surmise from this Namespace page that the form:
namespace type {
where type is one of public, private, or shared creates an
unnamed namespace of type type while the form:
namespace name {
where name is none of public, private, or shared, creates a
namespace with the name name and the default type (unspecified on this
page, but probably private).
I don't see any of that in the wiki2 page. Maybe you were looking at wiki1 page.
The namespace can be given the type
desired by an (undocumented) namespace setting:
namespace inbox (
type = type
Is this correct?
It's mentioned in examples :) Yeah, could be more clearly mentioned in the wiki
page too. Of course it's already in the example-config/conf.d/10-mail.conf
file. The name part in namespace name { } should also be in the wiki page,
although that's not namespace-specific thing at all, but works everywhere in
dovecot.conf. It simply gives a (human-readable) name for the namespace within
the configuration, it doesn't actually do anything.
[Dovecot] The deleted_to_trash Plugin (workaround Outlook 2007 behaviour)
Hi, I see this plugin exists for v1 v2, all very interesting... Surprised no one seems to have created an RPM and it looks like deleted_to_trash is one of the very few plugins to not be shipped as part of the default install with CentOS 5.5 or CentOS 6 (i.e. Dovecot v1 v2 respectively.) Am I missing something, or does everyone really build from source? Thanks, James.
Re: [Dovecot] Removing specific entry in user/auth cache
I dont known about Angel, but for me is useful because sometimes i need to deactivate smtp/imap/pop access from accounts, or change their home after storage migration, and removing a specific record i can use a long time cache. On Wed, Jun 27, 2012 at 9:24 AM, Timo Sirainen t...@iki.fi wrote: On 27.6.2012, at 14.10, Angel L. Mateo wrote: We have dovecot configured with auth cache. Is there any way to remove a specific entry (not all) from this cache? Nope. What do you need it for?
Re: [Dovecot] The deleted_to_trash Plugin (workaround Outlook 2007 behaviour)
On Jun 27, 2012, at 9:10 AM, J E Lyon wrote: Hi, I see this plugin exists for v1 v2, all very interesting... Surprised no one seems to have created an RPM and it looks like deleted_to_trash is one of the very few plugins to not be shipped as part of the default install with CentOS 5.5 or CentOS 6 (i.e. Dovecot v1 v2 respectively.) Am I missing something, or does everyone really build from source? I was not aware of this plugin. Looking at the plugin configuration options how would one handle all the various folder names that users use for Trash? http://wiki2.dovecot.org/Plugins/deleted-to-trash Regards, Brad smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] The deleted_to_trash Plugin (workaround Outlook 2007 behaviour)
On 27 Jun 2012, at 19:27, Bradley Giesbrecht wrote: On Jun 27, 2012, at 9:10 AM, J E Lyon wrote: Hi, I see this plugin exists for v1 v2, all very interesting... Surprised no one seems to have created an RPM and it looks like deleted_to_trash is one of the very few plugins to not be shipped as part of the default install with CentOS 5.5 or CentOS 6 (i.e. Dovecot v1 v2 respectively.) Am I missing something, or does everyone really build from source? I was not aware of this plugin. Looking at the plugin configuration options how would one handle all the various folder names that users use for Trash? http://wiki2.dovecot.org/Plugins/deleted-to-trash Hi Brad, Well, it could be a configurable folder name, or not, but it doesn't matter _too_ much . . Looking at various IMAP clients, they already use a variety of folder names, so if I access my IMAP account using my MacBook and my Android and an installation of MS-Outlook, then I might end up with a Deleted folder *and* a Trash folder. It doesn't much matter, I can undelete within an application where I've accidentally hit delete and if I'm looking further back for something deleted last week, I can search both folders if I can't remember where it was deleted. It all works out adequately in the end -- from an end user's point of view -- even if it's not very pretty from a software design point of view. J.
Re: [Dovecot] started with dovecot sieve
Rolf wrote: LMTP would be new to me and I fear just other hard-to-understand configuration topics. LMTP (Lightweight Message Transfer Protocol) is really simple, similar to SMTP, but immediately returns a status code which tells whether the delivery has been successful or not. I encourage you to read this HOWTO: http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP Dovecot listens and accepts mails on the LMTP service port, postfix delivers mails directly into this LMTP service port. Since it is an additional service, you should be able to try it first, without interfering with your deliver functionality. Here you can read, how the LMTP communication looks like: http://de.wikipedia.org/wiki/LMTP Regards Daniel -- https://plus.google.com/103021802792276734820
Re: [Dovecot] Setting up mixed mbox and maildir
On Wed, 2012-06-27 at 17:30 +0300, Timo Sirainen wrote:
On 27.6.2012, at 0.19, Jonathan Ryshpan wrote:
If you are working with 2.0 or later dovecot, you should be at
http://wiki2.dovecot.org/Namespaces
I am using 2.1.7 . I surmise from this Namespace page that the form:
namespace type {
where type is one of public, private, or shared creates an
unnamed namespace of type type while the form:
namespace name {
where name is none of public, private, or shared, creates a
namespace with the name name and the default type (unspecified on this
page, but probably private).
I don't see any of that in the wiki2 page. Maybe you were looking at wiki1
page.
Quite right; this comes from a reading of pages in both wiki1 and wiki2.
I now surmise that this isn't a good idea since wiki1 describes v1.x
and wiki2 describes v2.x, which have different syntaxes (syntaces?). Is
all this correct?
The namespace can be given the type
desired by an (undocumented) namespace setting:
namespace inbox (
type = type
Is this correct?
It's mentioned in examples :) Yeah, could be more clearly mentioned in
the wiki page too. Of course it's already in the
example-config/conf.d/10-mail.conf file. The name part in namespace
name { } should also be in the wiki page, although that's not
namespace-specific thing at all, but works everywhere in dovecot.conf.
It simply gives a (human-readable) name for the namespace within the
configuration, it doesn't actually do anything.
It looks like it does *something*, since 15-mailboxes.conf contains the lines:
# NOTE: Assumes namespace inbox has been defined in 10-mail.conf.
namespace inbox {
I am continuing to attempt to set up dovecot to keep its mail store in maildir
form while receiving it from an mbox, but without success. Dovecot reports the
error that it can't create the file ~/mail/.imap/INBOX (and also that it can't
chown it to user mail, not surprising since it doesn't exist). This seems
reasonable, since jonrysh (that is me) is not a member of the group mail. What
should be done next? Should I join the group mail? It seems that this should
not be necessary in general. The mail store is in ~/maildir, so what is the
function of the mbox ~/mail?
Dovecot must be misconfigured, but it's not clear to a newbie like myself
what's wrong. Any advice would be appreciated. I have attached an extract
from maillog showing the errors (dovecot.log) dovecot reports (dovecot.log),
and the output of dovecot -n (dovecot-n).
Thanks for your help - jon
Jun 27 16:05:26 amito dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled)
Jun 27 16:05:50 amito dovecot: imap-login: Login: user=jonrysh, method=PLAIN, rip=::1, lip=::1, mpid=14464, TLS, session=jF+WQXzDNgAB
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Debug: Effective uid=1000, gid=1000, home=/home/jonrysh
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Debug: Namespace data: type=private, prefix=, sep=., inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Dovecot
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Debug: maildir++: root=/home/jonrysh/Dovecot, index=, control=, inbox=, alt=
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Debug: Namespace inbox: type=private, prefix=#mbox., sep=., inbox=yes, hidden=yes, list=no, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/jonrysh
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Debug: fs: root=/home/jonrysh/mail, index=, control=, inbox=/var/spool/mail/jonrysh, alt=
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Error: chown(/home/jonrysh/mail/.imap/INBOX, group=12(mail)) failed: Operation not permitted (egid=1000(jonrysh), group based on /var/spool/mail/jonrysh - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm)
Jun 27 16:05:50 amito dovecot: imap(jonrysh): Error: mkdir(/home/jonrysh/mail/.imap/INBOX) failed: Operation not permitted
Jun 27 16:05:57 amito dovecot: imap-login: Login: user=jonrysh, method=PLAIN, rip=::1, lip=::1, mpid=14477, TLS, session=wb4GQnzDPwAB
Jun 27 16:05:57 amito dovecot: imap(jonrysh): Debug: Effective uid=1000, gid=1000, home=/home/jonrysh
Jun 27 16:05:57 amito dovecot: imap(jonrysh): Debug: Namespace data: type=private, prefix=, sep=., inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Dovecot
Jun 27 16:05:57 amito dovecot: imap(jonrysh): Debug: maildir++: root=/home/jonrysh/Dovecot, index=, control=, inbox=, alt=
Jun 27 16:05:57 amito dovecot: imap(jonrysh): Debug: Namespace inbox: type=private, prefix=#mbox., sep=., inbox=yes, hidden=yes, list=no, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/jonrysh
Jun 27 16:05:57 amito dovecot: imap(jonrysh): Debug: fs: root=/home/jonrysh/mail, index=, control=, inbox=/var/spool/mail/jonrysh, alt=
Jun 27 16:06:07 amito dovecot: imap(jonrysh): Error: chown(/home/jonrysh/mail/.imap/INBOX, group=12(mail)) failed: Operation not permitted
Re: [Dovecot] Removing specific entry in user/auth cache
Francisco Wagner C. Freire wgrcu...@gmail.com writes: On Wed, Jun 27, 2012 at 9:24 AM, Timo Sirainen t...@iki.fi wrote: On 27.6.2012, at 14.10, Angel L. Mateo wrote: We have dovecot configured with auth cache. Is there any way to remove a specific entry (not all) from this cache? Nope. What do you need it for? I dont known about Angel, but for me is useful because sometimes i need to deactivate smtp/imap/pop access from accounts, or change their home after storage migration, and removing a specific record i can use a long time cache. I'm not sure that the auth cache holds that information, but I think you can at least invalidate a particular auth cache entry by 1) Changing the user password (and save the previous hash) 2) Authenticate using the new credentials (and invalidate the auth cache entry). For example, you can just do a manual connection on your dovecot server x login someuser newpassword This will replace the cache entry with a new one. 3) When you are ready to put the account back online, change the password back to the original. A password mismatch forces a resync to your authentication system which will restore the auth cache. Joseph Tam jtam.h...@gmail.com
[Dovecot] indexer-worker
why this process (which most probably do squat index/update) runs as root, not - like imap process - as user? 29413 root 1 760 22820K 9204K kqread 1 0:17 5.86% indexer-worker
