similar to: "ldap_result() failed: Can't contact LDAP server" log messages

Greetings - Work moves onward here at setting up our Dovecot IMAP service and I've got a couple more questions, I'm afraid... :-} ============================================== Q1. The UW IMAP Server supports "pre-authenticated connections" -- does Dovecot? Specifically, it is possible to create a symlink from /etc/rimapd to the UW IMAP server binary and then use rsh

Greetings - I've just built Dovecot 1.0beta8 and find it refuses to start. This under Solaris 10 on an Intel-based Sun system. The error message Dovecot displays (on standard error) in response to /usr/local/sbin/dovecot is Fatal: Protocol imaps given more than once I've checked through my configuration file and the only mention of "imaps" is here: # Protocols

Hi, I'm new to the list; excuse me if this has been asked recently/before. running: # dovecot --version 1.0.8 Output of dovecot -n: base_dir: /var/run/dovecot protocols: none ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args:

Greetings - I've just discovered an oddity I didn't know I had... We have two NetApp filers: one serves people's home directories; the other their message store and control files filestores. At the moment the first of the two filers is not accessible to my Dovecot system and I assumed all would be well because, as far as I knew, I wasn't using it at all. However in

Greetings - I have been looking at Dovecot with a view to migrating us to it from the Washington IMAP server on our Sun systems. To start our testing we first of all installed the pre-built version of Dovecot from the Blastwave (www.blastwave.org) community supported packaged software site. This was Dovecot 0.99.10.4 and we successfully got it working in our test environment: at first just

Greetings - Could someone confirm how to perform various upgrades on a live system running Dovecot please? Scenario 1: Change to dovecot.conf =================================== If I make a change to dovecot.conf am I right in thinking I can simply send a HUP signal to the main dovecot process to get it to re- read the configuration file and act on its revised content? Scenario 2:

Greetings - [SIGH: I hit the "Send" button instead of "Attach". Here's Take 2...] Whilst playing with getting quotas from NFS-mounted filestores I've just discovered a slight problem with src/lib/mountpoint.c I had things working on a Solaris 10 test machine which had the mailstore mounted 'normally' using an entry in /etc/vfstab. However when I changed

Greetings - I'm having a frustrating time with mail clients not picking up Dovecot's QUOTA extension to IMAP. The problem is that the QUOTA keyword isn't advertised in Dovecot's response to a CAPABILITY enquiry until *after* the user has authenticated. Unfortunately I've yet to find a mail client that issues a CAPABILITY request after authenticating. Instead all do so

Greetings - I'm having trouble working out where to alter this behaviour (so please forgive me if it turns out to be an Exim thing rather than Dovecot!)... My test service is using Exim as the MTA and Dovecot's "deliver" for the LDA. We are using Maildir mailboxes with filestore quotas. When I send a large test message to myself that cannot be delivered because I

Greetings - Now that users are beginning to pile up more on our new Dovecot-based IMAP service I'm seeing a small number of entries like this in the logfiles: Corrupted index cache file /mailstore/index/o/ozw100/.INBOX/ dovecot.index.cache : invalid record size We are using Dovecot 1.0.3 with Maildir folders served over NFS from NetApp filers, but the index files are stored on local

Greetings - I'm now in the last couple of weeks before going live with Dovecot (v1.0.3) on our revamped IMAP service. I'd like to double-check about the best mount options to use; could someone advise, please? I have three separate directory trees for the message store, the control files and the index files. These are arranged as follows: Message Store Mounted over NFS from

Greetings - I've now got as far as playing with the imaptest10 test utility to see if I can stress-test our development server. imaptest10 is built against dovecot-1.0rc28 It may just be that I'm excessively heavy handed, but when I let imaptest10 rip with the command... ./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50 mbox=./dovecot.mbox msgs=1000 secs=30

Hi, I have configured dovecot for auth_bind against an LDAP server on the localhost and I'm seeing the following error in my dovecot logs: dovecot: Apr 30 09:03:18 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Apr 30 09:03:27 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server ... and so on ... When I turned on LDAP

Greetings - I think I've just had one of my fears confirmed: not Dovecot-specific exactly, but it affects how we will use of Prayer (Webmail Software) with Dovecot... Currently our production service uses MBX-format mailboxes with the UW IMAP server; we also use the University of Cambridge "Prayer" software for Webmail. By default Prayer saves its preference settings,

Greetings - On one of the mailing lists I'm on there was a recent-ish discussion about webmail clients, and someone mentioned a site selling sets of skins for SquirrelMail... the entire set was about $300. I'm trying to track down the site but seem to have deleted the message I'd carefully been keeping. I recall an off-topic discussion along these lines here recently, but

Hi, I experimented with Dovecot a while back and our site is now taking the plunge to switch to it from the UW IMAP server when we rejig the topology of our mail store and IMAP servers. Currently we have a farm of 5 IMAP servers running the UW server. Each has locally attached disk used to store people's mailboxes. Each user is allocated to one of these five servers and can only

Greetings - I'm finalising the layout of our new mailstore ready for a trial service using Dovecot (switching from the UW IMAP server). This is using Maildir mailboxes, changing from our current mix of MBX and traditional Berkeley. One of the things we are often asked for is how someone can grant another access to their mailbox: eg, a Head of Department wants the Departmental

Greetings - Whilst playing with getting quotas from NFS-mounted filestores I've just discovered a slight problem with src/lib/mountpoint.c I had things working on a Solaris 10 test machine which had the mailstore mounted 'normally' using an entry in /etc/vfstab. However when I changed to use the automounter for the mailstore obtaining the quota broke. The problem lies with

Greetings - We are running Dovecot 1.1.11 on our servers and have been gradually migrating people off our old (UW-based) systems onto the new (Dovecot-based) ones. As a result the new systems are seeing more connections from more people. We have started seeing problems reported by users of our webmail service that they are getting an error indicating the webmail software (Prayer) has failed to

I can't get my domain users presented to my local machine with getent passwd and the wiki https://wiki.samba.org/index.php/Local_user_management_and_authentication/nslcd doesn't give me any steps troubleshoot this issue. My best guess it that I configured the user account incorrectly or I configured nslcd incorrectly. I can't exactly see what is the problem. I get these messages from