Just for closure, I purged the uw-IMAPd server packages, removed the
certificate and installed them again via apt-get. Worked like a charm
with the certificate being regenerated. Thanks.
Luke
CW Harris wrote:
>
>
> Probably, although I think you need to remove/move the cert first.
>
> If not
her have debconf handle it.
> >
> >Luke
> >
> >Roberto Sanchez wrote:
> >
> >>http://tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html
> >>
> >>Create a CA (if you don't already have one) and issue yourself a new
> >>cert.
&g
cates-HOWTO/index.html
Create a CA (if you don't already have one) and issue yourself a new
cert.
-Roberto Sanchez
from /usr/share/doc/uw-imapd-ssl/README.Debian.gz
1. SSL support.
This package has been compiled with SSL support. On installation it will
generate a self-signed certificate
Thanks. I see that as kinda the last resort. I was hoping that there
was a way to do a dpkg-reconfigure to allow the IMAP setup to recreate
the certificate, since I'd rather have debconf handle it.
Luke
Roberto Sanchez wrote:
http://tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html
Create a
Luke Reeves wrote:
When I installed the uw-imapd package on my server, a self signed
certificate was created and is now used for SSL IMAP connections. The
problem is that it's almost a year later, and I have to regenerate the key.
The key is stored in /etc/ssl/certs/imapd.pem, but I'm not sure
When I installed the uw-imapd package on my server, a self signed
certificate was created and is now used for SSL IMAP connections. The
problem is that it's almost a year later, and I have to regenerate the key.
The key is stored in /etc/ssl/certs/imapd.pem, but I'm not sure how to
recreate it
Hi,
i've apt-getted uw-imapd-ssl (woody), and it seemed to run just fine. I
was able to connect from machines in my local network. Then I changed
the hostname of that machine, and i think this was the moment when it
started to refuse connections. However, i thought removing and
regener
On Sun, Jan 13, 2002 at 10:41:22AM -0500, Jaldhar H. Vyas wrote:
> Ok, this is good because it means the basic IMAP connection is working and
> the maildirs are being read correctly.
Indeed they are, albeit incorrectly! See below!
> > However, when I click on a message, I get the error
> > text,
On 13 Jan 2002, Forrest L Norvell wrote:
> The only real problem at this point is getting Evolution and imapd-ssl
> to talk to each other. I have SSL enabled between Evolution and the IMAP
> server. After a lot of head-bonking, I figured out that setting the
> namespace to "Mai
ole lot of time and pain in converting my mail rules
over to procmail. I'm pretty pleased with the way that's all working.
The only real problem at this point is getting Evolution and imapd-ssl
to talk to each other. I have SSL enabled between Evolution and the IMAP
server. After a lot of he
hanasaki <[EMAIL PROTECTED]> writes:
> Am I using the courier package wrong or does it not currently support
> imapd-ssl?
You need the courier-imap-ssl package in the non-US archives for ssl
support.
--
Brian Nelson <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
http://bignachos.com
Am I using the courier package wrong or does it not currently support
imapd-ssl?
Thanks,
--
[EMAIL PROTECTED]
Spam : def: It's not kosher.
12 matches
Mail list logo
