Re: Dual port popper

[Robert Brandtjen]

on 6/5/93 4:58 PM, [EMAIL PROTECTED] at
[EMAIL PROTECTED] wrote:

>> GET ME OFF THIS LIST ...
>> 
>> HELP
>> 
>> 
>> HELP.
>> 
>> I WANT OFF THE LIST.
>> 
> 
> I do not see unsubscribe at the boot of each email. I am getting TOO many
> emails and I l solved my OS X  server email issue.
> 
> HELP HELP 
> 
> PLEASE

How sad...
Makes me embarrassed to say I use the same OS.

 Robert Brandtjen
 --
 Web Site Creation and Hosting Services
 [EMAIL PROTECTED]
 www.prometheusmedia.com

Re: Dual port popper

[Randall Gellens]

At 4:45 PM -0600 6/5/01, The Doctor wrote:

>   > The strings you enter will depend on your configuration.  In many cases
>>  command line options alone will suffice.  Try reading the manual, trying
>>  it yourself, and then asking for specific help if you are stuck.
>
>
>  The manual was of no help.
>
>  Again the question is how can you get qpopper to use both ports 
> 110 (unsecure)
>  and port 995 (SSL Secure) on the same deamon?

See page 51 of the Administrator's Guide:

>  If you want to enable both alternate-port and STLS, you can do 
> this with three configura-tion
>  files. One file contains the set tls-support = stls command, and a second
>  file contains the set tls-support = alternate-port command. Both files also
>  contain one other command, which instructs Qpopper to read the 
> third configuration
>  file, for example, set config-file = /etc/mail/pop/qpopper-tls.config.
>  Set all other options in this third file. Then use the -f 
> run-time option to cause Qpopper
>  to read either of the first two files.

Keep in mind that alternate-port TLS means that an SSL/TLS 
negotiation first thing, so it can't be used with anything else.

Re: Dual port popper

[Kenneth Porter]

On Tue, 5 Jun 2001 16:45:54 -0600, The Doctor wrote:

>The manual was of no help.
>
>Again the question is how can you get qpopper to use both ports 110 (unsecure)
>and port 995 (SSL Secure) on the same deamon?
>
>This might become and FAQ question. 

Page 48, "Managing Qpopper", describes how to set up the certs and what
to put in the config files. You then read through the runtime options
under "Installing Qpopper" and add any other options you need.

How are you starting Qpopper? inetd, xinetd, or something else? Read
the documentation for those to see how to start a service. Then create
two entries for Qpopper, one on each port with options appropriate to
that port.

Note that you're not running the "same" Qpopper on both ports. You're
using the same executable, but with different options. And every user
connecting is using a unique process; users don't share one Qpopper
process.

Ken
mailto:[EMAIL PROTECTED]
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my 
answer on the list.]

Re: Dual port popper

[Clifton Royston]

 <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0us
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] 
on Tue, Jun 05, 2001 at 04:45:54PM -0600

On Tue, Jun 05, 2001 at 04:45:54PM -0600, The Doctor wrote:
> The manual was of no help.
> 
> Again the question is how can you get qpopper to use both ports 110 (unsecure)
> and port 995 (SSL Secure) on the same deamon?
> 
> This might become and FAQ question. 

  It gives info on a couple ways to do it on pages 38 and on 51 of the
PDF manual.  Try reading the configuration options settings for
"tls-support" on page 38.  Also try reading the chapter entitled
Security and Authentication, the section which says Setting TLS/SSL
Options.  The paragraph beginning "If you want to enable both
alternate-port and STLS..." explains how to make both unsecure and SSL
connections work on port 110 while supporting SSL-only on port 995.

  I really think you could have found this for yourself.

  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  [EMAIL PROTECTED]
   WWJD?   "JWRTFM!" - Scott Dorsey (kludge)   "JWG" - Eddie Aikau

RE: Dual port popper

[ablack]

if you kept the email that you received when you signed onto this list it
has the commands of how to unsubscribe in it.  If you did not keep that
email the command is as follows:

Should you ever wish to unsubscribe, send the word "unsubscribe"
(without the quotes) to <[EMAIL PROTECTED]>.

AB

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 05, 1993 4:58 PM
To: Joel B. Laing; The Doctor
Cc: Subscribers of Qpopper
Subject: Re: Dual port popper


