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

Michael F. Sprague wrote:
> Eli <[email protected]> wrote:
>> I've noticed on my servers that I get way too much info logged to
>> syslog (what I use to log all exim log data) when the demime ACL
>> condition blocks an attachment type.
> <SNIP>
> 
> Correct me if I'm wrong b/ I never used syslog to log exim info, but
> if you 
> use the stock exim logging you should get what you want.  You'll have
> one 'main' logfile (I usually call this mainlog) which is a bunch of
> 1 liners. 
> Then you'll have a 2nd log (I usually call rejectlog) which is
> multi-line and only contains entries for any message that is rejected
> for any reason. 
> 
> There may be a way to seperate this info using the syslog method but
> I am not sure.  In any case, I don't think this issue is related to
> exiscan in particular but rather exim in general.

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)?

Eli.