-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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. 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. - -- Best regards, Thanos Massias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows 2000) iD8DBQFAW2dTOs3ahFN/QpkRAoUUAKCoZI8EtXG72T5w/IcWNMWpN3NlZACfc8jj PVQRH7LVvTFKBWEKnCiub4w= =xJyP -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
