Thank you for your reply and replace client-data in public posting :-) I have implemented this way in our admin-backends because i can use the same way creating forward/alias and i have not to deal with user-ids/domains there
Means: If i create a new physical account one alias with userid is created and all other aliases are forwarders which makes it easier to query pyhsical acoounts and aliases for different screens I think one query should trigger this while receive the message if one of the To/Cc-Fields is on the left-side in the alias-table and reply-cache is empty/outdated -> send reply _______________________ we are speaking about 13664 LOC / 457.50 KB php-code which was a coding-marathon for few weeks i hope there are no changes in dbmail 3.0 in the logic for the following tables, all other backend-data are not interesting for my code which runs rock stable and has every possible option for dbmail/postfix/statistics * dbmail_acl * dbmail_aliases * dbmail_auto_replies * dbmail_mailboxes * dbmail_messages * dbmail_replycache * dbmail_users regards harry Am 08.01.2011 19:30, schrieb Paul J Stevens: > On 01/07/2011 10:05 PM, Paul J Stevens wrote: >> On 01/07/2011 09:48 PM, Reindl Harald wrote: >> >>> dbmail is sending the reply only if the message goes to the physical >>> account, but not if a message will be sent to one of the both aliases >> >> That sucks. >> >> What do the relevant dbmail_aliases and dbmail_users rows look like? Or >> level=5 logs of a failed auto-reply delivery. > > Harald, > > Looks like a bug alright. But only because you are using forwards, not > aliases. > > consider: > > mysql> select * from dbmail_aliases; > +------------+---------------------+---------------------+-------------+ > | alias_idnr | alias | deliver_to | client_idnr | > +------------+---------------------+---------------------+-------------+ > | 1 | testus...@localhost | 4 | 0 | > | 2 | testus...@localhost | testus...@localhost | 0 | > | 3 | testus...@localhost | testus...@localhost | 0 | > +------------+---------------------+---------------------+-------------+ > > here, the first two are aliases, while the third is a forward. As a work > around in your situation, if you want auto-reply to work for messages > sent to testuser2 and testuser3 you should assign them as aliases: > > dbmail-users -c testus...@localhost \ > -T testus...@localhost,testus...@localhost > dbmail-users -c testus...@localhost \ > -s testus...@localhost,testus...@localhost > > so you get: > > +------------+---------------------+---------------------+-------------+ > | alias_idnr | alias | deliver_to | client_idnr | > +------------+---------------------+---------------------+-------------+ > | 1 | testus...@localhost | 4 | 0 | > | 2 | testus...@localhost | 4 | 0 | > | 3 | testus...@localhost | 4 | 0 | > +------------+---------------------+---------------------+-------------+ -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
