$ to do this? Re: Concept: 'infinate' POP3 accounts per pop3 user.
Seeing as nobody has offered to do this free ;) I'd be interested to hear is anyone out there is interested in developing this project for me. It doesn't seem like a difficult task - security of the resultant qmail-pop3d is also important. I can swing $200-$300 for this. Please email me if you are interested. Regards, Paul. In article 7jhl3c$lvp$[EMAIL PROTECTED] you wrote: In article [EMAIL PROTECTED] you wrote: Paul Gregg writes: Assume this setup is running perfectly (ok, I have 4,000 users using it). Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). What methodology could be used so that if they login with a specific email address as a POP3 user then they only "see" email which is destined for that user. but if they logged in without a user@ part then they would get everything. You'll need a custom POP3 server for that. When the POP3 server initializes and scans the Maildir for messages, it should ignore messages that do not have a Delivered-To: address for the login user. Maildir-based POP3 servers are childishly simple, and you should be able to write one up, or modify an existing one, in no time at all. Ok, I figured out how best to code this up. Essentially, one needs to patch get_list() in qmail-pop3d.c get_list calls maildir_scan() (in maildir.c) to return a list of filenames, which get_list() then parses through to build a list of files/emails which are in the Maildir. This routine needs to also add the Delivered-To: checks that are in serialsmtp.c from the serialmail package. Simply we could call checkpasswd qmail-pop3d Maildir and checkpasswd could exec @ARGV, but add user@host to the args (so qmail-pop3d could read it). The check would need to find the Delivered-To: (first one) line and do a search in the string for /user@host/ (the login pop3 id). (checkpasswd could munge it whatever way you wanted to cover for user%host if you had to). Anyone feel up to the task? I'm afraid my C coding skills leave much to be desired - never got time to learn :(
RE: $ to do this? Re: Concept: 'infinate' POP3 accounts per pop3 user.
I missed the beginning of this thread, so pardon this if it's moot. But I couldn't help noticing that someone wants to use '[EMAIL PROTECTED]' as POP authentication ids. I tried to do this and ran into a serious problem: Netscape Mail chokes on the "@". It assumes you mistakenly entered your email address when you really meant to put your POP id. So it converts it to, in your example, '[EMAIL PROTECTED]', chopping off the '@theirname.domain.com' part. So we chose to avoid the "@". If my C skills were more proficient or I had more time, I'd still keep it as "@" internally but hack checkpassword so that Netscape users only could use an alternate character, such as "%" (thanks, Paul). Dave ... Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). ...
Re: Concept: 'infinate' POP3 accounts per pop3 user.
On Fri, Jun 04, 1999 at 12:57:38AM +, Paul Gregg wrote: Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). Slightly off topic: I know of (at least) one eMail client which assumes user@host is connect(host, pop3) USER user So you should probably also be prepared to handle user%domain@host which should result in connect(host, pop3) USER user%domain \Maex -- SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses Research Development| mailto:[EMAIL PROTECTED] | you funny and you need Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0| a mouse to delete files D-80807 Muenchen | Fax: +49 (89) 32356-299 |
Re: Concept: 'infinate' POP3 accounts per pop3 user.
On Mon, Jun 07, 1999 at 05:28:38PM +0200, Markus Stumpf wrote: On Fri, Jun 04, 1999 at 12:57:38AM +, Paul Gregg wrote: Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). Slightly off topic: I know of (at least) one eMail client which assumes user@host is connect(host, pop3) USER user So you should probably also be prepared to handle user%domain@host which should result in connect(host, pop3) USER user%domain The checkpassword replacement I wrote (with which you can assign domains to users, allowing them to specify infinite POP3 accounts in a file in their homedir, but with separate Maildirs) accepts user@host, user%host and user_host. You can't have it though... Greetz, Peter -- | 'He broke my heart,| Peter van Dijk | I broke his neck' | [EMAIL PROTECTED] | nognikz - As the sun |Hardbeat@ircnet - #cistron/#linux.nl | | Hardbeat@undernet - #groningen/#kinkfm/#vdh |
Concept: 'infinate' POP3 accounts per pop3 user.
Hi all. Consider the following setup: Each user of an ISP has a full "virtualhost" username. Qmail is configured so that [EMAIL PROTECTED] is delivered into their individual Maildir/Pop3 box. Each user logs in with their username 'theirname.domain.com'. Assume this setup is running perfectly (ok, I have 4,000 users using it). Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). What methodology could be used so that if they login with a specific email address as a POP3 user then they only "see" email which is destined for that user. but if they logged in without a user@ part then they would get everything. My inital thoughts are to auth, then create a sub-Maildir and mv the relivant emails into it, set HOME appropriately and launch qmail-pop3d. However, this has implications against "Leave mail on server", so if this happens we need to consider mv-ing emails back to the parent Maildir/cur and tearing down the sub-Maildir. I could do the above described setup ok, but perhaps there may be an issue(s) I haven't considered. Anyone have any thoughts on this? This has obvious application in providing "company wide" or private boxes within a single ISP account setup without having to do anything fancy for each client. Paul. -- Email pgregg at tibus.net | CLUB24 | Email pgregg at nyx.net| Technical Director| INTERNET | System Administrator | The Internet Business Ltd |Free Access| Nyx Public Access Internet | http://www.tibus.net | www.club24.co.uk | http://www.nyx.net |
Re: Concept: 'infinate' POP3 accounts per pop3 user.
Paul Gregg writes: Assume this setup is running perfectly (ok, I have 4,000 users using it). Essentially I'm thinking of enabling the user to login via POP3 as '[EMAIL PROTECTED]' with their normal password. (I've written the checkpasswd so it's easy to authenticate ok). What methodology could be used so that if they login with a specific email address as a POP3 user then they only "see" email which is destined for that user. but if they logged in without a user@ part then they would get everything. You'll need a custom POP3 server for that. When the POP3 server initializes and scans the Maildir for messages, it should ignore messages that do not have a Delivered-To: address for the login user. Maildir-based POP3 servers are childishly simple, and you should be able to write one up, or modify an existing one, in no time at all. -- Sam
