Hummmm well ok... But with the mysql patch, Qmail now use a table called
valias in MySQL witch for my case contains:
mysql> select * from valias where valias_line="&te...@mydomain.com";
+----------+--------------+-----------------------------+
| alias | domain | valias_line |
+----------+--------------+-----------------------------+
| test | mydomain.com | &myem...@anotherdomain.com |
+----------+--------------+-----------------------------+
1 row in set (0.00 sec)
I know from now on that I should not use aliases, do you know if this kind
of patch might work?
I'm not sure what you mean by "patch" but my understanding of qmail/vpopmail
is that aliases/forwards get processed _before_ the .qmail-default, since
they specify something other than a final destination. My observation has
been that until the actual delivery is ready to occur, the .qmail-default
does not get processed, meaning maildrop will not get run. This has not,
however, caused any problems with my filters.
I think that this method is not getting processed as an alias, because I
know that the email sent to my server (even if is an alias) get filtred.
The only problem is that the email is lost... :\
And both domains are setup with the filters? If you only setup mydomain.com
to call maildrop from your .qmail-default and you have not setup
anotherdomain.com to do the same thing, then of course it's not going to get
processed by maildrop. The chain of execution in that case would not
include maildrop anywhere.
I think at this point the best thing you could do is for you to post more
information about your setup. To this point I've just assumed that you are
calling maildrop from .qmail-default -- is this a correct assumption? You
should also post your mailfilter file for review, too, because perhaps
something is missing from there.
You can also try running maildrop with the -V flag and watching messages
sent to standard error to see if something is abending.
cheers,
-ben