Hi Allyn. I've never had a reason to use CONFIRM_CC yet. But I could give it a try on my machine, and see what it does.
It's a bit late now to do anything - I'm getting tired. Keith On Sat, 20 May 2006, Allyn Baskerville wrote: > To: tmda-users@tmda.net > From: Allyn Baskerville <[EMAIL PROTECTED]> > Subject: Re: How does CONFIRM_CC work? > > The default action for ACTION_INCOMING is confirm, and it > is still set this way. I was testing from my yahoo > account. I never receive a challenge on my local account > where TMDA is running, but I do receive a challenge on the > yahoo account. When I set ACTION_INCOMING = "ok", the > messages are delivered from the yahoo account with no > challenge and with no entry in the whitelist. Removing it > causes the challenges to be initiated. > > Should there be something obvious in the logs? I don't see > anything obvious. > > > ----- Original Message ----- > From: "Keith Roberts" <[EMAIL PROTECTED]> > To: <tmda-users@tmda.net> > Sent: Saturday, May 20, 2006 8:56 AM > Subject: Re: How does CONFIRM_CC work? > > > > From my understanding according to the manual for 1.0.3 - > > Any email you receive that comes from someone not on your > > whitelist or blacklist should be sent a copy to the address > > set in CONFIRM_CC. > > > > CONFIRM_CC > > > > An optional e-mail address which will be sent a copy of any > > message that triggers a confirmation request. > > > > Example: > > > > CONFIRM_CC = "[EMAIL PROTECTED]" > > > > No default. > > > > What do you have the default action set to for mail not on > > your white or blacklist? > > > > Does TMDA send any confirmation messages out at all? > > > > Try setting ACTION_INCOMING = "ok" in the TMDA config file. > > > > Are you testing TMDA locally, or using a seperate webmail > > account for testing? > > > > ACTION_INCOMING > > > > Specifies how incoming messages should be disposed of by > > default if they didn't match FILTER_INCOMING and were not > > sent to a tagged address. Possible values include: > > > > "bounce" bounce the message > > > > "drop" silently drop the message > > > > "ok" deliver the message > > > > "confirm" request confirmation for the message > > > > "hold" silently hold message in pending queue > > > > Default is confirm > > > > Keith Roberts > > > > > > In theory, theory and practice are the same; > > in practice they are not. > > > > On Sat, 20 May 2006, Allyn Baskerville wrote: > > > >> To: tmda-users@tmda.net > >> From: Allyn Baskerville <[EMAIL PROTECTED]> > >> Subject: How does CONFIRM_CC work? > >> > >> I installed "CONFIRM_CC = [EMAIL PROTECTED]" in my > >> configuration file, and but I never received an email. It > >> went instead to the user who initiated the email. Is this > >> how it works? I was going to set up a mailbox and > >> occasionally parse it for addresses I knew should be > >> whitelisted. Thanks - Al > > _____________________________________________ > > 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 > _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
