On Thu, August 7, 2008 11:46 pm, Tek Support wrote: > Thank you, maybe you've seen my last post which said that I got a > bounce from the server, and it said something about a qmail program > called "preline" not understanding the "hello".
Judging by your error message, it looks like preline is trying to run a command name hello. I *think* the only way this could happen is if you mistyped something in .qmail, and said something like: | /var/qmail/bin/preline hello ... Either that, or double-check that your premail executable, and the executable it's suposed to be executing haven't become corrupted/mis-edited. Perhaps there's a line like this near the top of one/both of those, if they're scripts of some kind: #!hello > > I'm a little lost on that part, but if you aren't using qmail, then > I'm sure that won't help you, help me. I'll do a google search on > preline and see what I can come up with. > > Thanks again for your advice. I have learned a few things, and maybe > I can use that to get this resolved. And maybe someone else who uses > qmail and tmda can ehlp also. > > Thanks > John > > > 2008/8/7 David Grimberg <[EMAIL PROTECTED]>: >> The mail server I uses neither qMail nor vpopmail so I'm not too certain >> how >> to check if it is being set. I do know that the .tmda/config file is >> actually executed by tmda as a python script. Therefore, anything that >> is >> possible in python can be done in your .tmda/config file, including >> writing >> environment variable out to a log file somewhere, or possibly even >> setting >> environment variables from within the config file (don't quote me on >> that >> though, I'm not a python expert either). However, since you are not >> getting >> any tmda log files you may not even be getting that far. It may be >> possible >> to put something in your .qmail file to log your environment, but I >> don't >> know what or how. >> >> Tek Support wrote: >>> >>> David, if I might ask you another question, how do I "ensure that >>> $HOME" is getting set? Since it's an environment variable, and >>> qmail/vpopmail is running in the background, I'm not sure how to check >>> if $HOME is actually getting set in an environment I can't log into. >>> >>> Thanks for the help... >>> John >>> >>> >>> >>> >>> >>> 2008/8/7 David Grimberg <[EMAIL PROTECTED]>: >>> >>>> >>>> Hi John, >>>> >>>> I just took a quick look at your setup and noticed a discrepancy in >>>> some >>>> of >>>> your directory locations. In the first part of your email you stated >>>> your >>>> directory structure was: >>>> >>>> ... >>>> So now my directory/file setup is now like this: >>>> /home/vpopmail/domain.com/user/.qmail >>>> /home/vpopmail/domain.com/user/.qmail-default >>>> /home/vpopmail/domain.com/user/Maildir/ >>>> /home/vpopmail/domain.com/user/.tmda/ >>>> /home/vpopmail/domain.com/user/.tmda/config >>>> /home/vpopmail/domain.com/user/.tmda/crypt_key >>>> /home/vpopmail/domain.com/user/.tmda/filters/ >>>> /home/vpopmail/domain.com/user/.tmda/lists/ >>>> /home/vpopmail/domain.com/user/.tmda/logs/ >>>> >>>> >>>> You then showed us your .qmail file: >>>> >>>> ... >>>> ---Begin--- >>>> #| /var/qmail/bin/preline /home/vpopmail/tmda-1.1.12/bin/tmda-filter >>>> -S /home/vpopmail/bin/vpopmail-vdir.sh >>>> | /var/qmail/bin/preline /home/vpopmail/tmda-1.1.12/bin/tmda-filter -c >>>> /home/vpopmail/domains/domain.com/user/.tmda/config >>>> ./Maildir/ >>>> ---End--- >>>> >>>> >>>> What jumped out at me was the extra directory "domains" between >>>> "vpopmail" >>>> and "domain.com" >>>> >>>> Further since you are in a virtual domain setup, you do need to ensure >>>> that >>>> the $HOME environment variable is getting setup properly so that the >>>> tilde >>>> "~" expansion will work, otherwise you should use full paths within >>>> your >>>> config file as you did with the CRYPT_KEY_FILE variable. >>>> >>>> And my .tmda/config >>>> ---Begin--- >>>> # -*- python -*- >>>> MAIL_TRANSFER_AGENT = "qmail" >>>> RECIPIENT_DELIMITER = "-" >>>> DELIVERY = "~/Maildir/" >>>> BARE_APPEND = "~/.tmda/lists/whitelist" >>>> CONFIRM_APPEND = "~/.tmda/lists/whitelist" >>>> LOGFILE_DEBUG = "~/.tmda/logs/debug" >>>> LOGFILE_INCOMING = "~/.tmda/logs/incomging" >>>> #CRYPT_KEY_FILE = "~/.tmda/crypt_key" >>>> CRYPT_KEY_FILE = >>>> "/home/vpopmail/domains/domain.com/user/.tmda/crypt_key" >>>> ---End--- >>>> >>>> >>>> Have you tried running tmda-filter yourself? A simple test to see if >>>> your >>>> setup is working is to just issue a command similar to the following: >>>> >>>> $ tmda-filter -M [EMAIL PROTECTED] [EMAIL PROTECTED] >>>> >>>> where [EMAIL PROTECTED] is one of the following: >>>> >>>> the address of your TMDA user e.g. [EMAIL PROTECTED] >>>> a valid tagged address generated using the tmda-address script e.g. >>>> [EMAIL PROTECTED] >>>> an invalid tagged address generated using the tmda-address script e.g. >>>> [EMAIL PROTECTED] >>>> >>>> and where [EMAIL PROTECTED] is an address is your whitelist >>>> when >>>> using the first recipient address form and a non white listed address >>>> when >>>> using the second recipient address form. >>>> >>>> If possible you should run these tests from the same user that >>>> processes >>>> you >>>> incoming mail so you can be sure that there aren't any file permission >>>> issues preventing qmail from executing your tmda filter setup. Which >>>> brings >>>> me to my next question, You did set the permissions on your tmda >>>> related >>>> files as per the documentation right? >>>> >>>> Good luck with the rest of your debugging, >>>> >>>> - Dave >>>> >>>> >> > _____________________________________________ > tmda-users mailing list (tmda-users@tmda.net) > http://tmda.net/lists/listinfo/tmda-users > > _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
