similar to: dsync initial replication failing

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

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):

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

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):

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

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

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

Any plans on having custom Quota Exceeded messages in the future (or now)? I'd love to be able to put the exceeding username in the message to help with some issues. Thanks, Cassidy

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,

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:

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

I've had reports of a number of clients running Outlook 2011 on Mac where they have quite a few folders with the same name appended by multiple "1"s. So far I've only narrowed it down to Outlook 2011 on Mac. We've been in the process of migrating to sdbox on a new server from maildir using dsync backup. Example folder structure: INBOX INBOX 1 INBOX 1 1 INBOX 1 1 1 INBOX 1

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

We're using FreeBSD 10.1 Thanks On Thu, May 21, 2015 at 4:56 PM, Xin Li <delphij at delphij.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 05/21/15 15:47, Cassidy Larson wrote: > > I've been seeing this same error as well now: > > > > Fatal: master: service(indexer-worker): child 20979 killed with > > signal 6 (core not

I've just discovered the recent addition of the comment.char arg to scan, a useful feature no doubt but the default value of # rather than "" breaks my code which looks for # as a delimeter in a file and provides a messy incompatability with earlier versions of R and with Splus. Is there any chance that this default could be changed to ""? -- Steve

Hi, I am trying to SSH to a remote server through R script. In other words, I would like to know how I can get a SSH connection to the remote server and then execute commands on that server with the R script. So in bash, I would normally type ssh -lusername remoteserver.com; press enter and then wait for the password prompt to key in my password. I have tried system("ssh