On Wed, 24 Dec 2003 12:06:12 -0600
Tim Legant <[EMAIL PROTECTED]> wrote:
> MT <[EMAIL PROTECTED]> writes:
>
> > 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."
>
> Yup, I remember this.
>
> > 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.
>
> Ok.
>
> > There was no mention of putting open2web in
> > /var/qmail/control/virtualdomains.
>
> Ok. So this means that open2web.com is in /var/qmail/control/locals
> and that, for the most part, addresses at open2web.com are real system
> users. That is, any system users in /etc/passwd are valid email
> addresses in the 'open2web.com' domain. For example, system user
> 'joe' should receive mail to '[EMAIL PROTECTED]'.
In fact, there isn't one address at open2web.com who is a real system user. All users
are like 'mt', as in non-system users.
>
> > 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-*"."
>
> That's correct. Since there is no system user 'mt', you need to route
> that mail to the 'o2w' system user, preserving extension addresses so
> that TMDA will work.
>
> > 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
> > #
>
> In the configuration you have explained above, ~alias/.qmail-nobody
> is the file qmail will use to process mail to '[EMAIL PROTECTED]',
> unless there is a system user named 'nobody'.
>
> > cat ~/.qmail-nobody
> > #
> >
> > cat ~/.qmail-o2w-nobody
> > #
>
> I have no idea what system user the tilde ('~') represents in these
> two paths....
Sorry, this should have said:
cat /home/o2w/.qmail-nobody
#
cat /homeo2w/.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).
>
> I hadn't remembered your configuration and guessed that the 'o2w'
> system user was supposed to be handling all open2web.com mail. In
> that case, the above statement is correct. Since open2web.com is
> *not* a virtual domain, however, it is wrong. Any non-system user
> addresses that are not in /var/qmail/users/assign will be handled by
> the 'alias' user.
>
> > So what I did is:
> >
> > rm /var/qmail/alias/.qmail-nobody
>
> You *can* use this file if all you intend to is drop mail addressed to
> '[EMAIL PROTECTED]'. There is no need to preserve any extension
> parts of the address (there shouldn't ever be any extension parts) and
> there is no need to actually deliver the mail, so the file you
> described above, with a single line containing '#', is perfect for
> this.
That's right. As soon as I removed it I started getting a ton of double bounced
messages.
>
> > 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.
>
> Again, I'm not sure what user the '~' refers to, but in any case, the
> above is too complicated. Since you don't need delivery, just go with
> the /var/qmail/alias/.qmail-nobody file.
OK, so the plan is as follows:
cat "#" > /var/qmail/alias/.qmail-nobody
rm /home/o2w/.qmail-nobody
rm /home/o2w/.qmail-o2w-nobody
The reason I have .qmail-nobody and .qmail-o2w-nobody in /home/o2w is based on another
thread wherein someone posted the following:
>>>>For example, system wide I have a file:
>>>>
>>>>[machine]:~# cat /etc/qmail/alias/.qmail-nobody
>>>>#
>>>>
>>>>And in my personal account I have:
>>>>
>>>>[EMAIL PROTECTED]:~> cat .qmail-nobody
>>>>#
>>>>
>>>>For each of my domains I created a symlink:
>>>>
>>>>[EMAIL PROTECTED]:~> ls -l .qmail-stassart-nobody
>>>>lrwxrwxrwx 1 user group 13 Nov 13 10:27
>>>>.qmail-stassart-nobody -> .qmail-nobody
>>>>
>>>>This creates a dropped e-mail address for each of my domains.
I may have misunderstood his post, but that's why I came up with
cat /var/qmail/alias/.qmail-nobody
#
cd o2w
cat .qmail-nobody
#
cat .qmail-o2w-nobody
#
ls -l .qmail-o2w-nobody
.qmail-o2w-nobody -> .qmail-nobody
Again, thanks for your help.
Mark
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
