search for: _simply_

Hi Folks, The spreadsheet-like layout displayed when 'data.entry' is invoked is very useful simply for legible display of data, quite apart from its intended use for the purpose of entering or editing data. If one wants to use it _simply_ as a display device, so that one can look around inside a data-set while working on it, then it is not a good idea to have its _editing_ capabilities active: this is dangerous, since an inadvertent keystroke could change the data. So: is there a way to invoke 'data.entry' in "read-onl...

Hello, I am curious if the below setup makes any sense... If I have two public IP addresses served off of a cable modem, can I send one to a shorewall box in bridge mode, then have the other serve my network? Physically, I would like to run it: Cable Modem -> Shorewall Box -> Router -> Network Possible? I would like to do this using FC 4. thanks

...s to the existing file -- found during review after sending my last post as I run CentOS, not Debian and didn't adjust the path correctly (/etc/ldap vs. /etc/openldap) in dovecot-ldap.conf when setting that up. Anyway, ldapsearch uses the same library as Dovecot so if ldapsearch works, Dovecot _simply_ must work as well ;) As mentioned, I normally run CentOS, where /etc/ssl/certs has SELinux security context; don't you by any chance run something similar which may prevent Dovecot from accessing the file? I tested on Debian 8 with the standard repo software (same versions you reported), even...

I've tested your soulution, but it also says the same error. I've tested all combinations of: - tls_ca_cert_file = <cert> - tls = yes - tls_require_cert = demand Every time it says "Connection error". Only when tls is uncommented it says "TLS required". Additional information from my contact with the openldap-technical mailing list: The