<snip> How does TMDA do the request/confirm process in detail? </snip>
Here is how it works based on my own experiences:
1) Your MTA or filter program (procmail/maildrop) sends a new incoming message from an unknown user. This message is given to tmda-filter for processing. 2) TMDA looks up the TMDA settings for the recipient user (usually in ~/.tmda/). 3) TMDA checks to see if the sender is in the blacklist and, if so drops the email 4) TMDA checks to see if sender is in whitelist, if so it delivers the mail 5) TMDA then checks to see if the sender is in the confirmed list and, if so delivers the mail 6) Otherwise TMDA responds to the sender with a confirmation message 7) User responds to confirmation message. TMDA checks the user's settings to see if it should add the sender's email address to the confirmed list. If so it does it 8) TMDA then sends a "message sent" note to the sender and deliver the message.
I haven't peered at the code so I may have the order of items 3, 4 and 5 wrong. I'm also sure there is a lot more going on under the hood but this is the typical behavior I've seen.
Not sure if that helps but there you go.
--Tony Tom Wolfe wrote:
This is the same problem I have been having (see below), and posted a question about it a few days ago... no one has suggested a solution and I've pretty much given up on it myself...
Regards, Tom Wolfe
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Plachy Sent: Tuesday, October 19, 2004 5:24 AM To: [EMAIL PROTECTED] Subject: pending messages not released after confirmation - confirmation notaccepted
Hi all!
I have tried to build a configuration in which I get mails from my provider with fetchmail. After fetching the mails are put with .procmailrc to tmda. This seems to work pretty good.
The mails where put into the pending queue and a confirmation-request is sent to the sender. If the sender answers the request a new request is send (see logfile).
How does TMDA do the request/confirm process in detail? What could it be, that I have not thought?
Hope anyone has an idea/solution for this problem...
so long,
Andreas
Logfile:
Date: Tue Oct 19 12:00:05 CEST 2004 From: "Tamedhon Admin" <[EMAIL PROTECTED]> Rept: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subj: test15 Actn: CONFIRM action_incoming (918)
Date: Tue Oct 19 12:00:05 CEST 2004 From: "Tamedhon Admin" <[EMAIL PROTECTED]> Rept: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subj: test15 Actn: CONFIRM pending 1098180005.3355.msg (918)
Date: Tue Oct 19 12:06:05 CEST 2004 From: "Tamedhon Admin" <[EMAIL PROTECTED]> Rept: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subj: Re: Bitte bestaetigen Sie Ihre Nachricht / Please confirm your message Actn: CONFIRM action_incoming (2742)
Date: Tue Oct 19 12:06:05 CEST 2004 From: "Tamedhon Admin" <[EMAIL PROTECTED]> Rept: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subj: Re: Bitte bestaetigen Sie Ihre Nachricht / Please confirm your message Actn: CONFIRM pending 1098180365.7341.msg (2742)
In my tmda-config-file I have entries for (and other...):
HOSTNAME = "mud.tamedhon.at" CONFIRM_ADDRESS = "[EMAIL PROTECTED]" RECIPIENT_HEADER = 'x-originally-to'
My .procmailrc looks like:
# Uncomment this for users without valid shells. # SHELL=/bin/sh
# Set the necessary environment variables. EXTENSION="$1" :0 * EXTENSION ?? . { DELIMITER="+" } #RECIPIENT="[EMAIL PROTECTED]" RECIPIENT=`formail -x To | sed 's/[<>]//g;s/^[ ]*//'` SENDER=`formail -x Return-Path | sed 's/[<>]//g;s/^[ ]*//'`
# Run the message through tmda-filter. :0 w | /usr/src/tmda/tmda-1.0.3/bin/tmda-filter
# Take the exit code from TMDA. #EXITCODE=$? EXITCODE=0
# TMDA takes care of final delivery DEFAULT=/dev/null
In .procmailrc I have set EXITCODE=0 because TMDA returns "99" and this is identified as an error. I have not tried to fix this till now, but it seems to work fine so. Only for the RECIPIENT I tried my own configuration simmular to SENDER. This also seems to run fine.
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
