Are there any plans to add RFC 3348 support to imapd? I'm currently
trying to improve performance in Horde IMP 4.x when accessing a
UW-IMAP server. IMP does 'LIST #shared/*' and then imapd returns a
huge list of shared folders, even though the user doesn't have access to
most of those
Mark,
Thanks for the quick response and the clarification. The way we
organized our shared folders a user will never have access to a
child mailbox is they don't have access to the parent and they would
never create folders in #shared.
Am I correct in that we'd want to modify
I built imap-2004a on Solaris 9 (OpenSSL 0.9.7d) like so:
$ make gso PASSWDTYPE=pmb SSLTYPE=nopwd SSLDIR=/opt/local \
SSLCERTS=/var/ssl EXTRALDFLAGS='-R/opt/local/lib'
I'm able to connect securely via port 995 (pop3s), but I can't connect
via 110 using starttls.
$ openssl s_client -connect
pop with starttls works when I force the use of TLSv1.
$ openssl s_client -connect mailtest:110 -starttls pop3 -tls1
I guess the client I was testing is broken. But my original openssl
command worked for starttls against a non-UWash pop3 server.
On Mon, Jul 26, 2004 at 03:27:44AM -0400, Matt
My feeling about hashed spool directories is that this functionality is
site-specific, with no obvious single definition of how it is to be
implemented that applies in all instances. Consequently, I consider it to
be something that should always be of the form of a third-party patch
rather
Sorry, I forgot to include the attachment.
Cheers.
On Sun, Feb 01, 2004 at 05:59:13PM -0500, Matt Selsky wrote:
My feeling about hashed spool directories is that this functionality is
site-specific, with no obvious single definition of how it is to be
implemented that applies in all
I noticed that some people have asked about hashed spool directories in
the past. This means the spool is /var/mail/s/e/selsky instead of
/var/mail/selsky
The attached patch against imap-2002e implements hashed spool
directories (which are disabled by default). If there are any changes
which
