"bwest" <[EMAIL PROTECTED]> writes: > -I don't use .qmail files I use the deafultdelivery so the TMDA > start is there.
I assume your defaultdelivery file looks something like this? | preline tmda-filter ./Maildir/ > -I use qpopper to pop my mail (it appears to be working fine). TMDA and POP have nothing to do with one another, so this is a variable you shouldn't have to consider. > -I use SMTP to deliver the messages. Do you mean your machine receives messages from the world at large with an SMTP server (qmail, you've indicated)? Or do you use something like fetchmail to POP your mail from somewhere else and feed it to your local MTA? > -Tmda is set up with the deafults and nothing more added to the > config file than dictated by the sample config file. The sample.config file says nothing is required in the case of qmail. Have you uncommented any of the DELIVERY options, or the CONFIRM_APPEND line or any of the LOGFILE_xxx options? > When I get a message it is sent to the ~/.tmda/pending and a incoming log > file is created in my log directory. This log file is correct. I am not > receving any errors for the delivery of the confirmation message. So TMDA successfully creates the confirmation request and sends it through your SMTP server. > The problem is that the confirmation message is placed in the qmail > queue with no sender data and no recipent data, but the confirmation > message itself has the correct data on it in the queue. What could > be my problem? The envelope sender for confirmation requests is the standard bounce envelope sender -- the empty sender <>. If you're looking at the /var/qmail/queue/info/<n>/<inode> file to see the envelope sender, you'll just see the 'F' character followed by a null character (^@). This is normal for empty envelope senders. If there is no envelope recipient for the confirmation request, which should be the envelope sender address of the original incoming message, TMDA won't have created the confirmation request. That is, TMDA doesn't attempt to reply to empty envelope senders and any other envelope sender is, by definition, not empty. Can you give us some more information on why you think there is no recipient for the confirmation request? Also, could you post the relevant entries from your LOGFILE_INCOMING for a test message? > Like I said there are not errors being passed to me just the message is not > being released from the queue because there must have been a problem > creating it in the queue and it didn't know it. Which message isn't being released from the queue? The original incoming message or the confirmation request generated by TMDA? Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
