Re: Lots of logged info when using demime condition to block attachment types

Eli <[email protected]> wrote:
<SNIP>
> Ahh, so the stuff I'm seeing from exiscan that is multi lined is *supposed*
> to be going to a separate log file, but since I'm catching ALL the different
> levels to one, it's all jumbled up together :P  I didn't think of that!
> This I can fix :)
> 
> I'm still curious why the demime part is dumping out all the headers though?
> What's the purpose of seeing that information (I know more info is good, but
> why only for demime)?

I don't think it's specific to the demime code.  Rather exim does it for any
message that gets rejected.  Here is a sample from my rejectlog that was
rejected b/ of a high spamassassin score:

------------------------------------------------------------------------------
2004-07-02 11:56:16 1BgQOb-0003yY-9j H=gsd1.sendthrough.net [69.8.164.119] F=<[email protected]> rejected after DATA: This message crossed our UCE threshold.  Sorry.
Envelope-from: <[email protected]>
Envelope-to: <[email protected]>
P Received: from gsd1.sendthrough.net [69.8.164.119]
        by hermes.sanellc.net with smtp (Exim)
        id 1BgQOb-0003yY-9j; Fri, 02 Jul 2004 11:56:13 -0400
I Message-Id: <6US61V4T7YK5D89OB316OB4AS@9RO5533H108O6JNBT9F8ZTAT1>
F From: American Singles <[email protected]>
T To: <[email protected]>
R Reply-to:<[email protected]>
  Subject: Search Attractive Singles in Your Area
  Date: Thu, 24 Jun 2004 17:20:08 -0400
  MIME-Version: 1.0
  Content-Type: multipart/alternative;
 boundary="Boundary-=_b6125542673761fa465e185e7bd8072ef"
  X-SaNE-itized-By: exiscan 4.30-16
------------------------------------------------------------------------------

As you can see, this also includes a bunch of the headers.

I cannot explain why you see multi-line stuff for demime only when using syslog.
Again, I've never used syslog with exim so I cannot make a good comparison.

thanks,
mikeS
-- 
Michael Sprague  | [email protected]
Partner          | System and Network Engineering (SaNE), LLC
use STD::disclaimer;