Re: Virtual Domains Aliases
[EMAIL PROTECTED] writes: We are presently Qmail 1.03. We added a virtual domain. To route the mail to the virtual domain users, we had to add an alias for each user. We're actually routing the mail for that domain to a specific mail server. Is there a way to route that email w/o adding an alias for each emember of that domain. Hmmm I don't remember anyone answering your question. Basically, the answer is "yes". When mail comes in to a virtualdomain, it's controlled by the right-hand side. Let's say that mail for example.com is controlled by alias-example. And let's also say that all users @example.com should be delivered to example.crynwr.com. You'd do it like this: ~alias/.qmail-example-default would contain: |forward "$[EMAIL PROTECTED]" -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | "Ask not what your country 521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Virtual Domains Aliases
We are presently Qmail 1.03. We added a virtual domain. To route the mail to the virtual domain users, we had to add an alias for each user. We're actually routing the mail for that domain to a specific mail server. Is there a way to route that email w/o adding an alias for each emember of that domain. Thanks. Ralph Hubbard Systems Engineer Sarcom INC. 8337-A Green Meadows Dr. N Lewis Center, OH 43035 (614) 854-1918 (614) 854-1590 FAX
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 08:39:01AM -0500, [EMAIL PROTECTED] wrote: Set up an entry in virtualdomains like vdomain.foo:alias-virtual-vdomain Every mail to [EMAIL PROTECTED] would be redirected to the local [EMAIL PROTECTED] Set up an ~alias/.qmail-virtual-vdomain-default that contains |/var/qmail/bin/forward `echo $LOCAL | cut -f 4- -d "-"` That cuts the first three parts of alias-virtual-vdomain-user revealing the real username. Look into dot-qmail(5) for explanations of the Enverinmoentvariables. Greetings -- Robert Sander www.gurubert.de
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 03:01:11PM -, Petr Novotny wrote: Set up an ~alias/.qmail-virtual-vdomain-default that contains |/var/qmail/bin/forward `echo $LOCAL | cut -f 4- -d "-"` That cuts the first three parts of alias-virtual-vdomain-user revealing the real username. $DEFAULT would do just fine. But is $DEFAULT not the complete address [EMAIL PROTECTED], or am I missing something here, is it just the user-part? BTW: the man page is qmail-command(8) Greetings -- Robert Sander www.gurubert.de
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 04:40:34PM +0100, Robert Sander wrote: On Fri, Feb 04, 2000 at 03:01:11PM -, Petr Novotny wrote: Set up an ~alias/.qmail-virtual-vdomain-default that contains |/var/qmail/bin/forward `echo $LOCAL | cut -f 4- -d "-"` That cuts the first three parts of alias-virtual-vdomain-user revealing the real username. $DEFAULT would do just fine. But is $DEFAULT not the complete address [EMAIL PROTECTED], or am I missing something here, is it just the user-part? Mail to [EMAIL PROTECTED] is delivered locally as virtual-vdomain-user. If that ends up being handled by ~alias/.qmail-virtual-vdomain-default, then $DEFAULT is user, i.e. the address with virtual-vdomain stripped off. If the address wound up being handled by .qmail-virtual-default, then $DEFAULT would have been vdomain-user. It's the portion of the address that matches the -default part of the .qmail-... file. Chris
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 11:02:09AM -0500, Chris Johnson wrote: Mail to [EMAIL PROTECTED] is delivered locally as virtual-vdomain-user. If that ends up being handled by ~alias/.qmail-virtual-vdomain-default, then $DEFAULT is user, i.e. the address with virtual-vdomain stripped off. If the address wound up being handled by .qmail-virtual-default, then $DEFAULT would have been vdomain-user. It's the portion of the address that matches the -default part of the .qmail-... file. I see, I just thought -default matches the complete [EMAIL PROTECTED] part. Then it is very (and more performant) in .qmail-virtual-vdomain-default: |/usr/bin/forward $DEFAULT should do it. Greetings -- Robert Sander www.gurubert.de
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 05:05:21PM +0100, Robert Sander wrote: On Fri, Feb 04, 2000 at 11:02:09AM -0500, Chris Johnson wrote: Mail to [EMAIL PROTECTED] is delivered locally as virtual-vdomain-user. If that ends up being handled by ~alias/.qmail-virtual-vdomain-default, then $DEFAULT is user, i.e. the address with virtual-vdomain stripped off. If the address wound up being handled by .qmail-virtual-default, then $DEFAULT would have been vdomain-user. It's the portion of the address that matches the -default part of the .qmail-... file. I see, I just thought -default matches the complete [EMAIL PROTECTED] part. Then it is very (and more performant) in .qmail-virtual-vdomain-default: |/usr/bin/forward $DEFAULT should do it. That'll deliver the mail locally. If you want to do that, just make it a local domain. I don't think that's what you want to do. If all mail for this domain is to be sent off to some other server, just list the domain in rcpthosts, remove it from locals and virtualdomains, and put: vdomain.foo:mailserver.for.vdomain.foo in control/smtproutes. Unless I misunderstand your original question, this is all you need to do. Chris
Re: Virtual Domains Aliases
On Fri, Feb 04, 2000 at 11:12:59AM -0500, Chris Johnson wrote: Then it is very (and more performant) in .qmail-virtual-vdomain-default: |/usr/bin/forward $DEFAULT should do it. That'll deliver the mail locally. If you want to do that, just make it a local domain. I don't think that's what you want to do. If all mail for this domain is to be sent off to some other server, just list the domain in rcpthosts, remove it from locals and virtualdomains, and put: vdomain.foo:mailserver.for.vdomain.foo in control/smtproutes. Unless I misunderstand your original question, this is all you need to do. It was not my original question. But the thread was useful to me because I have a setup with a mailserver handling several domains and every user is a local one. I have set up virtualdomains in the described way to handle them. But $DEFAULT would just do it, too. Greetings -- Robert Sander www.gurubert.de