On Wed, Oct 29, 2008 at 2:36 PM, Ian Eiloart <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I offer an IMAP service to 12000 users, but we don't offer POP3.
>
> However, we have a blind person who has a braille computer, with POP3
> client, but no IMAP client.
>
> I've configured a perdition proxy which can
I can see why you describe it as "well hidden". Thanks for the
enlightenment. I'll endeavor to get all of these points adequately
included in the documentation. Thanks!
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3114
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3115
Am Donnerstag 30 Oktober 2008 18:51:23 schrieb Wesley Craig:
> On 30 Oct 2008, at 12:54, Andreas Winkelmann wrote:
> > Service-Name itself is the given name of the Daemon from
> > cyrus.conf. It is not
> > the service Name from Cyrus-SASL. Separating Options between the
> > Daemons is
> > not a Cy
On 30 Oct 2008, at 12:54, Andreas Winkelmann wrote:
> Service-Name itself is the given name of the Daemon from
> cyrus.conf. It is not
> the service Name from Cyrus-SASL. Separating Options between the
> Daemons is
> not a Cyrus-SASL Feature it is a Cyrus-IMAP Feature. You can use it
> for ot
On 30 Oct 2008, at 12:34, Andrew Morgan wrote:
> I always thought the service name for options was whatever service
> name you put in cyrus.conf. It would be the first column in the
> SERVICES section, such as:
>
> imap cmd="/usr/local/cyrus/bin/imapd" listen="imap"
> prefork=10 maxchi
Am Donnerstag 30 Oktober 2008 17:09:21 schrieb Wesley Craig:
> I think the actual syntax would be:
>
> sasl_pop_pwcheck_method: auxprop
> sasl_pop_auxprop_plugin: sasldb
>
> The documentation (which needs improvement, and since you're getting
> free help on the cyrus list I hope you'll
On Thu, 30 Oct 2008, Wesley Craig wrote:
> What's mentioned in the SASL documentation (which is considerably
> worse than the IMAP documentation, IMHO) is that you can put the
> service name between sasl_ and _option. Also missing is what Cyrus
> IMAP uses for the service names -- I looked in the
I think the actual syntax would be:
sasl_pop_pwcheck_method: auxprop
sasl_pop_auxprop_plugin: sasldb
The documentation (which needs improvement, and since you're getting
free help on the cyrus list I hope you'll open a bugzilla with some
suggested improvements) is mostly in th
Thanks, Andreas. That's probably enough to get me going.
Can I ask how you discovered the "well hidden feature" of imapd.conf? Is
there proper documentation for this anywhere?
--On 29 October 2008 20:16:21 +0100 Andreas Winkelmann <[EMAIL PROTECTED]>
wrote:
>> I offer an IMAP service to 12000
> I offer an IMAP service to 12000 users, but we don't offer POP3.
>
> However, we have a blind person who has a braille computer, with POP3
> client, but no IMAP client.
>
> I've configured a perdition proxy which can give him POP, but not IMAP
> access. However, we're moving toward using Cyrus pr
You can run two saslauthd's, with separate configurations and
separate sockets. The one for pop would use the special ldap filter,
presumably looking for an attribute or something that only users
authorized to use POP would have.
:wes
On 29 Oct 2008, at 09:36, Ian Eiloart wrote:
> I offer
gt;
> - Original Message - From: "Ian Eiloart" <[EMAIL PROTECTED]>
> To:
> Sent: Wednesday, October 29, 2008 2:36 PM
> Subject: offering limited pop access
>
>
>> Hi,
>>
>> I offer an IMAP service to 12000 users, but we don't offer PO
Hi,
I offer an IMAP service to 12000 users, but we don't offer POP3.
However, we have a blind person who has a braille computer, with POP3
client, but no IMAP client.
I've configured a perdition proxy which can give him POP, but not IMAP
access. However, we're moving toward using Cyrus proxyd
13 matches
Mail list logo
