procmail
[Top] [All Lists]

Re: Scoring Recipe for repeating addresses?

2002-06-19 18:31:54
On Tue, 18 Jun 2002 18:23:59 -0700, PSE-L(_at_)mail(_dot_)professional(_dot_)org
(Professional Software Engineering) wrote:
=> Once you take a look at the sandbox setup, you'll realize that it is little 
=> more than a generic .procmailrc that sets a few things up so that you don't 
=> deliver messages on forwards, and deposit messages into a separate subdir 
=> from where you normally would.

        In other words, just set it up to change SENDMAIL for
!bang use and direct logs and mail delivery to another area (and
not use any other deliveries). OK, I've reviewed your site notes
and done it for myself -- no small accomplishment for someone
like me who understands very little about shell etc.

=>  If you can write a procmail recipe, you can 
=> use a sandbox.

        Got it going and testing fine. Thanks for the push!

=> If $DOMAINLIST is properly defined to be a regexp to select one of your 
=> domains, yes, that would work

DOMAINLIST=(example\.com|example2\.org|example3\.(com|net)|\
example4\.tld)

* $ ^(To|Cc):.*\/[-+\._a-z0-9]*@([-a-z0-9]+\.)*$DOMAINLIST

=> Sandbox it and begin to discover wild things about procmail.  A sandbox 
=> will allow you to play all manner of what-if scenarios and tweak your 
=> regexps.  You can TRY things without risking your live email, which will 
=> make it a LOT easier to learn about procmail, since you're not living under 
=> the gloomy cloud of "I must get this right the first time or else I'll hose 
=> all my email."

        I really hated that pressurized "open heart surgery"
feeling ... not to mention the times I screwed up ...

=> For instance, I have some complex spam recipes - which I can run against a 
=> saved mail file simply by including the spam rcfile (and perhaps setting a 
=> variable or two) into another rcfile used by my sandbox.  This permits me 
=> to take messages that "got past" my filters the first time and see whether 
=> some changes will catch them in the future

        I'm a windoze (nt4/win2k) desktop type but my copy of
Agent will allow me to dump text files of saved message (good and
spam) into the proper format for FTP to the procmail FrreBSD
machine.

=> or just to see the VERBOSE

        And you wrote "Sheer volume", indeed!

=> You're very welcome.

        I very much appreciate your terrific and on-going help.

        Now I have a couple more related questions to ask if
that's OK.  I notice that your site procmail variable setup
samples strip preceeding (but not trailing) whitespace off for
the TO (and FROM and SUBJECT) headers with:
        * ^To:[  ]*\/[^ ].*

would I not be better off in this case using this form instead of
the simpler form you suggested in your example earlier in this
thread:
        * ^To:\/.*

        Also, if in another recipe I reversed the logic in your
test for non-blank KEYADDR (you suggested):
        * ! KEYADDR ?? ^^^^
wouldn't that give me a positive flag that there are no proper
email addresses in the To/Cc headers for any of my domains? As I
have for years gone thru the struggle of only delivering based on
proper To/Cc headers (and all that entails, I know, I know,
mailing lists etc etc), wouldn't that allow me to reject the
message right then? (And to heck with the Bcc senders)

        Thanks again,

        - Don
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>