I know this must be something I've overlooked as it just seem so silly that penpals would work in reverse order.
All outbound email from my location sends through a SMTP server which forwards to the AMAVIS filtering server before leaving the network. Inbound email comes into the AMAVIS server, and once reviewed by amavis is forwarded to the SMTP server for POP3/IMAP access. In this setup, there are thousands of domains being scanned, and amavis as well as postfix utilize a mysql db to determine where to forward the email after it's scanned via a postfix transport table. With this setup, I typically leave @mynetworks and @local_domains_maps undefined and the setup works great. I am experimenting with penpals now and when I activate it with my current config it seems to only log a penpals scan on one in every few thousand messages. Even messages which the SQL statement should hit (and does hit if i run the SQL statement by hand) are ignored by amavis for penpals purposes. I modified my @mynetworks and @local_domains_maps to have valid data for the local network and my test domain I'm working with. The results of this caused all outbound email from anywhere in @mynetworks to get penpals attributes checked when the sql statement returned data; however, no inbound email would ever produce penpals log entries. Of course my goal is for penpals to mark incoming emails, not outgoing. Do these symtoms ring any familiar bells for anyone that might point out where i goofed? Thanks, - Nate ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
