Niklas Saers Mailinglistaccount <[EMAIL PROTECTED]> writes: > I've got problems delivering local messages through ofmipd, and it all > stops with tmda-inject. I'm running ofmipd as user postfix with command: > > /usr/local/tmda/bin/tmda-ofmipd -f -p 0.0.0.0:2525 -R pop3://localhost -S > /etc/ofmipd-usermapping.sh -C 20 -t /etc/ofmipd-throttle.sh --debug > > where the scripts contain the following: > > ofmipd-usermapping.sh: > ----- > #!/bin/sh > user=$1 > domain=$2 > echo /virtual/[EMAIL PROTECTED]
Interestingly, the output you provide below shows that this script returns "/var/virtual/[EMAIL PROTECTED]".... > vuser homedir: "/var/virtual/[EMAIL PROTECTED]" [...] > File "./TMDA/FilterParser.py", line 935, in firstmatch > TMDA.FilterParser.MatchError: [line 1]: need 'c' or 'n' flag to open new > db)) The first line of your outgoing filter has a 'from-dbm' rule. The DBM file that you reference doesn't exist, so tmda-inject quits with an error. You should either create this file with external tools or specify a text file using the 'from-file' rule instead. When you use 'from-file', you can also use the '-autodbm' parameter to cause TMDA to automatically create the DBM file from the text file. If the DBM file exists, TMDA will use it. If it doesn't exist or if the text file has a more recent timestamp than the DBM, TMDA will attempt to create the DBM from the text file and, if it is successfully created, will use it for the lookup. Finally, if TMDA has difficulties creating the DBM, it will fall back to matching against the text file. Generally, you will want to use the 'from-file' rule with the '-autodbm' parameter for flexibility unless you have other tools that you use to create your DBM file. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