> GET ME OFF THIS LIST ...
>
> HELP
>
>
> HELP.
>
> I WANT OFF THE LIST.
>

I do not see unsubscribe at the boot of each email. I am getting TOO many
emails and I l solved my OS X  server email issue.

HELP HELP

PLEASE
>

Re: Dual port popper

[The Doctor]

 <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on 
Tue, Jun 05, 2001 at 02:27:36PM -0400


On Tue, Jun 05, 2001 at 02:27:36PM -0400, Scott McDermott wrote:
> 
> 
>  <[EMAIL PROTECTED]>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 1.0.1i
> In-Reply-To: <[EMAIL PROTECTED]>; from 
>[EMAIL PROTECTED] on Tue, Jun 05, 2001 at 11:06:31AM -0600
> 
> The Doctor on Tue  5/06 11:06 -0600:
> > > > Also, How do I setup the configuration files?
> > >
> > > with a text editor ?
> >
> > So with a text editor, what do I enter?
> 
> You enter strings using the keys from your keyboard and then save the
> file.
> 
> The strings you enter will depend on your configuration.  In many cases
> command line options alone will suffice.  Try reading the manual, trying
> it yourself, and then asking for specific help if you are stuck.


The manual was of no help.

Again the question is how can you get qpopper to use both ports 110 (unsecure)
and port 995 (SSL Secure) on the same deamon?

This might become and FAQ question. 

Re: Dual port popper

[Steven Champeon]

on Sat, Jun 05, 1993 at 05:57:26PM -0400, [EMAIL PROTECTED] wrote:
> I do not see unsubscribe at the boot of each email. I am getting TOO many
> eamils and I l solved my OS X  server email issue.

Try viewing headers (included in every message):

 List-Subscribe: 
 List-Unsubscribe: 
 List-Archive: 
 List-Post: 
 List-Owner: Pensive Mailing List Admin <[EMAIL PROTECTED]>
 List-Help: http://www.pensive.org/Mailing_Lists/
 List-Id: 

That's the standard mechanism for announcing list-related meta information,
per RFC 2919 and RFC 2369.

 ftp://ftp.isi.edu/in-notes/rfc2919.txt
 ftp://ftp.isi.edu/in-notes/rfc2369.txt

I couldn't find the RFC where it suggests that acting like an idiot in
public because you scrapped the unsub instructions is now deprecated.

Steve

-- 
hesketh.com/inc. v: (919) 834-2552 f: (919) 834-2554 w: http://hesketh.com

Re: Dual port popper

[[EMAIL PROTECTED]]

> GET ME OFF THIS LIST ...
> 
> HELP
> 
> 
> HELP.
> 
> I WANT OFF THE LIST.
> 

I do not see unsubscribe at the boot of each email. I am getting TOO many
emails and I l solved my OS X  server email issue.

HELP HELP 

PLEASE
> 

Re: Dual port popper

[[EMAIL PROTECTED]]

>> 
> GET ME OFF THIS LIST ...
> 
> HELP
> 
> 
> HELP.
> 
> I WANT OFF THE LIST.
> 

I do not see unsubscribe at the boot of each email. I am getting TOO many
eamils and I l solved my OS X  server email issue.

HELP HELP 

PLEASE
> 

Re: Dual port popper

[[EMAIL PROTECTED]]

on 6/5/01 2:04 PM, Joel B. Laing at [EMAIL PROTECTED] wrote:

> The Doctor wrote:
>> 
>> On Tue, Jun 05, 2001 at 11:20:07AM -0400, Joel B. Laing wrote:
>>> 
>>> The Doctor wrote:
 
 queston:
 
 Using Qpopper 4.0.3 how can one set up qpopper to listen on
 ports 110 (unsecure) and 995 (secure)
 
 I have compiled all the certs and is ready to go, but even all the
 Qualcomm pages cannot seem to answer this.
 
 Does anyone have this set up successfully?
