Michael Nguyen writes:
Courier already includes the facility for selectively control which
services
can be used to access the account. Example: "disableimap=1" option
disables IMAP access to the account; POP3 access still goes through; et
alâ
Hmm...so how would I make this work for me... What I need is the following:
Consider user "BasicUser1".
BasicUser1 does not have the authority to use POP3 and IMAP via her local
MUA (e.g. Outlook Express). However, she does have the authority to use the
website to check her mail. We differentiate what she can and cannot do
based on her user status (an integer in the database).
I'm presuming that for webmail access you're not using sqwebmail.
If you were, then you'd simply set
"disableimap=1,disablepop3=1,disablewebmail=0". Problem solved.
The way we currently do it seems very sloppy, but it does work. If we could
somehow streamline it into a something sleek and beautiful, I'd love to. Do
you still think that Courier has enough as-is to do what I want? If so,
could you give me a concrete example as to how you'd do this?
If you want to "streamline" things, the first thing you should get rid of is
the whole concept of webmail-over-IMAP. It adds unnecessary overhead, and
overcomplicates things more than they have to be.
Another alternative is to create duplicate records in your authentication
table. Same account home directory, maildir, userid and groupid. Different
userid and password. You create one record that's used by webmail, and
another record that's used for external user logins.
pgpaWbaIyXjZp.pgp
Description: PGP signature
