similar to: login_trusted_networks (v2.0.8)

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:

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,

http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz.sig There are many small fixes all around, plus some more noticeable changes: * Services' default vsz_limits weren't being enforced correctly in earlier v2.0 releases. Now that they are enforced, you might notice that the default limits are too low and you need to increase

http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz.sig There are many small fixes all around, plus some more noticeable changes: * Services' default vsz_limits weren't being enforced correctly in earlier v2.0 releases. Now that they are enforced, you might notice that the default limits are too low and you need to increase

Hi all, Ok, been wanting to do this for a while, and I after the Heartbleed fiasco, the boss finally agreed to let me buy some real certs... Until now, we've been using self-signed certs with the following dovecot config: ssl = required ssl_cert = </etc/ssl/ourCerts/imap.pem ssl_key = </etc/ssl/ourCerts/imap_key.pem Now, I've created new keys/certs and the CSR, got the new

Starting a new thread, as I've got a lot more details now... First, I know this may be (or is even likely) something weird happening with Thunderbird, but the bottom line is, I have to find a resolution or a workaround or something, or I will be unable to pull the trigger on the server migration. It is simply unacceptable to lose ANY mails doing this. Goal: migrate mailstore from old

Today I've been trying to get dovecot (1.0 rc2) to use certificates for client side authentication. If my memory serves right, beta8 had no problems with it (although it was some time ago and on different machine). Similar setup works perfectly well for postfix (for authentication that is, on the same machine). Originally I thought I overdid some certificate settings (keyUsage, nsCertType,

I'd like to get the IP-address of the webmail-klient logged in my maillog (for being compliant with coming data retention policies). I've noticed that with login_trusted_networks pointing at my dovecot directors, we get rip=client-ip logged on the backends. How is the proxy providing this to the dovecot backends? Anybody know what magic we need to implement in our webmail-solution to be

Hi, It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) However... trustwise, this is trusting two different entities. The first case you put trust in the host. In the second

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot v2.2 with unix_listener auth-client { } to verify passwords for a different service. However, it looks like that auth_failure_delay effects all connects going through that socket. I mean: connect /var/run/dovecot2.2/auth-client attempt bad auth 2s penalty NO disconnect ==> Note, it's another connection almost

Hi, For the upcoming 2.3 development, I'd like to re-suggest this: It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. (like a proxy) * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) Often these two uses cases have a

I've been having some problems with IMAP user connections to the Dovecot (v2.0.8) server. The following message is being logged. Jan 16 10:51:36 postal dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped The server is running Red Hat Enterprise Linux release 4 (update 6). Dovecot is v2.0.8. We have only 29 user accounts in

My dovecot directors (v2.0.8) had 3 instances of these yesterday: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 17374 killed with signal 6 (core dumps disabled) imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 1780 killed with signal 6

Well, my Dovecot server (v2.0.8) is up and running, and now it's time to migrate mailboxes from the old mail server [Lotus Domino Release 5.0.8] running on Windows NT 4.0 [ancient -- been the mail server since Aug-2000]. I saw "dsync(1)" and thought my troubles were over. Only I can't figure out how to make it work with the NT/Domino server as a source for mailboxes. I guess

Greetings- As most of you who monitor this list know, I've been messing about with Asterisk -HEAD, Cisco Callmanager, and the nufone H323 channel driver here for some time- with pretty decent success. I'm hoping to cash in a chip here- I've run into something that is probably a very simple answer, yet not found a decent reference to resolve it. Scenario- -HEAD as of last week

Hi, We are planning to use Dovecot-2.0.5 (Maildir format) as IMAP server. Currently, we are using Postfix+UW-Imap (mbox format) with the following configuration: - Postfix: Sends new messages to /var/mail/user - UW-IMAP: Reads mails from /var/mail/user and moves them to ~/nsmail/mbox Using that configuration, when a user overtakes his HOME?s quota, the MTA is still able to send new messages

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 finally upgraded to v1.2.16 on my backend servers, with ldap instead of previously mysql, and put a couple of dovecot v2.0.8 directors in front of them (used haproxy previously). It seemed to work OK initially, but after a few hours we got bit by "Connection queue full" problems on the directors. So I now set default_process_limit=512 and also: service anvil {

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