Eric Helfgott writes:
> Sorry, I was unaware this was your filter, and didn't know that all the
> functionality it provides would be lost with my suggestion of removal of
the
> offending filter generating the spam.log file entry from Bill that I
glanced
> at. I'm not running TF, so I wasn't all familiar with it.
Humm, out of curiousity, how *do* you deal with filtering spam? SCSMFilter
and Antibanner are far too weak, unless you have virtually no mail at all.
The 20 mailboxes here generate more than 1000 spam a day *after* RBL and
user name blocking -- it would take forever to deal with that much mail, no
matter how wonderful your viewer is.
> Still, I would say to Bill that the log line entries here for TF are
> formatted different enough from other IMS filters that AVP will fail in
> parsing it. The trashbin viewer functionality in AVP won't work at
present
> with such entries in the log. It will halt processing upon encountering a
> parse error on an offending line.
That's too bad; I made the lines work with Spameye (at the time, I didn't
even know that AVP had a viewer). If it just ignored the offending line, it
would be much friendlier (I know that might not be as trivial as it sounds).
> If there is presently a way in TF to log entries to a separate file, this
> would restore this functionality. AVP logs to spam.log in the standard
> format, and provides more detailed information in a separate log file
> (AVP.LOG) that it maintains.
He could change the name of the log file (found on the Log page of the
manager) to something else, and then TF would write there instead. But of
course he'd lose all of the information about why something was filtered (if
he turned on the header option, it would be written into the message header,
but finding it would be a time waster unless the viewer was looking for it
explicitly).
> If Randy made TF's entries conform to what the other spam.log entries look
> like, then the information would be presented nicely in the AVP trash bin
> viewer interface.
I didn't do that because the existing lines made a file that was much too
large - most of the information in it is useless. The only things that
matter are the message name and the (real) filtering reason, the rest of it
is just waste space. Besides, there isn't any real filtering reason given in
the log, and that's all that's really important (the fact that it was
filtered is obvious!). The whole reason for writing into this log as because
Spameye would then display the filtering reason; there wasn't any other way
to do that and see other plugins filtering as well.
In any case, I'm not going to be putting new features into TF Classic -- the
code base is just too different from the other versions of TF. I probably
should add a way to shut off the Spam.Log altogether in TF Pro (rather than
just allowing it to be redirected) -- the log gets far too large and too
fragmented to be useful (after a week, it takes 20 minutes to copy it to a
save location, presumably because the 20000 fragments make it inefficient.
(TF Gateway doesn't write anything like the Spam log anyway.) Beyond that, I
don't know. What specifically is AVP looking for in the log?
> Otherwise, to put it simply, TF isn't compatible with the trashbin viewer
> feature in AVP.
I'm sure he can change where TF writes its log lines, and then he could at
least use the AVP viewer.
Randy.
This is the discussion list for the IMS Free email server software.
To unsubscribe send mailto:[EMAIL PROTECTED]
Delivered by Rockliffe MailSite
http://www.rockliffe.com/mailsite
Rock Solid Software (tm)
