Julie S. Lin wrote: > Given the similarily of the dot-courier interface to dot-qmail > you can simply follow the qmail configuration instructions > above, substituting .courier-foo for .qmail-foo."
Huh - didn't know that about Courier. > the below is my .courier file. > | preline /usr/local/bin/TMDA/tmda-1.1.9/bin/tmda-filter If the configuration really is identical to qmail, then you need to add the following line to your .courier file: |/usr/lib/courier/bin/maildrop TMDA doesn't deliver all messages itself; in qmail mode, any message that isn't held just gets passed through to the next entry in .qmail, so without that extra line, courier's default delivery destination gets used, which may well be /var/spool/mail for all I know. This is documented at: http://wiki.tmda.net/ServerConfiguration > can anyone give me more insight into what happens to the email once a > confirmation email > is received? What picks up the email from the pending folder and > "re"delivers it? where is this > configured? tmda-filter received the confirmation request. tmda-filter then modifies the original held email to include some extra headers used later, and re-injects the original email into your standard email reception path. The re-injection is configured via: http://wiki.tmda.net/ConfigurationVariables#MAIL_TRANSPORT When the re-injected message is then received by tmda-filter, the extra headers are checked, and hence tmda-filter passes the message on to the default delivery location. So, either/both of these could be the problem: 1) MAIL_TRANSPORT isn't correctly set, and TMDA is sending the re-injected message to something that delivers directly to /var/spool/mail. 2) The missing line in .courier _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
