similar to: v2.0.8 released

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, since some time I'm plagued by internal login failures. With v2.2.10 I got the some additional error, that I should raise the process_limit for the imap service, then I got the hint to raise vsz_limit for the lmtp and imap serverices. These hints are very helpful and are some sort of unique feature of Dovecot - descriptive error

I just spent a bit puzzling over "login_trusted_networks". My problem was using "10.1.2/24" instead of "10.1.2.0/24". Here are some things I looked for during troubleshooting that didn't pan out: (1) No messages printed to syslog. (2) Search for "login_trusted_networks" on the Wiki (wiki2) failed. (3) Comments in example config file

Hello, upgrade Dovecot from v1.2.10 to v2.0.8, after build a new configuration file following instructions of http://wiki2.dovecot.org/Upgrading/2.0 run dovecot I get this: auth: Error: Fatal: Dovecot version mismatch: Master is v2.0.8, dovecot-auth is v1.2.10 (if you don't care, set version_ignore=yes) log: Error: service(auth): child 3389 returned error 89 (Fatal failure) master: Error:

What are the major differences between Versions 1.x and 2.0? I am beginning to set up a new mail server for a small group of users (~20 accounts). Options are the "0.99" version pre- packaged with RHEL-4, or building v1.2.16 or v2.0.7. Just wondering what the list recommends for a new installation. Thanks, - Don

I've been using uw-imap for some time on my linux system and have been running into issues with it so I've decided to move to Dovecote, so far it seems to have solved the issues I've been having however I need/want to move the incoming emails out of /var/spool/mail/{user} in the same (or similar fashion) that uw-imap did, and I found the snarf plugin. However whenever I enable the

I've now upgraded dovecot from 2.0.21 to 2.1.10 and the good news is I no longer see dovecot crashing when loading the snarf plugin however snarf still does not do anything except make the inbox disappear. I've come to the conclusion that either snarf does not actually work, possible, but I doubt it, or more likely I have a configuration issue preventing it from working. The system is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have setup a shared namespace to expose user's mailboxes to other users. That works well. Via ACLs users can access other users mailboxes. I have setup a quota for each user, that works well, too. The quota is tracked and new messages are denied, if the quota is exceeded. I do not find hints, if you need to setup something special for

Hi all, I'm using dovecot v2.0.11 on fedora14 with postfix. This system was migrated from an old UW mbox system, so users already have ~/mail/INBOX.* files. Now for some reason, dovecot is creating ~/mail/mail/INBOX.* files and somehow not seeing the mail_location properly. I've set mail_location to "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u", which has worked on a

nut hardcodes systemdsystemshutdowndir to ${libdir}/systemd/system-shutdown. This is not valid: - Executable helpers are installed to ${libexecdir}, which is different from ${libdir} on bi-arch systems. - Even if nut will use ${libexecdir}, it could be different from systemd libexecdir. That is why it is better to check systemd.pc for the correct path. That path is stored as systemdutildir.

Hello! This is my first dovecot install, which I put together by mixing and matching pieces of various online howtos (fortunately, Dovecot doesn't seem to be overly complex - a big plus). I've got it mostly working, but the trash plugin doesn't seem to be working right. Below are configs and some logs. Any thoughts? Also, any suggestions regarding my configuration? I can post

Hi list, I get these warnings quite frequently. Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync Is this something to worry about? Otherwise the replication works perfectly. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum ---------------------------------------- Auf dem Huegel 69, D-53121 Bonn

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

Hi, I switched from dovecot 1.2.* to 2.0.* for a mail proxy. I try to play with the new cool utility doveadm, but I don't manage to get results from it. # /usr/local/dovecot-2.0.15/bin/doveadm proxy list username proto src ip dest ip port # As 'proxy list'

Dovecot users list, I started having problems with Outlook not syncing with Dovecot a public imap folder upon issuing a send/receive in the client; eventually Outlook timed out, and I received the following error in the Dovecot log. Jan 23 09:20:23 imap(user at mydom.com): Error: FETCH [] for mailbox projects.myfolder UID 120 got too little data: 7744 vs 7759 Jan 23 09:20:23 imap(user at

I have dovecot 2.0.11 installed on a CentOS 5.7 email server. Two of the server email clients, one using Outlook and the other Thunderbird, have had all the contents of their inbox disappear only to reappear at a later time. One client's inbox email reappeared upon receiving a test email (to check if it would show up in the inbox) from another user. Has anyone heard of such a thing?

I'm seeing the following: Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0' Is there something I can get for you to debug? doveconf -n: # 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: FreeBSD 11.1-PRERELEASE amd64 auth_debug_passwords = yes auth_default_realm = lerctr.org auth_mechanisms

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I wanted to enable stats, so I added the settings from http://wiki2.dovecot.org/Statistics into conf.d/99-stats.conf: mail_plugins = $mail_plugins stats protocol imap { mail_plugins = $mail_plugins imap_stats } plugin { # how often to session statistics stats_refresh = 30 secs # track per-IMAP command statistics stats_track_cmds