2006/5/3, Yasuda Yutaka <yasuda (at mark) mfc.bakkers.gr.jp>:
> Hi Devon,
>
> If it is possible, tell us please about the APOP issue.
> You dropped it? Or support it?
> If supported, I am interesting how. So where is the
> best place to keep clear-text password for APOP...
>
> Thanks.
> Yasu.
Hi Yasu,
At the moment, we install both packages, and you can choose to use one
or the other. Eventually qpopper will be obsoleted, and APOP will be
abandoned (replaced with POP3S and IMAPS). I don't have any plans to
support it in the near future, in any case.
--Devon
> On 2006/05/04, at 6:16, Devon H. O'Dell wrote:
>
> > We have recently integrated Dovecot support into RAQdevil.
> >
> > --Devon
> >
> >
> > 2006/5/3, Yasuda Yutaka <yasuda (at mark) mfc.bakkers.gr.jp>:
> >> Hi Shibuya-san,
> >>
> >> Primarily, it sounds good to add POPS/IMAPS feature to BlueQuartz.
> >> And my opinion is;
> >> . drop APOP and let us go to POPS/IMAPS
> >> . don't think about "switchable" setup for backward compatibility
> >>
> >> But I think it is better to show my thought in this time.
> >>
> >> So, one of the advantage of Cobalt is the integration of
> >> several authentication methods and password management
> >> into single UI. User can change their password by telling
> >> the replacement password to UI at *once*.
> >> It is a key. very key.
> >>
> >> As a guy said, Dovecot may support APOP in future release.
> >> (or current version already has well tested APOP feature,
> >> but I am not sure. see below.)
> >>
> >> Either or, I am afraid that the UI level integration will be broken.
> >> I mean we may not able to integrate Dovecot APOP password
> >> change function. As you know, APOP needs not-encrypted
> >> password string then Qpopper use special password command
> >> named "popauth". But Cobalt succeed to hide it from user.
> >>
> >> This is a problem.
> >> So it is okay to add APOP feature to BlueQuartz using Dovecot
> >> if we can integrate it. If it is not possible, it is better that we
> >> give up APOP support.
> >>
> >> Regards,
> >> Yasu.
> >>
> >> Just for your information, Dovecot APOP issue which I understand;
> >>
> >> . wiki shows up Dovecot doesn't (or doesn't want) support
> >> APOP as their policy, see;
> >> http://wiki.dovecot.org/Authentication
> >> . Timo Sirainen (author of Dovecot) said version 1.0-tests
> >> support APOP in Feb. 2005;
> >> http://www.dovecot.org/list/dovecot/2005-February/006320.html
> >> . In Oct. 2005, Timo said APOP works;
> >> http://dovecot.org/list/dovecot/2005-October/009500.html
> >> . the recent source codes seems to have APOP support code for
> >> POP3 access. See; src/pop3-login/client-authenticate.c
> >>
> >> but as I did glance Dovecot website, Timo is not
> >> active enough to support APOP totally.
> >>
> >> (And I did not test Dovecot by myself, sorry!)
> >>
> >>
> >>
> >
> >
> >
>
>
>