search for: alandaluz

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

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

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.

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

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

I've been seeing this same error as well now: Fatal: master: service(indexer-worker): child 20979 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) It's only shown up on one particular user, and after tracking down

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

Finally getting around to upgrading my setup to 2.3.x. All of our front end proxies are fine on 2.3 connecting to a 2.2 backend storage pair. So the question is, if I stage the upgrade, will it break replication between the two backend storage servers? My thought was to upgrade one to 2.3, and keep the other on 2.2 for a couple of days? If so, can 2.2 replicate to 2.3, and 2.3 replicate to 2.2

Just upgraded to Dovecot 1.1 and thought I'd try out managesieve plugin. My situation is I have two front end proxy boxes and four storage nodes in the back. I have been able to load the managesieve plugin just like I should on the storage nodes, but not on the proxy boxes. My proxy boxes have multiple server sections to deal with unique configurations for 5-7 different mail domains:

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

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

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

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

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

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

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)

Trying to get my new storage server synced up using dsync replication with SSH. Followed the wiki and everything works great for the initial sync, for about 4 hours, then I get some errors and it stops replicating: dsync-local(user at host.com): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync dsync-local(user at host.com): Error: Remote command returned error 75: