Re: Virtualdomains - AGAIN
Travis Leuthauser wrote: > Stephen Bosch wrote: > > > Actually, I want to make sure that mail addressed to > > address_set1@vdomain1 will only be accepted if it is sent to > > address_set1@vdomain1, but bounced or dumped if it is sent to > > address_set1@vdomain2; mail addressed to address_set2@vdomain2 will be > > accepted while mail to address_set2@vdomain1 will be bounced or dumped > > -- WHERE address_set1 and address_set2 are part of the total user space > > on the qmail box (that is, recipient exists only once on the system; > > recipient may be part of address_set1 *or* address_set2 but not both > > simultaneously)... > > If I understand what you're wanting properly, then what you want to do is > list your virtual domains in control/virtualdomains and in the home > directory for each virtual domain, define .qmail files for EVERY address > @virtualdomain.com, but do not put a .qmail-default file. That will cause > qmail to look for .qmail files in the home directories and if it does not > find one, then it will bounce the mail. > > Hope that helps and makes sense, It does. Thanks for all the help, everyone -- I followed your instructions and I am getting the desired results. I guess I didn't fully understand how the virtualdomains feature worked; I didn't realize that qmail would bounce the mail without a corresponding .qmail-[recipient] or .qmail-default. That's perhaps one area, though, that the documentation or LWQ might be made *just a tad* clearer -- it's great so far, but I imagine that one extra line of text would be enough to minimize confusion even further. I'll see if I can come up with that magic line *chuckles* it's all a bit funny to me right now. I'm feeling decidedly like a punch-card computer scientist at the moment =) Again, thanks -Stephen- > > Travis Leuthauser > Network Administrator > WinConX Online, Inc. > 225-751-0959 > 225-752-6517
Re: Virtualdomains - AGAIN
It's in the docs, sorry I can't say exactly where though.. they work the same as all the other .qmail files. .qmail-address Contents: &account to deliver mail to Travis Leuthauser Network Administrator WinConX Online, Inc. 225-751-0959 225-752-6517 - Original Message - From: "dG" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 19, 2000 5:29 PM Subject: Re: Virtualdomains - AGAIN > .qmail files for EVERY address > > @virtualdomain.com, but do not put a .qmail-default file. > > What would the naming format and contents of those .qmail filez be? If its > in the docs then RTFM works for me :) > >
Re: Virtualdomains - AGAIN
On Tue, Sep 19, 2000 at 05:29:28PM -0500, dG wrote: > .qmail files for EVERY address > > @virtualdomain.com, but do not put a .qmail-default file. > > What would the naming format and contents of those .qmail filez be? If its > in the docs then RTFM works for me :) man dot-qmail for contents, man qmail-local for naming format when using virtualdomains I think. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me
Re: Virtualdomains - AGAIN
.qmail files for EVERY address > @virtualdomain.com, but do not put a .qmail-default file. What would the naming format and contents of those .qmail filez be? If its in the docs then RTFM works for me :)
Re: Virtualdomains - AGAIN
- Original Message - From: "Stephen Bosch" <[EMAIL PROTECTED]> To: "qmail" <[EMAIL PROTECTED]> Sent: Tuesday, September 19, 2000 3:58 PM Subject: Re: Virtualdomains - AGAIN > > > Hello =) > > Charles Cazabon wrote: > > > > You can probably see by now that I have a common user space. What I want to > > > do is prevent mail sent to [EMAIL PROTECTED] from also being > > > accepted as [EMAIL PROTECTED] I look at the above virtualdomains > > > scenario and ask myself why I am even bothering with virtualdomains, since > > > putting both domains in control/locals and control/rcpthosts will get me the > > > same result. > > > > If you mean to say that you _want_ email to any_address@vdomain1 and > > any_address@vdomain2 to be interchangeable with mail to any_address@localdomain, > > then just putting those domain names into locals makes more sense. > > Virtual domains add flexibility for other things, though. > > Actually, I want to make sure that mail addressed to > address_set1@vdomain1 will only be accepted if it is sent to > address_set1@vdomain1, but bounced or dumped if it is sent to > address_set1@vdomain2; mail addressed to address_set2@vdomain2 will be > accepted while mail to address_set2@vdomain1 will be bounced or dumped > -- WHERE address_set1 and address_set2 are part of the total user space > on the qmail box (that is, recipient exists only once on the system; > recipient may be part of address_set1 *or* address_set2 but not both > simultaneously)... If I understand what you're wanting properly, then what you want to do is list your virtual domains in control/virtualdomains and in the home directory for each virtual domain, define .qmail files for EVERY address @virtualdomain.com, but do not put a .qmail-default file. That will cause qmail to look for .qmail files in the home directories and if it does not find one, then it will bounce the mail. Hope that helps and makes sense, Travis Leuthauser Network Administrator WinConX Online, Inc. 225-751-0959 225-752-6517
Re: Virtualdomains - AGAIN
Stephen Bosch <[EMAIL PROTECTED]> wrote: > > Actually, I want to make sure that mail addressed to > address_set1@vdomain1 will only be accepted if it is sent to > address_set1@vdomain1, but bounced or dumped if it is sent to > address_set1@vdomain2; mail addressed to address_set2@vdomain2 will be > accepted while mail to address_set2@vdomain1 will be bounced or dumped > -- WHERE address_set1 and address_set2 are part of the total user space > on the qmail box (that is, recipient exists only once on the system; > recipient may be part of address_set1 *or* address_set2 but not both > simultaneously)... Use virtual domains, controlled by a user account. For virtual domain 1, controlled by vuser1, have .qmail-extension files for each address you want to be valid. Ditto for virtual user/domain 2. Make sure that vuser1 does not have any .qmail-extension files for addresses who should be in virtual domain 2 only, and vice versa. Ensure that neither user has .qmail-default files. Note that prepend values change the above slightly if you use them. > Is that better? Clearer. Charles -- -- Charles Cazabon <[EMAIL PROTECTED]> QCC Communications Corporation Saskatoon, SK My opinions do not necessarily represent those of my employer. --
Re: Virtualdomains - AGAIN
Hello =) Charles Cazabon wrote: > > You can probably see by now that I have a common user space. What I want to > > do is prevent mail sent to [EMAIL PROTECTED] from also being > > accepted as [EMAIL PROTECTED] I look at the above virtualdomains > > scenario and ask myself why I am even bothering with virtualdomains, since > > putting both domains in control/locals and control/rcpthosts will get me the > > same result. > > If you mean to say that you _want_ email to any_address@vdomain1 and > any_address@vdomain2 to be interchangeable with mail to any_address@localdomain, > then just putting those domain names into locals makes more sense. > Virtual domains add flexibility for other things, though. Actually, I want to make sure that mail addressed to address_set1@vdomain1 will only be accepted if it is sent to address_set1@vdomain1, but bounced or dumped if it is sent to address_set1@vdomain2; mail addressed to address_set2@vdomain2 will be accepted while mail to address_set2@vdomain1 will be bounced or dumped -- WHERE address_set1 and address_set2 are part of the total user space on the qmail box (that is, recipient exists only once on the system; recipient may be part of address_set1 *or* address_set2 but not both simultaneously)... air! *INHALES* Is that better? Stephen Bosch
Re: Virtualdomains - AGAIN
On Tue, Sep 19, 2000 at 02:34:16PM -0600, Charles Cazabon wrote: > Stephen Bosch <[EMAIL PROTECTED]> wrote: > > > > Okay, this is a foolish newbie question. I'm having trouble wrapping my > > head around the problem. > > A newbie who has apparently read, and understood, most of the documenation, > FAQs, Life with qmail, ... what a novelty! No, this is Dave Sill playing a trick on us, I think. :) --Adam
Re: Virtualdomains - AGAIN
Stephen Bosch <[EMAIL PROTECTED]> wrote: > > Okay, this is a foolish newbie question. I'm having trouble wrapping my > head around the problem. A newbie who has apparently read, and understood, most of the documenation, FAQs, Life with qmail, ... what a novelty! > In control/virtualdomains we put > > @virtualdomain.org:username > > (question - is the prepend *required*?) If you mean whatever is after the colon, yes -- an empty prepend means the domain is not virtual. If you mean an optional "-extension" after a username after the colon, then that is indeed optional. It's one of the few areas which I find djb's documentation isn't perfectly clear on. > Now all mail to virtualdomain.org will be sent to the local extension address > [EMAIL PROTECTED] > > But I still want to make sure that mail is delivered to the local user > recipient, so I create the file > > ~username/.qmail-recipient > > and I put > > &recipient > > in it. > > You can probably see by now that I have a common user space. What I want to > do is prevent mail sent to [EMAIL PROTECTED] from also being > accepted as [EMAIL PROTECTED] I look at the above virtualdomains > scenario and ask myself why I am even bothering with virtualdomains, since > putting both domains in control/locals and control/rcpthosts will get me the > same result. If you mean to say that you _want_ email to any_address@vdomain1 and any_address@vdomain2 to be interchangeable with mail to any_address@localdomain, then just putting those domain names into locals makes more sense. Virtual domains add flexibility for other things, though. > Did that make any sense? Mostly. Charles -- -- Charles Cazabon <[EMAIL PROTECTED]> QCC Communications Corporation Saskatoon, SK My opinions do not necessarily represent those of my employer. --
Virtualdomains - AGAIN
Okay, this is a foolish newbie question. I'm having trouble wrapping my head around the problem. We have two ways of accepting mail for a domain. We can either treat it as a local, *real* domain, or we can treat it as a virtual domain which supplements a real domain. If we treat it as a local real domain, we put it in control/rcpthosts and control/locals. Mail addressed to [EMAIL PROTECTED] and [EMAIL PROTECTED] will be delivered to the local user foobar. If we treat it as a virtual domain, we put it in control/rcpthosts and control/virtualdomains but *not* control/locals. In control/virtualdomains we put @virtualdomain.org:username (question - is the prepend *required*?) Now all mail to virtualdomain.org will be sent to the local extension address [EMAIL PROTECTED] But I still want to make sure that mail is delivered to the local user recipient, so I create the file ~username/.qmail-recipient and I put &recipient in it. You can probably see by now that I have a common user space. What I want to do is prevent mail sent to [EMAIL PROTECTED] from also being accepted as [EMAIL PROTECTED] I look at the above virtualdomains scenario and ask myself why I am even bothering with virtualdomains, since putting both domains in control/locals and control/rcpthosts will get me the same result. Did that make any sense? Thanks, Stephen Bosch
Re: virtualdomains (again)
ryan p bobko <[EMAIL PROTECTED]> wrote: > > and finally, my virtualdomains: > > Y:bronco15 > mail.Y:bronco15 > > > My understanding is that all mail to Y or mail.Y will go to user bronco15. However, >when I send mail to ryan@Y, I get the following message: > > > Hi. This is the qmail-send program at X. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > : > Sorry, no mailbox here by that name. (#5.1.1) Mail for ryan@Y will be delivered to bronco15-ryan on the local machine. If bronco15 doesn't have a .qmail-ryan, and doesn't have a .qmail-default, it will bounce. Charles -- -- Charles Cazabon <[EMAIL PROTECTED]> QCC Communications Corporation Saskatoon, SK My opinions do not necessarily represent those of my employer. --
Re: virtualdomains (again)
On Mon, Sep 11, 2000 at 08:47:58PM -0400, Adam McKenna wrote: > On Mon, Sep 11, 2000 at 05:43:16PM -0700, ryan p bobko wrote: > > I don't see why it should have anything to do with ryan's .qmail-default. > > Isn't the whole point that the mail gets forwarded to bronco15? I'd like > > all users (even the ones that don't exist) to be forwarded to the user > > bronco15 (who does exist). > > Kindly wrap your email at 78 characters. > > If you want this type of behavior, then create a .qmail-default file in > ryan's homedir. If you want to know how it works or why it is this way, man Sorry, I meant to say bronco15's homedir, not ryan's. brain fart. --Adam
Re: virtualdomains (again)
On Mon, Sep 11, 2000 at 05:43:16PM -0700, ryan p bobko wrote: > I don't see why it should have anything to do with ryan's .qmail-default. > Isn't the whole point that the mail gets forwarded to bronco15? I'd like > all users (even the ones that don't exist) to be forwarded to the user > bronco15 (who does exist). Kindly wrap your email at 78 characters. If you want this type of behavior, then create a .qmail-default file in ryan's homedir. If you want to know how it works or why it is this way, man qmail-send and dot-qmail. --Adam
Re: virtualdomains (again)
On Mon, Sep 11, 2000 at 05:34:19PM -0700, ryan p bobko wrote: > : > Sorry, no mailbox here by that name. (#5.1.1) Does ryan have a .qmail-default file in his homedir? --Adam
virtualdomains (again)
Hi, I know this topic has been beaten to death, but I just can't get virtualdomainsto work in my setup. Hopefully some kind soul can help, especially since this seems to be the most vanilla setup I could have. Just like the FAQs say, I want to have all mail for the domain Y to be delivered to a user a domain X. I control both domains, and they're both on the same server. my locals file: mail.X X my rcpthosts file: mail.X mail.Y X Y and finally, my virtualdomains: Y:bronco15 mail.Y:bronco15 My understanding is that all mail to Y or mail.Y will go to user bronco15. However, when I send mail to ryan@Y, I get the following message: Hi. This is the qmail-send program at X. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : Sorry, no mailbox here by that name. (#5.1.1) What's going on! This setup couldn't be more straightforward, so I'm starting to think that perhaps there is a compile-time configuration option or something. Again, any help you be enormously welcome. Thanks, ryan -- "Ain't that something what happened today. One of us got traded to Kansas City." -- Casey Stengel, informing outfielder Bob Cerv he'd been traded
