"Monique Y. Herman" <[EMAIL PROTECTED]> writes: > The RECIPIENT variable may be the address the sender actually specified, > but in the case of forwarding, it's not the address the *person* who > sent the mail specified. Almost all of my mail is actually forwarded > from other servers ... (Yes, it's #131234512 on my to-do list to > straighten all of this out, but in the meantime ...)
Yeah, forwarding complicates things. The RECIPIENT changes to the address of the person where the mail is actually received. If more than one forwarding hop is involved, it changes more than once. All that RECIPIENT reflects is the address @ the host where the mail is actually being delivered. If you have access to the other servers, you might be able to save the original envelope recipient (before forwarding) in a custom header field, using formail, from the procmail package (or reformail, from maildrop). Then tell TMDA to use that field as the RECIPIENT by setting the RECIPIENT_HEADER in your config file. Be careful when you do this! The recipient address, whether from RECIPIENT or a custom header field, is used to construct the Reply-To address in the challenge. If the MTA(s) serving your forwarded address(es) can't properly identify and forward extension addresses, you'll lose the confirmation information and the sender will just get another confirmation request, and another, and another.... > On 2004-02-16, Tim Legant penned: > >> I think it's useful. See below. However, if you want to filter >> against the To: field, you can use a 'headers' rule to do so. There's >> not much value there, though, because valid mail might not have your >> address in the To: field. > > Well, it doesn't help in the case of BCCs, but I can't off the top of my > head think of a situation in which, if someone is BCCing me with > messages I want, I wouldn't just whitelist the sender. I would be > surprised if I ended up on the BCC list of a legitemate email from a > complete stranger. That's a good point and also, some software that sends BCCs won't include your address anywhere in the header, not even in a BCC field. That behavior is allowed, though probably less common than putting just your name into a BCC field (regardless of how many addresses were in the BCC field of the original). The absence of your address in a BCC field doesn't mean much, therefore. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
