Hi all, fixed in assp 2.6.8 *SPAM-Evaporator* build 22293:
- if BlockRepForwHost was configured and any of EmailBlockReportDomain, EmailBlockReport or BlockRepForwHost was changed, queued forwarding requests failed in case any of these vales is changed, the BlockReport-Forwarding queue is cleared now changed: - If delaying is enabled and DelayUseNetblocks is set to 'On' and the perl module 'NetAddr::IP::Lite' is installed and enabled, assp resolves the SPF record for the domain used in the envelope sender address. If the connected IP-address is valid (in terms of the SPF-record) all IP-adresses and ranges from the SPF-record are hashed and the hash is used (instead of the the connected IP-address) for delaying. This new behavior makes sure, that another valid IP-address, that tries to deliver the same mail after the first valid address was delayed, will be not delayed. If no SPF-record is available, the SPF-record is invalid or the connected IP-address is not valid - the connected IP-address will be used for delaying (old behavior). Because it is expected that a system will try to connect again after it was delayed, the SPF-records are cached inside assp. The records are stored in assp/tmpDB/files/SPFRecCache.sav and refreshed by the MaintThread, if any TTL gets outdated. Thomas
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
