David writes:
> The plugins are all in FilterB.plu in the following order:
>
> 1. AVP
> 2. CheckMX
> 3. Trashfinder
>
> The log file shows the following:
>
> B0000301090.MSG trashed, filter noreply@ detected in header.
>
> The "noreply@" filter is in the filteri.dat file; so that must be where it
> is trapped. But why? Trashfinder has the "from" address in the list of
> exceptions, so the email should be passed through without further
> checking.
Trashfinder's exception lists only operate in TF; they have no effect on
other plugins or on SCSMFilter itself.
In this case, TF said the message was OK, but that doesn't stop something
else from filtering it.
> If I put TF in the filteru.plu, so it comes after SCSM has done its work,
> the message will still get trapped by filteri.dat. So it doesn't matter
> where I put TF, before or after, the message will still get
> trashed because filteri.dat says 'No'.
>
> Is that a bug or a feature?
Well, it's a feature of SCSMFilter. It also can happen that SCSMFilter can
trash a message that TF would have deleted. I long ago got rid of any
filtering by SCSMFilter, as TF can do the same filtering, but also includes
exception lists and the like. I just use SCSMFilter to run the plugins (like
TF).
So I recommend using an empty or nearly empty filteri.dat, especially if you
have pass lists.
Randy Brukardt.
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)
