Brian Grossman writes:
Actually, we're only using courier for the webmail so far. Our pop system
is still back in the qmail ages. In that pop auth system (using the same
daemon), there's a way to pass around meta information (like "don't check
more than once every 10 minutes; see http:blah"). Is there in courier? It
would be handy in smtpd and webmail too.
There are no frequency limits there right now. There is a way to shoehorn
in some custom code into authentication.
Glad you caught that. Please consider it a feature request...
It is definitely something I want to do. Next year.
And since I'm at it, it would be nice to be able to have a custom auth
module be able to carry around some extra data. Custom error messages is
one example.
You can already do that -- with environment variables. That's how a
non-default location of the account's maildir gets set. It's just a matter
of defining additional environment variables, making sure that they are
initialized up front, and then doing whatever needs to be done with them.
And of course, there's being able to specify the extension
from the auth module, the idea being to replace the aliases file with a
database lookup.
You can already read the alias file from an LDAP directory. There's no
technical reason it can't be read off a MySQL table as well, it just hasn't
been done.
5 messages in net.sourceforge.lists.courier-users[courier-users] Re: login frequency R...
