Steven Hildreth wrote:
> The port for the SSL (465 and 993) seem to be a little off standard.
> Netscape (as far as I have found) does not allow this, it wants the SSL
> tunnel on the same (25 and 143) ports,
What version of Netscape did you test that with? 993 is the correct
port for IMAP over SSL (simap). If you tell netscape to use SSL, it
will not use 25 and 143, it will use 465 and 993. As long as you're
using UW-IMAP, imap access is fine (Netscape has some IMAP bugs that
don't get along with courier-imap).
Encrypting SMTP is probably a waste of cpu cycles, since it's terribly
unlikely that the message will be passed from your mail server to the
next in anything but plain text.
Netscape should work just fine with this setup.
> In all honesty I have to say I fought moving from Netscape Messanger to
> Outlook Express,
> big bad Microsoft Train, but it actually works really well with a IMAP
> client
No it doesn't, but neither does Netscape. Outlook express has a fair
IMAP driver, but when I used it last, every time I added a mail folder,
I had to refresh the list of folders, and resubscribe to every one. It
was quite irritating, especially with many folders. Has this changed?
Netscape has its own problems, mostly in it's IMAP driver, that mostly
affect non-UW-IMAP servers. I never had a problem using UW-IMAP, but
switched to courier for better Maildir support, and faster access.
> and even supports
> custom (non-CA signed) certs for email encryption, something that Netscape
> hated.
My certs are self signed, and netscape hasn't complained. It warned me
that the signature was not recognised the first time that I used it, but
that's the intended behavior. Outlook does the same.
I've been using an SSL tunnel and netscape for some time now, with
Netscape verisons 4.5 -> current. If you've seen specific versions have
trouble, let me know.
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
