On Thu, 04 Dec 2003 19:46:27 -0600
Tim Legant <[EMAIL PROTECTED]> wrote:
> MT <[EMAIL PROTECTED]> writes:
>
> > On Tue, 02 Dec 2003 20:02:20 -0600 Tim Legant <[EMAIL PROTECTED]> wrote:
> >
> >> You have a couple of options here.
> >>
> >> 1. You can restore the ~alias/.qmail-info file so that all messages to
> >> [EMAIL PROTECTED] are forwarded to '[EMAIL PROTECTED]'. If you do this, you
> >> will need to add a header (using formail [from the procmail
> >> package] or reformail [from the maildrop package]) that specifies
> >> the original recipient ('[EMAIL PROTECTED]'). Then you will need to
> >> tell TMDA about that header using the RECIPIENT_HEADER variable.
> >>
> >> If you don't do this, when someone sends a message to 'info',
> >> confirmation messages will come from 'xyz', which can be confusing.
> >
> > OK, I set up according to the first option. When I sent a message to
> > '[EMAIL PROTECTED]', the confirmation message came from '[EMAIL PROTECTED]',
> > not '[EMAIL PROTECTED] as you suggest. If you want to confirm, I can give
> > you the real address.
>
> Sure, you can send it to me personally. I used to run this way
> (various addresses @catseye.net in ~alias) and discovered that when
> qmail forwards, the original recipient is lost. So I'm unsure how you
> could be seeing what you're seeing.
You're right, I was mixed up about this.
>
> >> 2. You can remove xyz.com from locals and put it in virtualdomains:
> >
> > I was thinking of doing this, but wasn't sure if I could leave
> > locals empty or delete locals
>
> If a domain is specified in both locals and virtualdomains, locals
> always wins. qmail-send(8) (in the _virtualdomains_ section) says:
>
> qmail-send handles virtualdomains after locals: if a domain is
> listed in locals, virtualdomains does not apply.
>
> >> xyz.com:xyz
> >>
> >> Now, all mail coming into the machine for any address at xyz.com
> >> will be delivered to the xyz user. By default, TMDA knows about
> >> virtual domains and will handle this correctly. This is probably
> >> your easiest course.
> >>
> >> Be aware that messages to root, mailer-daemon and postmaster, which
> >> used to be delivered according to the .qmail-* files in alias, will
> >> now be delivered to the xyz user. The delivery instructions in
> >> ~xyz/.qmail-root, ~xyz/.qmail-mailer-daemon and
> >> ~xyz/.qmail-postmaster will take precedence over any instructions
> >> in ~xyz/.qmail-default, if you want to handle those addresses
> >> differently from any other addresses @xyz.com
> >
> > /var/qmail/alias/.qmail-root
> > /var/qmail/alias/.qmail-postmaster
> > /var/qmail/alias/.qmail-mailer-daemon
> > all contain xyz
>
> Yes, but my point above was that if you make xyz.com a virtual domain,
> these files in ~alias will no longer be used.
>
> >> MT <[EMAIL PROTECTED]> writes:
> >>
> >> > cd /home/xyz
> >> > became the xyz user
> >> > vi .qmail
> >> > |preline /usr/bin/tmda-filter
> >> > ./Maildir
> >> > ln -s ~/.qmail .qmail-default
> >>
> >> Once you do one of the above (option 2 is probably your best bet),
> >> these instructions, and qmail in general, will start working again.
> >>
> > My system has several virtualdomains. One of them is called
> > 123.com. I used to have an email address with this domain called
> > [EMAIL PROTECTED] Although it is now defunct, I was still receiving email
> > from spammers which MAILER-DAEMON tried to bounce back to the
> > spammer. As is the case with email from spammers, the bounce
> > bounced. Anway, since I set up TMDA, I'm no longer getting these
> > bounce bounced messages from MAILER-DAEMON.
>
> Unless mail *to* postmaster is whitelisted (or mail *from*
> mailer-daemon), TMDA will stop these message and send back a
> confirmation request, unless it determines that the sender's address
> cannot be replied to (like '<>' and '[EMAIL PROTECTED]').
>
> > As .qmail-mailer-daemon defers to xyz, does this mean all my
> > MAILER-DAEMON mail is sitting in the pending queue. If so, this is
> > probably no ideal. Is there a way to defer MAILER-DAEMON mail
> > through xyz without it going through TMDA?
>
> I mentioned this in my reply to your message of today; here's a
> re-cap. Set up ~alias/.qmail-mailer-daemon and
> ~alias/.qmail-postmaster to point to a different address, say
> xyz-admin, or xyz-mailadmin. Then create a ~xyz/.qmail-admin or
> ~xyz/.qmail-mailadmin file to deliver directly to your inbox
> (~/Maildir/ was your default, I think) rather than running
> tmda-filter.
OK I've done this. root, postmaster and mailer-daemon, which all used to point to o2w,
now point to o2w-admin. Then, in the o2w system user directory, I created a new
.qmail-admin file containing ./Maildir/
Now, if I were to remove open2web.com from ~/control/local and add it to
~/control/virtualdomains, then the alias files (root, postmaster and mailer-daemon) no
longer function. Anything sent to root, postmaster or processed by mailer-daemon end
up going through the .qmail file in o2w, which means they will go through TMDA again.
Mark
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
