Hi Ben,

On Thu, 19 Jun 2003, Benjamin Tomhave wrote:

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 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... :\

Here an example in my logs: Jun 19 13:54:34 wolverine qmail: 1056045274.481262 info msg 52967: bytes 1522 from <myem...@mydomain.com> qp 24294 uid 89 Jun 19 13:54:34 wolverine qmail: 1056045274.499078 starting delivery 349008: msg 52967 to local mydo...@mydomain.com Jun 19 13:54:34 wolverine qmail: 1056045274.610344 delivery 349008: success: vdelivermail:_valiases_processed/did_0+0+1/

If you can see, valiases_processed ?!?!?! But the mail never gets forwarded to my email account. Everything has been tested properly, the only problem now is the !@#$%#%#% forwarded contain in my MySQL table :\ I really need to find a solution for this. MySQL is required for what I need here.

I had a very bad idea (looks more like a patch to me) creating a small program that connects on my MySQL server and check if it's a forward. If it's a forward I should pipe everything vdelivermail or if it's a mail account, give it to maildrop. What do you think of that? Do you think it worth a try?

Thanks, -Pat