The FreeBSD Diary |
![]() |
(TM) | Providing practical examples since 1998 |
|
qpopper with APOP
30 March 2001
|
|
|
I'll show how I installed qpopper and then set up the APOP database. You will need an APOP capable client. |
|
|
Install
|
|
Since I have the entire ports tree installed, all I needed
to do was:/usr/ports/mail/qpopper make install Then I added the following line to /etc/inetd.conf:
Then I restarted inetd:
|
|
|
The APOP database
|
|
I started reading man qpopauth. Guessing, I did the
following steps:
The password I set above is what is known as the "shared secret". That's what you set in your APOP client. NOTE: if you add a user to the database, they must use APOP. They cannot use plain POP. If they try to use plain POP, they will be told their password is incorrect. |
|
|
/etc/hosts.allow
|
|
Don't forget to allow qpooper access via /etc/hosts.allow. Here's what I added to my file. Adjust for your domain.
This will allow anyone from example.org to use qpopper. They will still have to authenticate as usual (user id, password, shared secret). |
|
|
A word of caution
|
|
| APOP doesn't secure your mail messages. All it does is secure your password. Your mail message will still be downloaded in clear text. But that's not really a security issue. Chances are, your mail was delivered to your mail server in clear text too. Only you can decide if APOP is appropriate to your location. | |
|
stunnel
31 March 2001
| |
| Felipe Gustavo de Almeida wrote in to say that stunnel encrpts
all POP data. Have a read of this from /usr/ports/security/stunnel/pkg-descr:
|
|
|
popautd
4 April 2001
| |
Rob Hudson wrote in to say:
|
|