Yesterday my ASSP setup (the latest 1.4) within short time generated a maillog file of about 6.6 GB in size !
This is what filled the log: Aug-23-08 23:59:55 [MSGID-sig] 195.186.19.62 <> to: [EMAIL PROTECTED] info: found expired MSGID signature in [In-Reply-To:] Aug-23-08 23:59:55 [MSGID-sig] 195.186.19.62 <> to: [EMAIL PROTECTED] info: found expired MSGID signature in [In-Reply-To:] Aug-23-08 23:59:55 [MSGID-sig] 195.186.19.62 <> to: [EMAIL PROTECTED] info: found expired MSGID signature in [In-Reply-To:] Aug-23-08 23:59:55 [MSGID-sig] 195.186.19.62 <> to: [EMAIL PROTECTED] info: found expired MSGID signature in [In-Reply-To:] Message ID tagging was on 'block' send 250 OK to ISP was ticked The offending IP was not in any ISPIP or other settings. A simple restart didn't solve the problem. Only when I restarted ASSP and turned off Message ID tagging the message went through. This brings me to the following questions: - what could have caused this ? - would it be possible to limit the maillog size from exploding under attack (for example by stopping logging after x entries per day) and as a proposal for the multithreaded version: could threads be reserved for whitelisted entries only ? -- View this message in context: http://www.nabble.com/Huge-maillog-file-tp19132785p19132785.html Sent from the assp-test mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
