On Tue, 23 Dec 2003 11:13:27 -0600 Tim Legant <[EMAIL PROTECTED]> wrote:
> MT <[EMAIL PROTECTED]> writes: > > > On Mon, 22 Dec 2003 18:22:47 -0600 > > Tim Legant <[EMAIL PROTECTED]> wrote: > > > >> You'll have to give us information about the user in virtualdomains, > >> the actual system user (they're probably the same, but may not be) and > >> any lines related to 'open2web.com' in users/assign. > > > > System user is o2w > > > > cat /var/qmail/users/assign > > =mt:o2w:512:512:/home/o2w::: > > +mt-:o2w:512:512:/home/o2w:-:: > > This is half of what I need. How is open2web configured in > 'virtualdomains'? If it's not, then that's the problem. If it is, > then I still need to see how in order to tell you how to fix this. I > also need to know how you want open2web.com configured. Is all mail > supposed to be handled by the 'o2w' user? Or does some open2web.com > mail go to other system users? > > For example: If 'virtualdomains' says "open2web.com:o2w", then you > don't need anything in 'users/assign'. All mail to any address at > open2web.com will automatically be delivered to the 'o2w' user. You > can trap each address with a /home/o2w/.qmail-<address> file. If this > isn't working, make sure you don't have anything about open2web.com in > 'locals' or 'users/assign' and if users/assign is empty, make sure > that 'users/cdb' doesn't exist. > > Also, since this is really a qmail configuration question, you should > probably spend some time carefully reading the relevant qmail man > pages: qmail-send(8), qmail-lspawn(8), qmail-local(8) and > qmail-users(5) will explain how the various pieces in the delivery > process fit together. Hi Tim, open2web is not configured in /var/qmail/control/virtualdomains. In fact in an earlier post you recommended that I remove: cat /var/qmail/alias/.qmail-mt &o2w As "This configuration is for qmail delivering directly to system users." And then you recommended that an "easier way to handle this is to set up 'mt' in the users/assign file:" /var/qmail/users/assign: +mt:o2w:<o2w_UID>:<o2w_GID>:/home/o2w::: So that's what I have done. There was no mention of putting open2web in /var/qmail/control/virtualdomains. Here is another quote from your previous post: "From now on, all mail to [EMAIL PROTECTED] will be delivered to the o2w system user and qmail will use the .qmail and .qmail-default files for delivery instructions. No forwarding is necessary. The single line in the users/assign file handles both the base address, "mt", and all extension addresses, "mt-*"." "This is much easier than forwarding, inserting headers, setting RECIPIENT_HEADER in the config file and so forth. None of that is necessary if you use the users/assign file." Then in my last post I admit I got a bit mixed up about "bounce" and "double bounce" and "BOUNCE_ENV_ADDRESS" (which I now know doesn't exist) and "BOUNCE_ENV_SENDER". The question remains, though, that I never really dealt with [EMAIL PROTECTED], which, as far as I understand, is supposed to What I was trying to understand in this present thread has to do with Jim Ramsay's post: "I drop all mail incoming to my BOUNCE_ENV_ADDRESS as it is only ever generated if the original incoming mail used a bad envelope sender (implying spam), in which case I don't want to see either the original message or the bounce notice." BOUNCE_ENV_ADDRESS should, of course be, BOUNCE_ENV_SENDER I responded by posting the following: BOUNCE_ENV_SENDER = "[EMAIL PROTECTED] cat /var/qmail/alias/.qmail-nobody # cat ~/.qmail-nobody # cat ~/.qmail-o2w-nobody # Then you tell me that my "BOUNCE_ENV_SENDER is set properly if you wish to ignore these. However, you're ignoring them in the wrong place (/var/qmail/alias). So what I did is: rm /var/qmail/alias/.qmail-nobody I thought I should create +nobody:o2w:<o2w_UID>:<o2w_GID>:/home/o2w::: Which points to: cat ~/.qmail-nobody # cat ~/.qmail-o2w-nobody # And gets dumped in the process. I admit I haven't inserted "+nobody:o2w:<o2w_UID>:<o2w_GID>:/home/o2w:::" into the assign file because I first wanted to verify with you. I hope my explanation isn't too convoluted. Thanks, Mark _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
