Re: converting from qpopper

[Sergey Poznyakoff]

> In that case, why not always build popauth.  I see it as a general utility:
> - Could extend again mu_db.c to support more then one DB
>     popauth --type=db2 // or something

Actually, this can be done at mu_dbm level, then pop3d will behave the
same way: pop3d --daemon --type=db2...

> - Could cover the most of qpopper options
> 
> - popauth in its own directory and always compile,
>   unless no supporting DB was found

If it could be used for other purposes as well, then surely it
deserves its own subdir. But then its name is kind of a misnomer:
we'll have to rename it to something more appropriate, won't we?
(Making a softlink to popauth, for compatibility)

> > Well, returning to our muttons, was pop3d able to understand qpopper's
>                        ^^^^^^^^^
> [[laughs]]
> 8-)
> Is that english?

:^) I believe so. Jeff?

-Sergey