Ronald Wiplinger <[EMAIL PROTECTED]> writes: > Mark Horn wrote: > > It seems I expected that only if it is in the file confirmed it would > go to the next line. Sorry, was my fault. I just used the default > config file and remarked all what I did not used now.
The sample incoming filter is just to demonstrate how the various rules are used. The individual example rules in the file are not very useful. You need to figure out rules that work in your particular situation. To clarify one thing, TMDA reads the incoming filter file from top to bottom. The first rule that *matches* is the rule that is used. If a rule does not match the incoming email, TMDA goes on to the next mail. In your example, the email did not match anything in the filter, including any addresses in the confirmed file, until it came to the rule that says that any mail less than 10000 bytes should be delivered. Since that was the first match, it delivered the mail and stopped processing the filter. > ronald+confirm+1038508371.4717.329c4c@dns > > Above you can see, that it does not use the full qualified domain > name, just the real host name. How can I set this fix to > mail.elmit.com ??? TMDA uses the address that the email was sent to in order to create this confirm email address. If you have processing on your mail system that plays games with that address, or if you forward incoming mail to a second address, the original recipient address can be lost. You have two choices of how to handle this. You can fix your MTA's configuration, if that's the problem or, if you want to use the same base address for all confirmations, regardless of the address the original email was sent to, you can set CONFIRM_ADDRESS in your ~/.tmda/config file. See http://www.tmda.net/config-vars.html#CONFIRM_ADDRESS Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
