similar to: Dovecot Director and MasterUsers

Hi Guys, When I have a username like foo-bar-candy can I get/seperate foo, bar and candy as single variables for my storagepath of the usermail ? Thanks, Matt

TL;DR: Can director_username_hash use %{userdb:...} or %{passdb:...} ? ==================================== This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production, director-ized env, so assume everything is working correctly. Happy to post doveconf if it's relevant but wanted to ask a general question first. I was curious if there's a way to get userdb/passdb

Hi, After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(user at example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(user at example.org):

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

Hi dovecot masters, This is my first post here, since I desperately need some advices from the dovecot community. I've tried to get an answer on the Apple Forums but til now no luck....here we go: I've tried to sync our users emails (Mac OS X Server 10.6.8 Snow Leopard with dovecot 1.1.20-apple0.5) via imapsync to our new server by using the masterusers authentication method on the old

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

I'm in a fairly standard cluster environment: shared storage, bunch of servers each acting as both proxies and backends. We do /bin/checkpassword authentication, allowing a great deal of flexibility...protection against brute force, billing mechanisms, but relevant to this issue, I have it set up to allow users to login with either their username (if they are in one of our default

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

Dovecot version: 2.2.25 (7be1766) I?m looking into an issue we?re having with a new setup. We have one fronted host with two backend hosts, and we?re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts. When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host: frontend-machine $ cat

> On 12 April 2019 21:09 Mark Moseley via dovecot <dovecot at dovecot.org> wrote: > > > TL;DR: > > Can director_username_hash use %{userdb:...} or %{passdb:...} ? > > ==================================== > > This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production, director-ized env, so assume everything is working correctly. Happy to

Our directors hash by domain (director_username_hash = %d), as some of our users share folders with other users of the same domain. We now started using director tags to map domains to their backends. Unfortunately doveadm director map seems no to work with director_username_hash = %d user??? hash??? mail server ip expire time <unknown> 432784257 10.44.88.1?? 2020-11-23 13:10:55

Hi all, when hardening dovecot against the POODLE vulnerability, we followed the advise to disable SSL2 and SSL3 but this is giving problems with some email clients (claws-mail). ssl_protocols = !SSLv2 !SSLv3 results in the following error: dovecot: pop3-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=XXX, lip=XXX, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL

Hi, I've one problem: Mails, which I already read or deleted via my IMAP client (Thunderbird) on the same machine running the server (it runs behind DynDNS on my local machine, thanks to http://mein.homelinux.com/wiki/mailserver/) show up again if I connect via IMAP from other client computers, i.e. my notebook (Thunderbird again). As you can see from the config below I have

Hello, I'm trying to move from procmail to dovecot sieve. I found the translation script at http://www.dovecot.org/tools/procmail2sieve.pl It works well except the following use cases: * ^From:.*myemail at mydomain.com.* | formail -I"X-Priority: 2 (high)" -I"X-mydomain-com-seen: yes" | $SENDMAIL -oi \ myemail at mydomain2.com \ myemail at mydomain3.com :0c *

I need to migrate an old mail server running Dovecot (0.99.14) to a new server running Dovecot (1.0.7; as shipped with CentOS 5.2). My plan was to use the imapsync utility as this will "seamlessly" do the conversion from mbox to maildir between the boxes as well. I've got the MasterUser authentication working fine on the new host and was just about to start getting