Alternate directory for .qmail files
Hello- I was wondering if anybody had a patch to make qmail-local look in an alternate directory for .qmail files before going to $HOME. I know I saw somewhere that somebody had done something like this, but I've been unable to find it again. If all else fails, I will just go ahead and hack away at qmail-local myself, but I was hoping somebody out there could make my job easier. Thank you, Ben
Re: Alternate directory for .qmail files
On Fri, 23 Feb 2001, Alex Pennace wrote: > On Fri, Feb 23, 2001 at 07:01:48PM -0700, Ben Schumacher wrote: > > I was wondering if anybody had a patch to make qmail-local look in an > > alternate directory for .qmail files before going to $HOME. I know I saw > > somewhere that somebody had done something like this, but I've been unable > > to find it again. > > You can use the qmail-users mechanism to reach the same goal. I saw something about doing that on the qmail.org page, however, this is really not the ideal solution for what I'm trying to do. My goal is to make a web based management system for this, and I'd prefer to keep most everything out of the users home directory, for the sake of security and simplicity. Basically, I want to setup another directory that will have a subdirectory for each user on the system, with .qmail files that are written by the administrative interface, and the virtual POP boxes for these users. Similar to what vpopmail does, but in a way that doesn't negate the ability to have mail delivered to good old '/var/mail/$USER' boxes for those who would rather use a shell. Thanks, Ben
qmail+system accounts+virt. dom. POPs
Let me just get straight to what I'm trying to do and see if somebody can help me figure out how to do it. I'm setuping up a server to do virtual domain and email hosting for customers. I'm assuming that 90% of the customers using my system will want to do just POP3 email for their domains, however, I want to make it possible for the other 10% to use a shell account to access their email. Rather than make this a necessarily either or situation, I want to make it so that if they have POP3 email accounts, their mail will be default be delivered to those, but everything else will go into their standard system account. Because I want to make this system compatible with Pine, elm, etc, I would prefer to use the old mailbox format for the system accounts, but use Maildir, or MAilbox, for the POP3 accounts. So here's what I need. I want to find a way to using a simple POP3 daemon, that can handle both Mailbox and Maildir formats, and will look to a customers system (/var/mail) box if their username in the POP3 protocol is just a username, or in their virtual POP3 box if their username is '[EMAIL PROTECTED]'. I realize this is probably a horribly complicated system, but I think it would help my service appeal to both the power (shell & POP3 -- like me) user, and more standard (POP3-only) users. Any ideas on how to set this up would be greatly appreciated. Ben
mbox POP3 Server w/Virtual Domain Support
For various reasons, I need to find a good POP3 which can handle both the mbox server and virtual domains. Basically I need to be able to allow my users to have both shell and POP3 access to their mail, and since they will be using clients such as Pine, elm and others, I'm going to need to support the mbox format. Could somebody please point me in the direction of a good mbox format POP3 server. I've looked into qpopper and spop3d, but neither of these have native support for virtual domains as well. Thanks in advance, Ben Schumacher