Is there any other way to handle this without using users/assign?  (with
standard .qmail files)

Perhaps another forward program (a lower level one, if one exists).

I wonder if that is even possible.  Thank for the help so far. 

Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]

-----Original Message-----
From: Harald Hanche-Olsen [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 26, 1999 2:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Qmail '|forward user-$DEFAULT' problem with ezmlm

- "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>:

| - control/me
| mail.host.com
|
| - control/virtualdomains:
| domain.com:alias-domain
|
| - alias/.qmail-domain-user
| &localuser
|
| - alias/.qmail-domain-user-default
| |forward localuser-$DEFAULT
|
| Ok, I setup ezmlm, and I receive an error on a send to
| [EMAIL PROTECTED]:
|
| <[EMAIL PROTECTED]>:
| ezmlm-manage: fatal: I do not accept messages at this address (#5.1.1)
|
| If I put "mail.host.com" into my ~localuser/list/inhost and it
| works.  But I do not want to have each list, and each user to have
| to do this!
|
| Why is it being rewritten to [EMAIL PROTECTED] ? 

It's just how your virtualdomains setup works: By forwarding to the
new domain.

| I want to keep it at [EMAIL PROTECTED]
|
| Any solutions?

You could employ the users/assign mechanism instead of files in
~alias.  If you cause the following to be in users/assign:

=domain-user:user:123:456:/home/user:::
+domain-user-:user:123:456:/home/user:-::

(replace 123:456 by the user's uid:gid and /home/user by the user's
real home dir) and remember to run qmail-newu, then the mail will be
delivered directly.  You will want to write a script that does this
automatically, of course.

- Harald

Reply via email to