> > Matt Kettler comcast.net> writes:
> One way to achieve your desired goal would be to have SA tag the
> messages at the MTA level and then craft your delivery agent
> (EG procmail) to parse the SA headers and take action at
> delivery time to drop a message or route it to a spam-bin folder
> fo
On Tue, 9 May 2006, martin wrote:
> Matt Kettler comcast.net> writes:
> > >
> > SpamAssassin cannot be configured to drop mail at all.
> >
> > Based on how SA integrates into the mail chain it can only modify the
> > contents of the message. It has no ability to delete or alter message
> > delive
Matt Kettler comcast.net> writes:
> >
> SpamAssassin cannot be configured to drop mail at all.
>
> Based on how SA integrates into the mail chain it can only modify the
> contents of the message. It has no ability to delete or alter message
> delivery.
i understood this, so just want to ask
martin wrote:
> Dear all,
> spamd/spamc can had a user pref. file for user defined socring/white list
> etc,
> and using milter (spamass-milter) to control drop the spam mail or not.
> my question is, can drop the spam mail based on user pref. file? e.g. some
> user can decide to drop [marked]
Dear all,
spamd/spamc can had a user pref. file for user defined socring/white list etc,
and using milter (spamass-milter) to control drop the spam mail or not.
my question is, can drop the spam mail based on user pref. file? e.g. some
user can decide to drop [marked] spam email, while other ca
