[imapproxy] imapproxy Digest, Vol 48, Issue 1

[Ryan Novosielski]

Doh -- I was not aware that this list was not for up-imapproxy. I've 
been somewhat mixed up on this one, and since I saw no place that Horde 
imapproxy was even available anymore, I figured that this one must be 
for helping horde users use up-imapproxy.

As for the CA issue -- I actually did make a typo there... all three 
lines should read the same thing. Thanks, though, I'll go looking for 
the right list.

---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | | Ryan Novosielski - User Support Spec. III
|$&| |__| |  | |__/ | \| _| | novosirj at umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630 



imapproxy-request at lists.horde.org wrote:
> Send imapproxy mailing list submissions to
> 	imapproxy at lists.horde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.horde.org/mailman/listinfo/imapproxy
> or, via email, send a message with subject or body 'help' to
> 	imapproxy-request at lists.horde.org
>
> You can reach the person managing the list at
> 	imapproxy-owner at lists.horde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of imapproxy digest..."
>
>
> Today's Topics:
>
>    1. Problems with CA and force_tls (Ryan Novosielski)
>    2. Re: Problems with CA and force_tls (Chuck Hagenbuch)
>    3. Re: Problems with CA and force_tls (Jan Schneider)
>    4. Re: Problems with CA and force_tls (Eric Jon Rostetter)
>    5. Re: Problems with CA and force_tls (Chuck Hagenbuch)
>    6. Re: Problems with CA and force_tls (Eric Jon Rostetter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 06 Mar 2006 10:48:55 -0500
> From: Ryan Novosielski <novosirj+imapproxy at umdnj.edu>
> Subject: [imapproxy] Problems with CA and force_tls
> To: imapproxy at lists.horde.org
> Message-ID: <440C59E7.4040303 at umdnj.edu>
> Content-Type: text/plain; format=flowed; charset=ISO-8859-1
>
> I have installed imapproxy v1.2.4 with the following config-file:
>
> server_hostname <my.server.name>
> cache_size 3072
> listen_port 143
> server_port 143
> cache_expiration_time 300
> proc_username nobody
> proc_groupname nobody
> stat_filename /var/run/pimpstats
> protocol_log_filename /var/log/imapproxy_protocol.log
> syslog_facility LOG_MAIL
> send_tcp_keepalives no
> enable_select_cache no
> foreground_mode no
> force_tls yes
> enable_admin_commands no
> tls_ca_file /usr/share/ssl/certs/server-imapd.pem
> tls_ca_path /usr/share/ssl/certs/
> tls_cert_file /usr/share/ssl/certs/server_imapd.pem
> tls_key_file /usr/share/ssl/certs/server_imapd.pem
>
> And when starting the server, I get:
>
> Mar  3 14:47:22 sopris in.imapproxyd[13378]: main(): Configured to run 
> in background mode.
> Mar  3 14:47:22 sopris in.imapproxyd[13380]: main(): Enabling STARTTLS.
> Mar  3 14:47:22 sopris in.imapproxyd[13380]: main(): Failed to load CA 
> data.  Exiting.
>
> I have tried splitting the PEM file out into different files to see if 
> that helps (note, this is a self-signed cert) and this didn't help at 
> all. Is there any way to get more information out of the thing?
>
> Appreciate any responses.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 06 Mar 2006 12:45:15 -0500
> From: Chuck Hagenbuch <chuck at horde.org>
> Subject: Re: [imapproxy] Problems with CA and force_tls
> To: imapproxy at lists.horde.org
> Message-ID: <20060306124515.2ghdqgd4bo0scokk at marina.horde.org>
> Content-Type: text/plain;	charset=ISO-8859-1;	DelSp="Yes";
> 	format="flowed"
>
> Quoting Ryan Novosielski <novosirj+imapproxy at umdnj.edu>:
>
>   
>> I have installed imapproxy v1.2.4 with the following config-file:
>>     
>
> I don't know the answer, and I feel like I should warn you that this  
> list has seen extremely little traffic recently.
>
> Assuming anyone else is here, does anyone feel that this particular  
> imapproxy implementation adds anything special? Or would people be  
> okay with deprecating this codebase and pointing people towards, say,  
> up-imapproxy?
>
> -chuck
>
>