On Tue, 02 Dec 2003 20:02:20 -0600
Tim Legant <[EMAIL PROTECTED]> wrote:
> MT <[EMAIL PROTECTED]> writes:
>
> > My question has to do with setting up the dot-qmail files in the home
> > directory. The problem is that I don't have a dot-qmail file in the home
> > directory because the .qmail files are set up in /var/qmail/alias and contain
> > a reference to the home directory as follows:
> >
> >>cd /var/qmail/alias
> >>cat .qmail-info
> > &xyz
>
> A quick note... this isn't so much a reference to the home directory
> as it is a forwarding instruction. This means that when qmail
> processes the delivery of a message to [EMAIL PROTECTED], it re-sends the
> message to the user xyz@<defaulthost> (which is xyz.com, in your
> case). In other words, it puts the message back in the queue and this
> delivery is finished.
# cat /var/qmail/control/defaultdomain
xyz.com
>
> Later, it finds the message in the queue, as if it were a new message,
> only this time the recipient is [EMAIL PROTECTED] So it goes to the xyz
> user's home directory to find a .qmail file from which it will read
> the delivery instructions.
>
> If you don't have a ~xyz/.qmail file, then it will use the default
> delivery instructions. Usually these are specified on the command
> line for the qmail-start program.
>
> > I set it up this way because this is the way I understood or
> > misunderstood the Life with qmail instructions.
>
> <grin> If you followed Life With Qmail, then your default delivery
> instructions are probably in /var/qmail/control/defaultdelivery.
# cat /var/qmail/control/defaultdelivery
./Maildir/
>
> > I set up the qmail control files as such:
> >
> >> cat defaultdomain
> > xyz.com
> >> cat locals
> > xyz.com
> >
> > cd /var/qmail/alias
> > cat .qmail-info
> > &xyz
> >
> > This setup works. But to use tmda, I need a .qmail file in
> > /home/xyz. So I deleted .qmail-info in the alias directory and did
> > the following:
>
> If there is no ~alias/.qmail-info file, qmail will try to deliver the
> message to the 'info' user, which it will try to find in /etc/passwd.
> Since you probably don't have an info user, it will try
> ~alias/.qmail-default. If you don't have a .qmail-default file in the
> alias directory, it will give up and bounce the message.
That's right, I don't have a /var/qmail/alias/.qmail-default file, so I end up getting
a bounce message.
>
> 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.
>
> 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
>
> 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
>
> > 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.
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?
Thanks in advance for helping me out with these problems.
Mark
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
