> I understood him to mean that when a message is sent to an > external domain from inside a local domain, the recipient's > name(s) would be captured and placed into an amavisd-new > whitelist. This could probably be done by scripting a program > to scan mail logs, collect the data, and place it into a > table, either static or dynamic. I have a feeling however > that once this was implemented, undesirable email addresses > would end up in the database. Once that started happening, > the idea would end up getting scrapped, but that is complete > conjecture on my part. If done correctly I could see the > value of this (at least conceptually).
This is a 'feature' of some systems, like GFI. One reason for doing this might be: User [EMAIL PROTECTED] sends email (through amavisd-new) to [EMAIL PROTECTED] [EMAIL PROTECTED] replys back (with content from original email) and domain.com's amavisd-new blocks it as spam. (it happens) First, you woeuld have to send all email out the same box amavisd-new. Second, I would suggest using the AWL feature, OR, maybe look at the reply-to or reference of or whatever headers from the original email (then it doesn't have to send out the amavisd-new system) ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
