Hello folks, I have a strange effect in qmailadmin: Every 3rd time I edit an autoresponder, the Copy to: field in the form changes from the intended destination address to something like that: <path/to/qmail/bin/>autorespond 10000 5 </path/to/vopopmail/domains/<domain>/<resondername>/message /var/vpopmail/domains/<domain>/<respondername> (where <domain> is the current domain that an autoresponder is edited for and <resondername> is the alias address for the mail robot)
If I correct this to the valid e-mail address, the next time I edit the mail robot, all semms ok, but the next time in turn it is crippled again. Nothing happens to the configuration of the domain or the responder, because the form can't be sent with above mentionned content of the Copy to: field (error message: invalid owner email address <path/to/qmail/bin/>autorespond 10000 5 </path/to/vopopmail/domains/<domain>/<resondername>/message /var/vpopmail/domains/<domain>/<respondername>). I guessed what happens, but I'm quite sure about that it must be like that: There are two records written each time containing the two distinctive alias lines (one for the call of the autoresponder, one for the forward). If my database system stores the record with the valais line with the command before the forward address, all is ok, but if I the robot will get edited (records deleted and added again), mysql randomly stores the record with the command valias line after the forward address. (and it may, nothing wrong with that afaik). It seems that Qmailadmin searches the last valias line for the mail robot that vpopmail resp. the underlying database backend returns, so it is depending on the order of the two records in the database. And I think it's a mistake to (indirectly) depend on the order of certain records returned by a database system like mysql. Software I use: vpopmail-5.4.13 qmailadmin-1.2.9 mysql-4.1.16 qmail-1.03-r16 Has someone had a similar problem yet? Regards, Michael Rhyner
