Jesse Guardiani <[EMAIL PROTECTED]> writes: > This line in UPGRADE seems a little misleading: > > ------ > The domains of the sender or recipient addresses > are now always added to the list of search keys. > ------ > > Maybe it should read something like this: > > ------ > If a domain is specified in a filter rule instead > of a full email address, the domain will be added > to the list of search keys. > ------
Actually, UPGRADING is correct. If you receive (in the simplest case) mail from <[EMAIL PROTECTED]> and the envelope sender is the same, then all of the from* filter rules will search for any of these strings in the file or db: [EMAIL PROTECTED] yahoo.com In other words, for each address that would be searched (envelope sender, From:, Reply-To: in the case of from* rules), the domain portion of that address is also added to the list, so the list is composed of: the envelope sender address the envelope sender domain the X-Primary-Address: address (if different from envelope sender) the X-Primary-Address: domain (if different from envelope sender) the From: address the From: domain the Reply-To: address the Reply-To: domain If any of those three addresses are the same, only one copy is added to the search keys. If any of the domains are the same, only one copy is added to the search keys. So, if my From: is <[EMAIL PROTECTED]> and my Reply-To: is <[EMAIL PROTECTED]> and my envelope sender is the same as my Reply-To:, the list of search keys looks like this: [EMAIL PROTECTED] [EMAIL PROTECTED] catseye.net Note that, if you never put just domains into your whitelists, the domain portion can never match, which is why this is completely backwards compatible and is also why domains are always added to the search keys. Therefore, you never need to specify a domain in a filter rule and probably shouldn't. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
