Thank you for the answer Davide. That basically means that as long as a source address sends e-mail, the entry will immediately pass through the greylisting.
I know, I know, I should have read the man pages, but wasn't anywhere near a machine to access the server... :) Thus, the 30 day expiry time is excessive overkill, and possibly a 14 day window might be better under normal operating conditions. In this particular case of our server, I am going to leave it, as it is a low volume private type server, rather than commercial. Thursday, June 22, 2006, 8:26:26 AM, you wrote: > On Mon, 19 Jun 2006, Jorn Hass wrote: >> I am not sure if an incoming mail resets the date-stamp as it comes >> in, back to the original 30 days, or wether the time-stamp just gets >> left to the initial access. In which case it would mean that the >> stream mail would never expire. Davide can possibly confirm/deny >> that... > From the GLST man page: > --exptimeo NSEC > Specify the expire timeout for triplets that have been successfully > accepted by the glst module. Every time a triplet is accepted (the > remote mailer retried after the blackout window set with --timeo) the > count of successfully accepted messages is increased, and the record > timestamp is updated with the current time. During cleanup, if the > timestamp is found older that the current time minus the timeout > specified with --exptimeo, the record (triplet plus record metadata) > is purged from the glst database. -- Best regards, Jorn mailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
