Ruud wrote:
I know i could let SpamAssassin only add its headers, without
modifying the existing ones, but it implies that the average user
know what to do with them. And that's not always the case.
About the only system that can not filter on specific headers is Outlook
Express. But OE supports IMAP, so you can pre-filter for them.
(like putting all list messages in a lists folder)
Like i already said, it's a customer site and i have some limit in what i
can do. I can certainly suggest, but i cannot impose.
We cannot switch to IMAP. I can surely set up rules in Outlook to filter
specifice headers, but i'd have to do it personally, manually, on every
client; if i put a ***SPAM*** in the subject, instead, everyone is able to
set up a rule to filter it, because it's simpler.
Thank you anyway for your suggestion.
About my original problem posted, which was forgotten between spam and
headers and other arguments, i found that is a postfix issue: the message
that got through my recipe - and that led me to the wrong way - was not the
original one, but a copy of it we send to an archive user using the
"always_bcc" postfix parameter.
The original message never got processed by procmail. I discovered it is
because if it is destined to an external recipient it won't be passed to the
"mailbox_command" command. So i have to set up a full filter command.
Thank you again.
--
Francesco Abeni
f(_dot_)abeni(_at_)givi(_dot_)it
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail