"Daniel Baron" <[EMAIL PROTECTED]> writes: >> But TMDA doesn't know anything about virtual users. You would have to >> tell tmda-pending which config file to use, first, and perhaps in the >> user's config file the CRYPT_KEY variable is defined, pointing to the >> correct location? > > Well, I tried to do that, but it didn't work. i put CRYPT-KEY="key that was > generated" into .tmda/config (found that in some other email in the archive). > Or at least, it didn't give me the desired results.
My fault. There was, long long ago, an option to put CRYPT_KEY in the config file. Now, you just need to make sure CRYPT_KEY_FILE points to the correct file. That's what I meant above but mis-typed CRYPT_KEY instead of CRYPT_KEY_FILE. > I'm using Courier with MySQL, so all users and their homedirs come out of a > database. When an email message arrives, the database is queried... happens > every time, of course, so TMDA should get it with the second mail as well. The fundamental problem is that TMDA doesn't really support virtual users. Different MTAs implement virtual domains/users differently. There are a couple of hacks to support qmail's virtual domain mechanism, but even that isn't (at this point) particularly well integrated. I think that $HOME is set correctly because tmda-filter is not failing, which means it is finding a 'crypt_key' file. > LOGFILES > > After sending out the first mail: > > /var/log/maillog: > > Dec 10 21:59:05 avocado courieresmtpd: started,ip=[111.222.333.444] > Dec 10 21:59:06 avocado courierd: newmsg,id=0002E25B.3FD7891A.0000AFBB: dns; > mailserver1 (mailserver1 [111.222.333.444]) > Dec 10 21:59:06 avocado courierd: > started,id=0002E25B.3FD7891A.0000AFBB,from=<[EMAIL PROTECTED]>,module=local,[EMAIL > PROTECTED]/usr/local/courier/var/mail/zac!!,addr=<[EMAIL PROTECTED]> > Dec 10 21:59:06 avocado courierd: Waiting. shutdown time=none, wakeup > time=Wed Dec 10 22:02:12 2003, queuedelivering=2, inprogress=1 > Dec 10 21:59:06 avocado spamd[58252]: connection from localhost [127.0.0.1] > at port 58313 > Dec 10 21:59:06 avocado spamd[44996]: processing message > <[EMAIL PROTECTED]> for courier:89. > Dec 10 21:59:09 avocado spamd[44996]: clean message (0.1/5.0) for courier:89 > in 2.9 seconds, 1478 bytes. > Dec 10 21:59:10 avocado courierlocal: > id=0002E25B.3FD7891A.0000AFBB,from=<[EMAIL PROTECTED]>,addr=<[EMAIL > PROTECTED]>,size=1419,success: Message delivered. > Dec 10 21:59:10 avocado courierd: completed,id=0002E25B.3FD7891A.0000AFBB > Dec 10 21:59:10 avocado courierd: Waiting. shutdown time=Wed Dec 10 > 22:38:22 2003, wakeup time=Wed Dec 10 22:02:12 2003, queuedelivering=1, inprogress=0 I don't see any indication here that TMDA sent the confirmation request, although you appear to have received it, so perhaps information about sent mail (using Courier's sendmail program) is logged somewhere else? > logs/incoming: > > Date: Wed Dec 10 21:59:10 CET 2003 > From: zac <[EMAIL PROTECTED]> > Rept: zac <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: test > Actn: CONFIRM action_incoming > (1556) > > Date: Wed Dec 10 21:59:10 CET 2003 > From: zac <[EMAIL PROTECTED]> > Rept: zac <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: test > Actn: CONFIRM pending 1071089950.44997.msg > (1556) This looks correct. At this point TMDA will have sent the confirmation request message. > After replying to the "register" mail: Assuming you mean the request to reply in order to release the original message.... > /var/log/maillog: > > Dec 10 22:06:54 avocado courieresmtpd: started,ip=[111.222.333.444] > Dec 10 22:06:57 avocado courierd: newmsg,id=0001CC12.3FD78AF1.0000B067: dns; > mailserver1 (mailserver1 [111.222.333.444]) > Dec 10 22:06:57 avocado courierd: > started,id=0001CC12.3FD78AF1.0000B067,from=<[EMAIL PROTECTED]>,module=local,[EMAIL > PROTECTED]/usr/local/courier/var/mail/zac!!,addr=<[EMAIL PROTECTED]> > Dec 10 22:06:57 avocado courierd: Waiting. shutdown time=none, wakeup > time=Wed Dec 10 22:07:23 2003, queuedelivering=2, inprogress=1 > Dec 10 22:06:57 avocado spamd[58252]: connection from localhost [127.0.0.1] > at port 58340 > Dec 10 22:06:58 avocado spamd[45169]: processing message > <[EMAIL PROTECTED]> for courier:89. > Dec 10 22:07:02 avocado spamd[45169]: clean message (0.1/5.0) for courier:89 > in 4.3 seconds, 1626 bytes. > Dec 10 22:07:03 avocado courierlocal: > id=0001CC12.3FD78AF1.0000B067,from=<[EMAIL PROTECTED]>,addr=<[EMAIL > PROTECTED]>,size=1535,success: > Message delivered. > Dec 10 22:07:03 avocado courierd: completed,id=0001CC12.3FD78AF1.0000B067 > Dec 10 22:07:03 avocado courierd: Waiting. shutdown time=Wed Dec 10 > 22:38:22 2003, wakeup time=Wed Dec 10 22:07:23 2003, queuedelivering=1, inprogress=0 Ok, so mail to zac-confirm-XXX can be delivered successfully. > logs/incoming: > > Date: Wed Dec 10 22:07:03 CET 2003 > From: zac <[EMAIL PROTECTED]> > Rept: zac <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: None > Actn: CONFIRM accept 1071089950.44997.msg > (1691) > > Date: Wed Dec 10 22:07:03 CET 2003 > From: zac <[EMAIL PROTECTED]> > Rept: zac <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: None > Actn: CONFIRM_APPEND > /usr/local/courier/var/mail/zac/.tmda/lists/confirmed(1691) This all looks good. Right after this log message is when TMDA re-injects the message (by re-sending it through Courier, again using Courier's sendmail binary). > That's it. Apparently it doesn't even try to send out that first email. What > am I missing? Do i need some parameter --actually-send-first-mail? ;) We can't really tell that from TMDA's log. It probably did send it since tmda-filter didn't end in error. The problem is that the Courier log doesn't seem to log anything sent using 'sendmail', in either the first case (the confirmation request to the original sender) or the re-injection of the original message. Until we can track down what's happening to the message we're up a creek, so to speak. We need to figure out where that message is going, so if there is a way to get Courier to log that in maillog, or if it logs it somewhere else, that would be helpful. Do you have an /etc/tmdarc? Also, what are the complete contents of zac/.tmda/config? Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
