similar to: imap-login process_limit reached

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

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

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,

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

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

Hi Martin, Thanks for your response! I haven't tested compiling OpenJDK 12-dev with LLVM toolchain, perhaps the issue had been fixed already, because clang treat invalid argument '-std=gnu++98' not allowed with 'C' as error. It is better only apply EXTRA_CFLAGS to C without EXTRA_CXXFLAGS. Furthermore, I just have interest, did you use clang analyzer, sanitizer and

noticed this in the log today, after about 11 warning IMAP appears to have not worked, 'service dovecot reload' got it going again question: what to check/alter ? ---------------- # grep process_limit /var/log/maillog Aug 13 15:31:44 geko dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped ''' Aug 13 20:45:35 geko

it's difficult to use llvm tools like sanitizers on openjdk sources, because of the "cheating" - relying on undefined behavior, and the JIT. On Wed, Sep 5, 2018 at 6:09 PM, Leslie Zhai <zhaixiang at loongson.cn> wrote: > Hi Martin, > > Thanks for your response! > > I haven't tested compiling OpenJDK 12-dev with LLVM toolchain, perhaps the > issue had

Nothing to do with Dovecot, but I figured this is the best place to ask. Do any of the newer versions of Outlook have proper identities support like Thunderbird, mutt, Roundcube, i.e. every other mail client on Earth? We have customers who set up ten different mailboxes for one person because otherwise Outlook won't Do the Right Thing. Is there some way to make it behave like the others? *

On 03/03/2015 11:03 PM, Earl Killian wrote: > On 2015/3/2 10:03, Reindl Harald wrote: >> >> that is all nice >> >> but the main benefit of RBL's is always ignored: >> >> * centralized >> * no log parsing at all >> * honeypot data are "delivered" to any host >> * it's cheap >> * it's easy to maintain >> * it

Hi, next problem with outlook 2003 On the IMAP Server (dovecot.x86_64 1.0.7-7.el5) I created a certificate with "mkcert_dovecot.sh". Some entries as be written to "/etc/pki/dovecot/dovecot-openssl.cnf". plaintext paswords are disables. IMAP Serverport: 993 Server needs SSL Now the outlook 2003 clients meens "the server uses a security certificate, which could not be

On 03/04/2015 09:45 PM, Dave McGuire wrote: > On 03/04/2015 03:37 PM, Oliver Welter wrote: >> Am 04.03.2015 um 21:03 schrieb Dave McGuire: >>> Am 04.03.2015 um 20:12 schrieb Michael Orlitzky: >>>> Please add [DNSBL] support to iptables instead of Dovecot. It's a waste of >>>> effort to code it into every application that listens on the network.

There was some interest in Trojita (an IMAP client) on this list at one point. It looks like it's been seeing steady development again: http://jkt.flaska.net/blog/Trojita_v0_2_9__a_Qt_IMAP_e_mail_client.html

Lutz Schildt posted this to the Gentoo bugzilla recently: http://bugs.gentoo.org/show_bug.cgi?id=415571 There's a backtrace and conf files attached. I was able to find this possibly-related post from a while ago: http://dovecot.org/list/dovecot/2010-September/052963.html

On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote: > `chmod -R 655 /etc/foobar/ssl' drops x attribute from `ssl' itself. > Use `chmod -R 755' or `chmod +x' or similar. > Your private keys should be... private. Use 750 instead.

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

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

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