>> What about adding one more config var: CONFIRM_APPEND_ALWAYS? By >> default it is set to false. When it is set to true, valid >> confirm-accept tagged emails' envelope senders are ALWAYS appended >> to CONFIRM_APPEND, even if the original pending message has already >> been deleted. > >How would TMDA determine the address to append if the message (or at >least the headers of the message) does not exist on disk? When a >message is confirmed, the appended address is that contained in the >original message, not the address contained in the confirmation >response. > >They are not always the same. We had lots of problems[1] with this in >the past which led to the current (and correct IMO) behavior.
Please excuse my ignorance because I am not 100% sure how it is tracked now. I am new to TMDA, in fact 36 hours ago, I hadn't even heard of it. Is it not possible to somehow track in a file (without the entire original message present) what the original address was? Why not keep just the headers for this purpose, they are no more than a couple of KBytes, unlike some SPAM messages that I have seen at 200K plus. Also, as an aside, Do all users have to have their own pending directory. I saw the option for setting the pending directory, but are problems caused if all users messages are stored in the same directory, a global pending directory. For example, is it ok to set the pending directory to be say /var/spool/tmda-pending and have the messages of all users in that directory. That would be of less concern to me as I have far more room available on /var than /home or /usr/home. ----------------------------------------- Sent by Interlinks Webmail http://www.interlinks.net/ http://www.durhamtelecom.com/ _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