>>> 
>>> Yup, works fine, you just need to modify inetd.conf and services. Have
>>> separate config files in etc (apop.conf and popper.conf) for the
>>> different behaviors. You should also look at your firewall rules if
>>> applicable.
>>> 
>>> For example,
>>> inetd.conf:
>>> 
>>> apopstream  tcp nowait  root/usr/local/etc/apop apop -f
>>> /etc/apop.conf
>>> pop3stream  tcp nowait  root/usr/local/etc/popper
>>> popper -f /etc/popper.conf
>>> 
>>> services:
>>> 
>>> apop995/tcp # Apop
>>> pop3110/tcp # Popper
>>> 
>>> Read the INSTALL file for the config options. Sorta depends on exactly
>>> what you are  trying to accomplish. You probably want the "non secure"
>>> popper to accept both clear text passwords and apop, and the "secure"
>>> one to only authenticate via apop. Also, if you port forward 110 to 995
>>> at the firewall, you can prevent users from having to reconfigure their
>>> clients.
>>> 
>>> Hope this helps,
>>> Joel
>> 
>> Why apop on port 995?
> Actually, I use a different port than 995. 995 is what you used in your
> question. I did not realize that that is used by TLS... The same basic
> setup applies, however, unless there is something about TLS I don't
> understand (which is quite likely). You can call the service anything
> you want, the point is using inetd and services to facilitate different
> instances of popper on separate ports, which is in essence what you are
> trying to do.
> 
> -Joel
> 
GET ME OFF THIS LIST ...

HELP


HELP.

I WANT OFF THE LIST.

Re: Dual port popper

[Joel B. Laing]

The Doctor wrote:
> 
> On Tue, Jun 05, 2001 at 11:20:07AM -0400, Joel B. Laing wrote:
> >
> > The Doctor wrote:
> > >
> > > queston:
> > >
> > > Using Qpopper 4.0.3 how can one set up qpopper to listen on
> > > ports 110 (unsecure) and 995 (secure)
> > >
> > > I have compiled all the certs and is ready to go, but even all the
> > > Qualcomm pages cannot seem to answer this.
> > >
> > > Does anyone have this set up successfully?
> >
> > Yup, works fine, you just need to modify inetd.conf and services. Have
> > separate config files in etc (apop.conf and popper.conf) for the
> > different behaviors. You should also look at your firewall rules if
> > applicable.
> >
> > For example,
> > inetd.conf:
> >
> > apopstream  tcp nowait  root/usr/local/etc/apop apop -f
> > /etc/apop.conf
> > pop3stream  tcp nowait  root/usr/local/etc/popper
> > popper -f /etc/popper.conf
> >
> > services:
> >
> > apop995/tcp # Apop
> > pop3110/tcp # Popper
> >
> > Read the INSTALL file for the config options. Sorta depends on exactly
> > what you are  trying to accomplish. You probably want the "non secure"
> > popper to accept both clear text passwords and apop, and the "secure"
> > one to only authenticate via apop. Also, if you port forward 110 to 995
> > at the firewall, you can prevent users from having to reconfigure their
> > clients.
> >
> > Hope this helps,
> > Joel
> 
> Why apop on port 995?
Actually, I use a different port than 995. 995 is what you used in your
question. I did not realize that that is used by TLS... The same basic
setup applies, however, unless there is something about TLS I don't
understand (which is quite likely). You can call the service anything
you want, the point is using inetd and services to facilitate different
instances of popper on separate ports, which is in essence what you are
trying to do.

-Joel

Re: Dual port popper

[The Doctor]

On Tue, Jun 05, 2001 at 11:20:07AM -0400, Joel B. Laing wrote:
> 
> The Doctor wrote:
> > 
> > queston:
> > 
> > Using Qpopper 4.0.3 how can one set up qpopper to listen on
> > ports 110 (unsecure) and 995 (secure)
> > 
> > I have compiled all the certs and is ready to go, but even all the
> > Qualcomm pages cannot seem to answer this.
> > 
> > Does anyone have this set up successfully?
> 
> Yup, works fine, you just need to modify inetd.conf and services. Have
> separate config files in etc (apop.conf and popper.conf) for the
> different behaviors. You should also look at your firewall rules if
> applicable.
> 
> For example,
> inetd.conf:
> 
> apopstream  tcp nowait  root/usr/local/etc/apop apop -f
> /etc/apop.conf
> pop3stream  tcp nowait  root/usr/local/etc/popper   
> popper -f /etc/popper.conf
> 
> services:
> 
> apop995/tcp # Apop
> pop3110/tcp # Popper
> 
> Read the INSTALL file for the config options. Sorta depends on exactly
> what you are  trying to accomplish. You probably want the "non secure"
> popper to accept both clear text passwords and apop, and the "secure"
> one to only authenticate via apop. Also, if you port forward 110 to 995
> at the firewall, you can prevent users from having to reconfigure their
> clients. 
> 
> Hope this helps,
> Joel

