On Fri, 20 Mar 2009, Robert Barty wrote: > If the POP client then reboots and is given a new IP address filter does > not sign the mail. > > The log shows: > > Mar 20 06:42:41 mydomain dkim-filter[31928]: n2KAgdkN003974 not POP > authenticated
This is expected behaviour. When you login via POP, your POP server updates the authentication database with the IP address from which you logged in. That's the database dkim-filter will query when it's deciding whether or not to sign something. If your POP client gets assigned a new IP address for whatever reason, the new IP address is (presumably) not in the database, and so the above condition occurs and the mail won't be signed. The database would be updated again when you log in to the POP server to retrieve mail. Presumably that's not happening. > If I restart the dkim filter it works again (signs mail from the POP > client with the new IP address). The filter doesn't maintain any state about the POP database, so restarting it doesn't change anything. The database is queried for every message passing through the filter. > It seems the filter reads the my popauth.db file only once and never > reads it again to refresh the list of POP client IP addresses. No, that's not the case. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
