headers
qpopper-request | 1 May 2004 09:02
Favicon

Qpopper Monthly Help File

         M O N T H L Y   Q P O P P E R   L I S T   H E L P

Addresses:
----------

Email addresses for this particular list server:

  List server:           qpopper-request <at> lists.pensive.org
  Everyone on the list:  qpopper <at> lists.pensive.org
  Human in charge:       listmaster <at> lists.pensive.org

Virtually,
The List Server Admin <listmaster <at> lists.pensive.org>
Permalink | Reply | 0 comments |
headers
Mike | 6 May 2004 08:25

Problem compiling qpopper on Mandrake 9.2

I recently upgraded to a new box with Mandrake 9.2 and have not been able 
to install qpopper 4.0.5.

I had previously installed qpopper 4.0.5 on Mandrake 9.0 with no problem.

After running configure (./configure --with-openssl=/usr/local/ssl) with no 
problem, I get the following when I try to make:

         -I../common ../common/libcommon.a \
         -lcrypt -L/usr/local/ssl/lib -lssl -lcrypto
../common/libcommon.a(maillock.o)(.text+0x3fc): In function `Qmaillock':
/home/mail/qpopper4.0.5/common/maillock.c:278: the use of `tempnam' is 
dangerous, better use `mkstemp'

While I have considered using a different POP server, I'd prefer to get 
qpopper up and running.

Any suggestions for how I can get qpopper to properly compile?

Thanks in advance.
Permalink | Reply | 2 comments |
headers
The Little Prince | 6 May 2004 09:06

Re: Problem compiling qpopper on Mandrake 9.2


On Wed, 5 May 2004, Mike wrote:

> I recently upgraded to a new box with Mandrake 9.2 and have not been able 
> to install qpopper 4.0.5.
> 
> I had previously installed qpopper 4.0.5 on Mandrake 9.0 with no problem.
> 
> After running configure (./configure --with-openssl=/usr/local/ssl) with no 
> problem, I get the following when I try to make:
> 
>          -I../common ../common/libcommon.a \
>          -lcrypt -L/usr/local/ssl/lib -lssl -lcrypto
> ../common/libcommon.a(maillock.o)(.text+0x3fc): In function `Qmaillock':
> /home/mail/qpopper4.0.5/common/maillock.c:278: the use of `tempnam' is 
> dangerous, better use `mkstemp'
> 

this warning doesn't stop the binary from being compiled. ignore it.

--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco                            Network Administrator/Engineer
thelittleprince <at> asteroid-b612.org              http://www.asteroid-b612.org

     "It's not easy bein' green..there's so many colors I'd rather be"
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Permalink | Reply | 1 comment |
headers
Mike | 6 May 2004 20:01

Re: Problem compiling qpopper on Mandrake 9.2

At 5/6/2004 12:06 AM, The Little Prince wrote:

> > After running configure (./configure --with-openssl=/usr/local/ssl) 
> with no
> > problem, I get the following when I try to make:
> >
> >          -I../common ../common/libcommon.a \
> >          -lcrypt -L/usr/local/ssl/lib -lssl -lcrypto
> > ../common/libcommon.a(maillock.o)(.text+0x3fc): In function `Qmaillock':
> > /home/mail/qpopper4.0.5/common/maillock.c:278: the use of `tempnam' is
> > dangerous, better use `mkstemp'
> >
>
>this warning doesn't stop the binary from being compiled. ignore it.

Thanks.  That caused me to dig deeper into the problem(s) I was having.

It turned out to be a problem with the certificate.  I compiled a 
certificate that required a password, so it was requesting a password every 
time I attempted to connect to qpopper, since I configured qpopper to only 
accept SSL connections.
Permalink | Reply | 0 comments |
headers
Arne Brutschy | 11 May 2004 10:20
Picon

Problem using chained certificates

Hello,

I hava a problem using chained certificates. My certificate chain looks 
like (ascii art ole!):

User has:     Root CA Cert
                    |
                    /
                    |
                Sub CA Cert
Server sends:      |
                Server Cert

So I tried to put all server side certificates (SubCA and Server cert) 
in one file:

-----BEGIN RSA PRIVATE KEY-----
  server private key
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
  server cert
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
  sub ca certs
-----END CERTIFICATE-----

This usually works with other servers (ie. UW IMAP). The server sends 
the complete certificate chain except the root certificate. This 
certificate is installed on the client, which can verify the complete chain.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lisa Casey | 26 May 2004 19:35

qpopper timeout

Hi,

I am running qpopper 4.0.4 on a Red Hat box. I have this file:
/etc/xinetd.d/ipop3 which contains this:

# default: off
# description: The POP3 service allows remote users to access their mail \
#              using an POP3 client such as Netscape Communicator, mutt, \
#              or fetchmail.
service pop3
{
        socket_type             = stream
        wait                    = no
        user                    = root
        server                  = /usr/local/sbin/popper
#       server                  = /usr/sbin/ipop3d
        server_args             = -R
        log_on_success          += USERID
        log_on_failure          += USERID
        disable                 = no
        server_args  =  qpopper -s -T 600
}

Yet I am still seeing 120 sec timeouts in maillog:

May 26 08:32:21 Raydeus-Dee popper[6041]: (4.0.4) POP login for dkbost at
(XX.XX.XX.XX) XX.XX.XX.XX
May 26 08:34:21 Raydeus-Dee popper[6041]: (v4.0.4) Timeout (120 secs) during
nw read from dkbost at XX.XX.XX.XX (XX.XX.XX.XX)
(Continue reading)

Permalink | Reply | 0 comments |

Gmane