similar to: Multiple Folders Continually Auto-Created

Trying to figure out Proxying with LMTP to a few back end storage servers for quota checking before accepting email delivery on the front end nodes. If I connect to the back end server directly via telnet, everything works great. If I use a front-end server to proxy to the back end server, I don't get the same result. Running 2.2.4 on both front and back end servers. Any help would be

On 16 May 2015, at 09:39, Xin Li <delphij at delphij.net> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > On 5/15/15 10:58, Xin Li wrote: >> Hi, >> >> I have seen the following assertion fails on my own mail server >> (indexer-worker): >> >> Panic: file charset-iconv.c: line 132 (charset_to_utf8):

Running 2.2.15 on FreeBSD 10.0. Forcing replication with: doveadm replicator replicate -f user at host.com on one user that I've seen some syslogs show up to see what's going on. Other users are fine. When I run the above command on the one user it produces a core dump. See below for syslog output and full backtrace: syslog output: Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user

Out of the blue my proxy installations started showing this: dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see src/lib/fdpass.c) Nobody can login. Running 1.0.0 on the proxy and 1.0.2 on my storage boxes. Anybody have any insights? -c

Running 2.2.15 on FreeBSD 10.0 with two back end storage boxes using TCP to sync. Seeing a couple of users that always seem to be throwing these kind of errors in the logs: dovecot: dsync-server(user at host.com): Error: write(/var/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable Just wondering what's the proper course of action to fix it? Thanks.

I start my dovecot with the "-c /path/to/custom/config" option so I can run multiple instances. Been trying out 2.0.1 so I can upgrade my boxes cleanly, but I require managesieve. So after installing the latest sources of the Pigeonhole plugin, I'm getting this when trying to start dovecot: # /usr/local/sbin/dovecot -c /usr/local/etc/dovecot/dovecot_custom.conf managesieve(root):

Started implementing the MasterUser changes to my config files so I can finally offer SPA for pop3/imap. Things are working fine with the MasterUser (horray!), however one of my guys started using SPA with Outlook Express and started getting another users mailbox. Turns out to be related to NTLM. His Outlook express is configured for the username of 'johnsmith'. However, you'll see

On 05/22/15 13:18, Cassidy Larson wrote: > We're using FreeBSD 10.1 I see. Yes that's the same problem I have seen. There is a behavioral difference (I think it's a FreeBSD bug) between FreeBSD's iconv(3) and GNU implementation, and there is arguably a bug with Dovecot that iconv(3) state should be reset for each multipart part. The two together would trigger the problem

Seeing a few core dumps on my two proxy servers with dovecot-auth since upgrading to 1.0.2. Example: Jul 30 13:36:51 alora kernel: pid 20234 (dovecot-auth), uid 0: exited on signal 11 (core dumped) Jul 30 13:36:51 alora dovecot: child 20234 (auth) killed with signal 11 Jul 29 19:17:08 marbella kernel: pid 70627 (dovecot-auth), uid 0: exited on signal 11 (core dumped) Jul 29 19:17:08 marbella

Just switched my storage boxes to 2.0.3 with Pigeonhole. Noticing for those that have quota fulls, my syslog is getting full of errors from sieve: dovecot: lda(user at host.com): Error: sieve: script /data/mail/host.com/user at host.com//.dovecot.sieve failed with unsuccessful implicit keep (user logfile /data/mail/host.com/user at host.com//.dovecot.sieve.log may reveal additional details)

We're in the process of migrating from mbox over to maildir. I'm running into a problem with the proxy and timeouts. Appears the idle timeout is set to 60 seconds. This is a bit too low for some of our large mbox files :( Any plans on adding the: #define CLIENT_LOGIN_IDLE_TIMEOUT 60 #define AUTH_REQUEST_TIMEOUT to the .conf file to be tunable on the fly? I ended up just patching the

Just updated one of my proxy boxes to the latest nightly (20070217), restarted the dovecot process and got a bit of errors showing up for each pop3/imap connection. Feb 19 11:14:00 marbella dovecot: pop3-login: Login: user=<user1 at host.com>, method=PLAIN, rip=209.33.217.218, lip=204.17.177.60 Feb 19 11:14:00 marbella dovecot: POP3(user1 at host.com): Set pop3_uidl_format in config file

I've been in the process of moving my pop3 proxy over to the dovecot proxy. I have a ton of users using pop3 still, and am seeing these errors popup within a minute or so of the connection to the database: Password query failed: Not connected to database Eventually the auth-worker will reconnect to the database and things will go on normal for another minute or two, then the same issue

Per Timo's direction, I decided to give the MasterUser a try in connecting my proxy to my destination server. This might allow for the use of 'secure password' for my clients that like to check that box by default. A couple of problems I'm running into running RC15: #1: My Proxy's SQL password_query line: password_query = SELECT a.clearpasswd AS password, v.storeIP AS host,

Just a quick question, nothing broke. I setup about 5 virtual servers. It's great! I can define which protocols to listen on per server. Just curious why I can specify a unique "login_dir" per server, but not a unqiue login_greeting? Appears dovecot always shows the first login_greeting from the first virtual server. Intended this way? -c -------------- next part --------------

Trying out the post-login scripting Timo added recently. Wanting to run a SQL query, as detailed in the example on the Wiki. However, my "USER" env variable is set to "OK" instead of the username. DOVECOT_VERSION=1.0.rc16 RESTRICT_GID_FIRST=127 USER=OK All the other variables (MAIL, HOME, etc) are fine with the correct username. Am I missing something obvious? Thanks, -c

Still seeing a few core dumps via the deliver process and corrupted transaction log files with RC18: Jan 22 10:46:36 zahara deliver(user at host.com): Corrupted transaction log file /data/mail/host.com/us/user at home.com/dovecot.index.log: start_offset (71680) > file size (71520) Jan 22 10:46:36 zahara deliver(user at host.com): seq = 6, rec->uid = 0, first_new_seq = 6, records = 5 Jan 22

I'm trying to upgrade my proxy front-ends to 2.0.2. I have the latest Pigeonhole release installed, and whenever I connect to the sieve port this gets logged in the syslog: managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=144(<unknown>) egid=144(<unknown>) missing +x perm: /, euid is not dir owner) I dont get any capabilities displayed

Trying to compile 1.1rc8 from scratch on FreeBSD 6.3 as well as from the dovecot-devel port and I get an error when trying to include gssapi. gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\"

Having some problems with setting up a proxy with any authentication mechanisms other than PLAIN. My passwords are stored in my database in plaintext (and MD5), so I figure I could use whatever scheme I want. Using the latest RC15. MySQL for the backend. This first one is CRAM-MD5. It fails (scheme_r != NULL??) then PLAIN tries to take over, but the auth server is restarting: Info: