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? -- 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 _______________________________________________ Dbmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