Why apop on port 995?

Re: Dual port popper

[Scott McDermott]

 <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] 
on Tue, Jun 05, 2001 at 11:06:31AM -0600

The Doctor on Tue  5/06 11:06 -0600:
> > > Also, How do I setup the configuration files?
> >
> > with a text editor ?
>
> So with a text editor, what do I enter?

You enter strings using the keys from your keyboard and then save the
file.

The strings you enter will depend on your configuration.  In many cases
command line options alone will suffice.  Try reading the manual, trying
it yourself, and then asking for specific help if you are stuck.

Re: Dual port popper

[Joel B. Laing]

The Doctor wrote:
> 
> queston:
> 
> Using Qpopper 4.0.3 how can one set up qpopper to listen on
> ports 110 (unsecure) and 995 (secure)
> 
> I have compiled all the certs and is ready to go, but even all the
> Qualcomm pages cannot seem to answer this.
> 
> Does anyone have this set up successfully?

Yup, works fine, you just need to modify inetd.conf and services. Have
separate config files in etc (apop.conf and popper.conf) for the
different behaviors. You should also look at your firewall rules if
applicable.

For example,
inetd.conf:

apopstream  tcp nowait  root/usr/local/etc/apop apop -f
/etc/apop.conf
pop3stream  tcp nowait  root/usr/local/etc/popper   
popper -f /etc/popper.conf

services:

apop995/tcp # Apop
pop3110/tcp # Popper

Read the INSTALL file for the config options. Sorta depends on exactly
what you are  trying to accomplish. You probably want the "non secure"
popper to accept both clear text passwords and apop, and the "secure"
one to only authenticate via apop. Also, if you port forward 110 to 995
at the firewall, you can prevent users from having to reconfigure their
clients. 

Hope this helps,
Joel

Re: Dual port popper

[The Doctor]

 <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on 
Tue, Jun 05, 2001 at 12:29:55PM -0400


On Tue, Jun 05, 2001 at 12:29:55PM -0400, Scott McDermott wrote:
> 
> 
> ive.org>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 1.0.1i
> In-Reply-To: <[EMAIL PROTECTED]>; from 
>[EMAIL PROTECTED] on Mon, Jun 04, 2001 at 09:41:42PM -0600
> 
> The Doctor on Mon  4/06 21:41 -0600:
> > > > Just run two servers then...one bound to one port, and another
> > > > bound to the other...am I missing something here?
> > >
> > > So I should run /path/to/popper  and /path/to/popper with options
> > > then?
> 
> Huh? Yes, you invoke two of them...specify different configuration files
> for each if you need to.
> 
> > Also, How do I setup the configuration files?
> 
> with a text editor ?


So with a text editor, what do I enter?

Re: Dual port popper

[Scott McDermott]

ive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] 
on Mon, Jun 04, 2001 at 09:41:42PM -0600

The Doctor on Mon  4/06 21:41 -0600:
> > > Just run two servers then...one bound to one port, and another
> > > bound to the other...am I missing something here?
> >
> > So I should run /path/to/popper  and /path/to/popper with options
> > then?

Huh? Yes, you invoke two of them...specify different configuration files
for each if you need to.

> Also, How do I setup the configuration files?

with a text editor ?

Re: Dual port popper

[The Doctor]

On Mon, Jun 04, 2001 at 06:56:29PM -0600, The Doctor wrote:
> 
> On Mon, Jun 04, 2001 at 05:43:37PM -0400, Scott McDermott wrote:
> > 
> > The Doctor on Mon  4/06 13:36 -0600:
> > > > > Using Qpopper 4.0.3 how can one set up qpopper to listen on ports
> > > > > 110 (unsecure) and 995 (secure)
> > > > 
> > > > That depends...do you want TLS to be available on 110 as well as
> > > > 995, or simple unencrypted POP on 110 and TLS on 995 ?
> > > > 
> > > > In either case though, it's simply a matter of setting up your inetd
> > > 
> > > The latter on a standalone server.
> > 
> > Just run two servers then...one bound to one port, and another bound to
> > the other...am I missing something here?
> 
> 
> So I should run /path/to/popper  and /path/to/popper with options then?

