Re: [Declude.JunkMail] Possible Missing JM Log lines in 1.75

[Matt]

Scott, There are some minor issues still with logging and processing of whitelisted E-mail.  I'm using WHITELIST AUTH, AUTOWHITELIST ON and PREWHITELIST ON.  Depending on how I whitelist though, I see all sorts of different logging, and on at least two of the methods, PREWHITELIST ON doesn't appear to be working as advertised as it logs fully and runs some filters and/or some DNSBL's.  Here are some examples: ----- WHITELIST AUTH ----- 02/28/2004 00:03:19 Q211601d4018ae229 Skipping E-mail from authenticated user [EMAIL PROTECTED]; whitelisted. ----- WHITELIST IP ----- 02/28/2004 01:35:54 Q36b903ed026c681a Skipping E-mail from IP 24.107.232.14       ; whitelisted [24.107.232.14       ]. ----- WHITELIST SUBJECT ----- 02/28/2004 01:35:57 Q36c505f7028296cb E-mail whitelisted - automatically passing all spam tests [[some string]] 02/28/2004 01:35:57 Q36c505f7028296cb L1 Message OK 02/28/2004 01:35:57 Q36c505f7028296cb Subject: [Some String] Strange message from Root to one of my users 02/28/2004 01:35:57 Q36c505f7028296cb From: something@example.com To: forums@example.com  IP: 156.21.1.21 ID: A64236D8017C 02/28/2004 01:35:57 Q36c505f7028296cb Tests failed [weight=0]: CATCHALLMAILS=WARN ----- AUTOWHITELIST  ----- 02/28/2004 08:57:10 Q9e2a00d101c879e0 RFC-NOABUSE:1 .  Total weight = 1. 02/28/2004 08:57:10 Q9e2a00d101c879e0 Skipping4 E-mail from [EMAIL PROTECTED]  ; whitelisted [[EMAIL PROTECTED]  ]. 02/28/2004 08:57:10 Q9e2a00d101c879e0 L1 Message OK 02/28/2004 08:57:10 Q9e2a00d101c879e0 Subject: Re: Neuz........ 02/28/2004 08:57:10 Q9e2a00d101c879e0 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]  IP: 64.136.30.79 ID: JPGVMWA8 02/28/2004 08:57:10 Q9e2a00d101c879e0 Tests failed [weight=0]: CATCHALLMAILS=WARN Fairly minor, but definitely not intended functionality. Thanks, Matt R. Scott Perry wrote: BTW, I have to throw away lines occasionally because of intermittent CRs that cause problems with parsing.  For my log parsing, I initially tried to use SQL Server DTS to isolate fields and parse from there, but SQL would merge two lines together at times because of a related problem with EOL characters.  A separate parser is doing better, but still occasionally has to throw away lines. I'd like to add my vote to the others for ironing out the few bugs in logging. FWIW, I'm not aware of any bugs with logging (as of the latest interim, which fixes an issue where two lines could be combined if certain control characters appeared in the subject). There are, however, two issues that I'm aware of.  [1] A problem where a flaw in Windows will incorrectly cause corruption to the log file (such as multiple lines getting mixed together), which affects any programs that use multiple processes/threads to save data (including IMail), and [2] The desire for more flexibility in logging (such as choosing whether or not "Msg Failed" lines should appear in the log file).  We're looking into the possibility of changing the logging to bypass the corruption program (by having a centralized process do all the logging), as well as more logging options.  However, these are not currently a high priority.                                                    -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list.  To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail".  The archives can be found at http://www.mail-archive.com. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =====================================================