Hi tim, thanks for your reply,
>> I'm running a working qmail server on a mandrake box which works >> flawlessly without qmail config. Not sure I understand this. Perhaps you mean "without ~/.qmail file"? DC: More specifically, yes as you've said above. >> What seems to be happening is that I am using ./Maildir/ for local >> delivery and i'm not 100% sure what .qmail is supposed to read. >> >> I have tmda installed in /usr/local/tmda and my .qmail says this. >> >> |preline /usr/local/tmda/bin/tmda-filter >> ./Mailbox The second line isn't necessary. You should be able to type "man dot-qmail" to see what kind of lines can be in a dot-qmail file and what actions they cause qmail to take regarding message delivery. The second line above says to deliver the message to a traditional Unix mbox file (all messages are stored in one file) in your home directory named Mailbox. Since you say you're delivering to ~/Maildir/, this line won't help. You can safely delete it. DC: I presumed this.. :) It's not causing you problems right now because qmail is ignoring it. The reason is because you have set DELIVERY in the TMDA config file. Setting DELIVERY is perfectly ok; it simply causes tmda-filter to return an exit code to qmail telling qmail to ignore any further delivery lines in your dot-qmail file(s). To achieve the same effect, you could comment the DELIVERY line in your config file and replace "./Mailbox" with "./Maildir/" (no quotes) in your .qmail and .qmail-default files (I realize they are currently the same file because of the symlink. If they were not, or if you had a more complex configuration, you would need to make the change in every file that runs tmda-filter.) Neither of these options is more "right" than the other; either will work. DC: ya, i followed that one too.. >> I've had to bin my /var/qmail/alias/.qmail-default as im using >> fastforward for /etc/aliases format for now. >I'm afraid I don't understand this. What do you mean by "bin"? I've >never used the fastforward package... in which dot-qmail file are you >calling fastforward? ~alias/.qmail-default? Also, this calls into > question just what '~' means, above. > TMDA requires the original envelope sender in the SENDER environment > variable and the original envelope recipient in the RECIPIENT > environment variable. I'm unsure how fastforward handles this; it may > be a problem. DC: the fastforward package supports sendmail like /etc/alias file and the .forward files that were present on sendmail/unix systems. it's activiated by the ~alias/.qmail-default file being setup (which i've disabled currently to keep things simple and try to get tmda working!!) >> When I send an email to myself via mutt(working qmail system) with >> email >> setup to work with tmda these things happen >> >> 1. i get no email to user. >> 2. messages are deferred to the ~/.tmda/defered Hmmm. I've never heard of this file (~/.tmda/defered). >> 3. my debug file says this >> >> Uncaught Python 2.3.3 Exception (Tue Jan 6 12:36:50 2004): >> ----------------------------------------------------------- >> Traceback (most recent call last): >> File "/usr/local/tmda/bin/tmda-filter", line 53, in ? >> execfile(os.path.join(execdir, 'tmda-rfilter')) >> File "/usr/local/tmda/bin/tmda-rfilter", line 882, in ? >> main() >> File "/usr/local/tmda/bin/tmda-rfilter", line 825, in main >> orig_msgin_size) >> File "/usr/local/tmda/TMDA/FilterParser.py", line 938, in >> firstmatch >> raise MatchError(lineno, str(e)) >> MatchError: [line 17]: need 'c' or 'n' flag to open new db This is often an indication that tmda-filter is being run as the wrong user. This may be a side-effect of fastforward. Again, I'm not familiar with how fastforward works but I do see a SECURITY WARNING in the man page relating to users.... DC: Like is said above, ive disabled the functionality of fastforward.. the errors above happened when f/f is not active. >> 4. I don't get a confirmation email. The above error means that TMDA has deferred the message (it's still in the qmail queue). If that happens you will receive neither a confirmation message nor the original message until the problem is fixed and tmda-filter can run successfully. DC: I'm still none the wiser as to why my tmda config doesnt work... Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