Also, How do I setup the configuration files?

Re: Dual port popper

[The Doctor]

On Mon, Jun 04, 2001 at 05:43:37PM -0400, Scott McDermott wrote:
> 
> The Doctor on Mon  4/06 13:36 -0600:
> > > > Using Qpopper 4.0.3 how can one set up qpopper to listen on ports
> > > > 110 (unsecure) and 995 (secure)
> > > 
> > > That depends...do you want TLS to be available on 110 as well as
> > > 995, or simple unencrypted POP on 110 and TLS on 995 ?
> > > 
> > > In either case though, it's simply a matter of setting up your inetd
> > 
> > The latter on a standalone server.
> 
> Just run two servers then...one bound to one port, and another bound to
> the other...am I missing something here?


So I should run /path/to/popper  and /path/to/popper with options then?

Re: Dual port popper

[Scott McDermott]

The Doctor on Mon  4/06 13:36 -0600:
> > > Using Qpopper 4.0.3 how can one set up qpopper to listen on ports
> > > 110 (unsecure) and 995 (secure)
> > 
> > That depends...do you want TLS to be available on 110 as well as
> > 995, or simple unencrypted POP on 110 and TLS on 995 ?
> > 
> > In either case though, it's simply a matter of setting up your inetd
> 
> The latter on a standalone server.

Just run two servers then...one bound to one port, and another bound to
the other...am I missing something here?

Re: Dual port popper

[Scott McDermott]

Christopher Crowley on Mon  4/06 14:14 -0500:
> "The server you are connected to is using a certificate that does not
> match its internet address.  Do you want to continue?" I have no way
> of  viewing this certificate during the Outlook Express authentication
> process.

This probably means the CN field in the certificate doesn't match the
PTR record of the machine you're connected to (and possibly also the A
record).  Maybe you are using CNAMEs.  You can't do that with X.509 very
well.

Re: Dual port popper

[The Doctor]

On Mon, Jun 04, 2001 at 01:57:30PM -0400, Scott McDermott wrote:
> 
> The Doctor on Sat  2/06 17:27 -0600:
> > Using Qpopper 4.0.3 how can one set up qpopper to listen on ports 110
> > (unsecure) and 995 (secure)
> 
> That depends...do you want TLS to be available on 110 as well as 995, or
> simple unencrypted POP on 110 and TLS on 995 ?
> 
> In either case though, it's simply a matter of setting up your inetd to
> give a different configuration file (if you need to even do that) on the
> command line of the server bound to each port.  IOW you would have two
> qpopper specifications in your inetd configuration file, with the same
> stuff but a different configuration file given and port number to bind
> to.


The latter on a standalone server.

Re: Dual port popper

[Christopher Crowley]

Subject: Dual port popper


> queston:
>
> Using Qpopper 4.0.3 how can one set up qpopper to listen on
> ports 110 (unsecure) and 995 (secure)
>
> I have compiled all the certs and is ready to go, but even all the
> Qualcomm pages cannot seem to answer this.
>
> Does anyone have this set up successfully?
>
>

I am trying to setup this configuration as well. The Openssl client can
connect, but I  run into this error from the Pop logs when I try to connect
via Outlook Express on Windows 2000 I fail. However, using OE on Win NT 4.0
I receive a message that says:

"The server you are connected to is using a certificate that does not match
its internet address.  Do you want to continue?" I have no way of  viewing
this certificate during the Outlook Express authentication process.

The openssl client authenticates just fine.

I will include some log info, hoping that it is useful and not overly
confusing.


POPlog
---
Windows 2000 failure:
- - - - - - - - - -- - -- -
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: (v4.0.3) TLSv1/SSLv3
handshake with client at dhcp-119-238.tulane.edu (129.81.119.238); new
session-id; cipher: EXP1024-RC4-SHA (EXP1024-RC4-SHA SSLv3 Kx=RSA(1024)
Au=RSA Enc=RC4(56) Mac=SHA1 export), 56 bits
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: OpenSSL Error during
read
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: ...SSL error:
error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: (null) at
dhcp-119-238.tulane.edu (129.81.119.238): -ERR POP EOF or I/O Error
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: OpenSSL Error during
write
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: ...SSL error:
error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: Error writing to
client
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: I/O Error
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6335]: Error writing to
client
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6340]: TLS handshake Error
Jun  4 14:03:01 majestic
/export/home/root/src/qpopper4.0.3/popper/popper[6340]: TLS/SSL Handshake
failed: -1

