"Andrea Riela" <[EMAIL PROTECTED]> writes: > I would check the pending messages with a script for each user. > I've vpopmail with virtualdomains.
[script to run tmda-pending...] > observe# ./check-pending-queue.sh > Traceback (most recent call last): > File "/usr/local/tmda-1.0/bin/tmda-pending", line 271, in ? > from TMDA import Pending > File "./TMDA/Pending.py", line 34, in ? > File "./TMDA/Defaults.py", line 1534, in ? > TMDA.Errors.ConfigError: Can't find key file: /root/.tmda/crypt_key > > % ./check-pending-queue.sh > Traceback (most recent call last): > File "/usr/local/tmda-1.0/bin/tmda-pending", line 271, in ? > from TMDA import Pending > File "./TMDA/Pending.py", line 34, in ? > File "./TMDA/Defaults.py", line 1534, in ? > TMDA.Errors.ConfigError: Can't find key file: /home/vpopmail/.tmda/crypt_key > > Where is my mistake? You haven't made a mistake, really. tmda-pending expects to run as the user receiving the mail, with the appropriate $HOME setting and so forth. It doesn't really work well for virtual domains. > The crypt_key is in /home/vpopmail/domains/nesys.it/test/.tmda, and > I've the correct link in my config file: CRYPT_KEY_FILE = > "/home/vpopmail/domains/nesys.it/test/.tmda/crypt_key" You could create a /home/vpopmail/.tmda/crypt_key (using tmda-keygen as usual) just to make tmda-pending happy. It should run at that point. We haven't done a lot of work on tmda-pending because the thought has been, for a while, that it's going away. What will probably happen is that future versions of TMDA will create the pending queue in a format that standard Unix mail readers can read (Maildir being the most likely) so that tmda-pending simply isn't necessary. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
