At 09:01 2004-01-19 -0600, ISMgr wrote:
:0 B
*^Content-Type: (application|audio)
I do not recall that there is any Content-Type which _STARTS_ with "audio".
*^.*name=.*.(vb[esx]|ws[hf]|c[ho]m|bat|cmd|hta|exe|lnk|pif|scr|shs)
/etc/messages-rejected
## porn spam
:0 B
* sex|porn|lover
/dev/null
Whoa, WAY too basic there. Mere presence of a word - or WORD PART - will
blow a message away forever? I wouldn't be the least bit surprised if some
of these strings might appear by chance in the BASE64 encoding of an
attachment...
Here's a pointer: while learning procmail, DO NOT file stuff to
/dev/null. You can't recover it from there. Put it in some other file,
then when you're wondering where something went and why, you can go check.
## Nigerian spam
:0 B
* nigeria
/dev/null
Again, don't file to /dev/null until you have a solid clue what you're
doing. That's also entirely too basic -- if you want to catch Nigerian
scams, you'll need to use scoring ('man procmailsc'), which allows you to
weigh a message based on multiple terms, and say, how frequently each might
appear, or ramp the score up based upon two terms appearing together.
Separate from this discussion, I'll see about posting my Nigerian scam
recipe later today.
When I send an attachment that is an MS Office format (excel in this
case), it isn't coming through at all.......no instance in
/etc/messages-rejected, but the maillog stamps the acceptance of the message...
Er, is the above preceeded by a LOGFILE and VERBOSE construct?
Your first line of inquiry when something doesn't work should be to examine
your VERBOSE procmail logs. Always. It'll tell you where procmail filed a
message, and which recipe caused it to happen.
Have you considered using a SANDBOX as I earlier mentioned? Take the above
/etc/procmailrc OUT OF SERVICE (because in the meantime, you're going to be
misfiling email with it), and place it into a standalone script file,
encompassed by a sandbox. Then (as per the page that describes my sandbox
setup and provides starting files for it), throw an existing mailbox at it:
formail -s procmail -m sandbox.rc < saved_messages.mbx
This allows you to see how the recipes will handle those messages. TO
create messages, simply mail yourself stuff and make copies from your mail
client (or using a text editor).
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail