Paul, Ah, didn't understand the regex thing. Now I get it.
I like your extension on the usermap, but right now I need the ability to deal with multiple IP's getting the same domain. In our soon to be production environment, we will have 4 front end servers that will have 4 IP's each. Each IP on a machine will be for domain1.com, second for domain2.com, etc. So it's nice using DBMail so that just in one place do I have to define the IP <-> suffix mapping. At this point like I said, I'm only working with 2.0.4, so I think you have it under control for 2.1, I'm just going to keep on my present course for people that want to stay with 2.0 but would like virtual domains. I'll try and take a look at 2.1 on my home box. Are your changes in the CVS? -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: Paul J Stevens [mailto:[EMAIL PROTECTED] Sent: Monday, June 06, 2005 10:55 AM To: DBMail mailinglist Subject: Re: [Dbmail] Restricting Access Niblett, David A wrote: > - I'll fix the case sensitive and put it back to normal. I would like > to point out that you do case insensitive matches on aliases. That is > why I added case insensitive to the usernames. I'll plan on adding an > option to the dbmail.conf file to OPT which way you would like it. > That seems like it would be the best fix for everyone. > > - If I hard coded my domain in there, well then I'm just an idiot. I > must have left it in there from testing. I'll get that fixed right > away. > > - Don't get why the regex code isn't valid. It's used in the db.c > file, so I just added the header to misc.h and used it. That's where > I stole the idea from. Point is usage of regex is deprecated for 2.1 > > - Yup, sorry, I don't do LDAP. I'd expect it to be pretty easy to add > in there, but I have no way to test, so I'd rather not release a patch > with my name on it that doesn't work. > > You are correct, I'm aiming for the 2.0 code as our policy is not to > run non-stable releases. I looked at the 2.1 and I like the idea > where you are going, but for now my patches will be for the 2.0 > branch. You are certainly welcome to use any code or ideas that I do > in the patches. I'm working on an expanded usermap feature that will allow socket-based virtual hosting in 2.1. Almost finished already for imap. > > In one comment you said I was only looking for 1 IP to name match (if > I interpret you correctly). I think you may be confused. If you put > in the dbmail_domains table: > > 10.0.0.1 xyz.com > 10.0.0.2 xyz.com > 10.0.0.3 abc.com > 10.0.0.4 abc.com > > That will cover any connection to 10.0.0.1 and .2 to have xyz.com > added to the end of the name. .3 and .4 connections will get abc.com. > I cover any number of IP's to any domain. I'll look and verify that, > but as it's running now on a couple of servers just fine, I'm not sure > I understand the problem. Well, since I'm treating this feature as a usermap I'm not initially interested in generic domain-maps where any login on inet/x.x.x.x:143 maps to login<suffix>. I want to get it right with a 1-1 mapping first. After that it should be easy to do more flexible types of mappings such as the one you're proposing. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
