From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: pop3 via ssl; imap
Date: 03 Apr 1999 03:02:15 +0400 [thread overview]
Message-ID: <m3u2uy8w3s.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Stainless Steel Rat's message of "Fri, 2 Apr 1999 12:51:19 -0500"
"Rat" == Stainless Steel Rat writes:
Rat> Couldn't you just put an "&" at the end of the command?
Rat> I tried that. It did not work.
i've found that it is very easy to use (pop3|imap|anything) via ssl
provided that you have:
* an application which could work with (pop3|imap|anything), but is
not "ssl-aware"
* SSLeay or openssl installed (namely, s_client)
* you are working on a unix box
then, all you need is:
* add a "fake" service name to /etc/services (for some unused port),
* add a record to /etc/inetd.conf for this service, which calls
s_client which connects via ssl to the remote server
* tell your (pop3|imap|anything) non-ssl-aware application to connect
to localhost (without ssl) instead of the remote server! :-)
so, the external channel will be ssl-encrypted, and the application
need not be ssl-aware at all (however, with ssl.el, nnimap works fine;
i did not find (i haven't really investigate this) a standard way to
tell pop3.el to use ssl.el's open-ssl-stream).
Best regards, -- Vladimir.
--
If you live in a country run by committee, be on the committee.
-- Graham Summer
next prev parent reply other threads:[~1999-04-02 23:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-20 8:27 Vladimir Volovich
1999-03-20 22:46 ` Simon Josefsson
1999-03-28 15:32 ` Lars Magne Ingebrigtsen
1999-03-28 18:20 ` Stainless Steel Rat
1999-04-02 13:41 ` Lars Magne Ingebrigtsen
1999-04-02 17:51 ` Stainless Steel Rat
1999-04-02 23:02 ` Vladimir Volovich [this message]
1999-04-03 2:13 ` Stainless Steel Rat
1999-04-04 18:45 ` Michael Welsh Duggan
1999-04-04 19:37 ` Stainless Steel Rat
1999-04-17 5:57 ` Lars Magne Ingebrigtsen
1999-04-18 13:53 ` Stainless Steel Rat
1999-04-18 18:07 ` Lars Magne Ingebrigtsen
1999-03-28 19:44 ` William M. Perry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3u2uy8w3s.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).