On 2004-03-19, Thanos Massias penned: > > > Does anyone see any value in a CHALLENGE_BOUNCE_CC implementation? > > This would enable a copy of the Challenge to be also posted to some > administrative address. > > This serves two purposes: 1) provide a handy indication that a > challenge was generated (in a way that one doesn't have to go over his > server's logs) 2) give the administrator the option of whitelisting an > address by answering the challenge him/herself. Agreed that this is > awkward but sometimes I deal with senders that fail to properly > respond to the challenge (no comments on this please) and prefer to do > this on behalf of them over contacting them, explaining them what to > do, explaining them why the procedure is as it is etc. This makes it > is easy to see when a user hasn't managed to respond to the challenge > in a reasonable period and, for important messages, do the > whitelisting myself.
I just have a cron job email me the summary of the queue, if anything's in it, now and again. My method seems a lot easier than manually culling through challenges looking for the ones that weren't confirmed and should have been ... > It was easy enough to modify send_bounce in tmda-rfilter for this > purpose (though by crude patch results in two extra copies of the > confirmation - one to me as the responder and one to me as the > administrative CC) and gave me some peace of mind. > -- monique _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
