Richard, > I noticed today that there is a client_addr field in the r/w database that > stores the source server's IP address. On my setup (Exim4 -> Amavisd-new - > -> Exim4) this is always populated with NULL.
Besides what Noel said, the answer may depend on what is the purpose for which you need the client's IP address. If you only need it for logging purposes (plain log or SQL), in is probably acceptable to fetch it from a mail header, either from a topmost Received header field, of perhaps from some dedicated header field supplied by your MTA. If the information is needed to choose a policy bank, for example to separate mail coming from inside from the rest (so that it may be perhaps treated more favourably), and you only need few (two, three, ...) distinct pockets, then a possible approach is to let amavisd listen on a couple of TCP ports, associate a policy bank with each, and let MTA choose to which content filter it will feed a message based on its own configuration file. A typical application would be to provide a policy bank ORIGINATING for mail coming from inside or from authenticated roaming users. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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/
