Niblett, David A wrote: > Oh for the love of God. Thanks Paul. > > I fixed my own problem WITH a patch that *I* wrote, and I didn't > even put it together. > > I have not heard back from you about that patch. Is there anything > you would like me to fix? Did I break anything?
A couple of things: - you make the login case-insensitive. While I understand your requirement, such a change would require some further discussion. Some people may very well rely on case-sensitive usernames. We try to follow posix compliance here, so case-sensitive is probably a requirement. - you're using regexp code in get_fqun(). Regexp is no-go. Also your domain (gru.net) is hard-coded in there. - no authldap.c integration (which is logical given that your patch is aimed at 2.0). other than that, I like the idea very much. But like I said I will like it better if we can integrate in into the usermap feature, by expanding that new table with IP based mapping/acl fields. Very much a worthy addition to the 2.1 codebase. We need to store the client's sockaddr and pass it to the clienthandlers, and we will also need to fix the listen calls to support a list of addresses, rather than only one like is currently the case. If I can make some time I'll start working on this asap. But these last weeks before the summer holidays are always filled with production deadlines, and exhausted children that need some extra support :-) > > -- > David > > -----Original Message----- > From: Paul J Stevens > To: DBMail mailinglist > Sent: 6/3/2005 4:56 PM > Subject: Re: [Dbmail] Restricting Access > > Niblett, David A wrote: > >>I have an interesting situation and I wonder if any one else has >>something like this and how you deal with it. >> >>Basically we want to do a free Webmail service that has ad's on it. >>For these users I want to only allow them to use the webmail interface >>to view their email (ie. no POP or IMAP). > > > run a separate dbmail-pop3d or imapd process on a dedicated port say > localhost/10110 and connect to that port from your webmail application. > Or better yet, use the new unix-socket support for better performance if > webmail > supports unix-sockets. > > >>We also have users that pay us for Internet access. For them I would >>like to allow POP and IMAP access to their box. > > > Run a seperate one on the usual port 110, publically accessible. > > If we now use your client-ip mapping idea in the usermap framework > recently > added we get: > > login | sock_ok | sock_deny | userid > --------+--------------+-----------+---------------- > clientA | /unix-socket | *:143 | [EMAIL PROTECTED] > clientA | *:143 | | [EMAIL PROTECTED] > > > >>Another type of situation is that if a customer doesn't pay their bill >>we want to not allow them to POP/IMAP their account. > > > clientB | | *:143 | [EMAIL PROTECTED] > > -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