-   ---   -   -
End POPlog
---
---



OpenSSL s_client transcript

CONNECTED(0003)
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
depth=0 /C=US/ST=Louisiana/L=New Orleans/O=Tulane
University/OU=TIS/CN=majestic.tcs.tulane.edu
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 /C=US/ST=Louisiana/L=New Orleans/O=Tulane
University/OU=TIS/CN=majestic.tcs.tulane.edu
verify error:num=27:certificate not trusted
verify return:1
depth=0 /C=US/ST=Louisiana/L=New Orleans/O=Tulane
University/OU=TIS/CN=majestic.tcs.tulane.edu
verify error:num=21:unable to verify the first certificate
verify return:1
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
---
Certificate chain
 0 s:/C=US/ST=Louisiana/L=New Orleans/O=Tulane
University/OU=TIS/CN=majestic.tcs.tulane.edu
   i:/O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign International
Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY
LTD.(c)97 VeriSign
-BEGIN CERTIFICATE-
MIIFUzCCBLygAwIBAgIQR1Z3EbQ1JJKV6WjFgrYSNDANBgkqhkiG9w0BAQQFADCB
ujEfMB0GA1UEChMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazEXMBUGA1UECxMOVmVy
aVNpZ24sIEluYy4xMzAxBgNVBAsTKlZlcmlTaWduIEludGVybmF0aW9uYWwgU2Vy
dmVyIENBIC0gQ2xhc3MgMzFJMEcGA1UECxNAd3d3LnZlcmlzaWduLmNvbS9DUFMg
SW5jb3JwLmJ5IFJlZi4gTElBQklMSVRZIExURC4oYyk5NyBWZXJpU2lnbjAeFw0w
MDEwMTAwMDAwMDBaFw0wMTEwMTEyMzU5NTlaMIGDMQswCQYDVQQGEwJVUzESMBAG
A1UECBMJTG91aXNpYW5hMRQwEgYDVQQHFAtOZXcgT3JsZWFuczEaMBgGA1UEChQR
VHVsYW5lIFVuaXZlcnNpdHkxDDAKBgNVBAsUA1RJUzEgMB4GA1UEAxQXbWFqZXN0
aWMudGNzLnR1bGFuZS5lZHUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANUP
kVCjbULqy26fEVgTVSatM1nMxVqLqvx8M7VKFwk2b8T0HYNfhBvi9bKBc0iD5nfG
iwfEmh2EYr++Mfb1lBGQUo6g9BBoA5K87tHPsWa1Nvc+m/m7XSVjAzixT+/ggr0k
ym30xduGmZCztz5NJ1ll9LOdZ/LCLek1Oa99lvVzAgMBAAGjggKNMIICiTAJBgNV
HRMEAjAAMIICHwYDVR0DBIICFjCCAhIwggIOMIICCgYLYIZIAYb4RQEHAQEwggH5
FoIBp1RoaXMgY2VydGlmaWNhdGUgaW5jb3Jwb3JhdGVzIGJ5IHJlZmVyZW5jZSwg
YW5kIGl0cyB1c2UgaXMgc3RyaWN0bHkgc3ViamVjdCB0bywgdGhlIFZlcmlTaWdu
IENlcnRpZmljYXRpb24gUHJhY3RpY2UgU3RhdGVtZW50IChDUFMpLCBhdmFpbGFi
bGUgYXQ6IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9DUFM7IGJ5IEUtbWFpbCBh
dCBDUFMtcmVxdWVzdHNAdmVyaXNpZ24uY29tOyBvciBieSBtYW

Re: Dual port popper

[Scott McDermott]

The Doctor on Sat  2/06 17:27 -0600:
> Using Qpopper 4.0.3 how can one set up qpopper to listen on ports 110
> (unsecure) and 995 (secure)

That depends...do you want TLS to be available on 110 as well as 995, or
simple unencrypted POP on 110 and TLS on 995 ?

In either case though, it's simply a matter of setting up your inetd to
give a different configuration file (if you need to even do that) on the
command line of the server bound to each port.  IOW you would have two
qpopper specifications in your inetd configuration file, with the same
stuff but a different configuration file given and port number to bind
to.