On Sunday 05 July 2015 03:27:53 Erik Christiansen wrote:
> On 01.07.15 22:44, Gene Heskett wrote:
> > On Wednesday 01 July 2015 22:40:44 George Ramsower wrote:
> > > And I did it again, left something undone. I forgot to del the
> > > Re:{Emc-users} in the Subject line. This furthers the confusion
> > > Dammit !!!
> >
> > Yep, guilty here too, because I filter to the emc folder based on
> > that subject line. I have not figured a more dependable way to do
> > it.
>
> I see you're using Kmail, Gene. Can't advise on how to do anything
> with that, and don't use my MUA (mutt) to do that job either. Here,
> it's procmail which sorts incoming mail into mailboxes, and this is
> the rule I use for this list:
>
> OR=2147483647^0 # Max score => immediate success. i.e. OR
>
> :0:
>
> * ^From [email protected]
> * $ $OR ^[email protected]
> {
>
> SUBJECT=`formail -czX "Subject:" | sed -re "s/Subject:// ; s/
> \[Emc-users\]//g"`
>
> :0fhw
> :
> | formail -i "Subject: $SUBJECT"
> |
> :0:
>
> cnc_linux_u
> }
>
> (My unread LinuxCNC mailbox is cnc_linux_u.) The rule is more complex
> than for most lists, because it strips any annoying "[Emc-users]" crap
>
> from the subject, if it's there. Here's one I use on clean lists:
> :0:
>
> * ^List-Post: <mailto:[email protected]>
>
> | mutt_u
>
> Even these two examples make evident that "From", "To:", or even a
> "List-Post:" header can be used for sorting. The top rule is
> fault-tolerant, sorting on presence of either of two header matches.
>
> There's a pile of info in "man procmailrc", and nifty explanatory
> examples in "man procmailex".
>
> Some initial guff I have is:
>
> # Avoid logging clashes. Separate
> log records. MAILDIR=/home/erik/mail # Thanks to Bart
> Schaefer & Ruud H.G. van Tol: LOGFILE=$MAILDIR/tmp_log.$$ # <-
> Each process uses a temporary log. FINAL_LOG=$MAILDIR/log #
> <- Append here, via TRAP, at process exit: TRAP='procmail -p
> DEFAULT=$FINAL_LOG /dev/null < $LOGFILE && rm -f $LOGFILE'
>
> DEFAULT=/var/mail/erik
> COMSAT=off
> OR=2147483647^0 # Max score => immediate success.
> i.e. OR VERBOSE=on
>
> It's handy to have logging on, in case something goes wrong.
>
> Erik
>From someone who understands procmail better than I do, but I find kmail
isn't really fond of having a file dumped into its system that it
didn't put there with its own filtering rules. So ATM I only have two
rules in procmail that do that, one for caught viri from a clamscan
session, gets saved in a /var/spool/mail/viri file, and one that sorts
mail from Dee's NY niece into a folder in kmail. But I've seen it come
in in the log tail, and noted that kmail has to read the directory twice
to see it. If sitting in that dir waiting for something she is sending,
I have to leave, then come back before kmail see's it. So I wind up
using procmail to check for viri, and a trip past spamd, but its kmail
that does the sorting in all other cases. A lot of blackjlist stuff
that I used to do in procmail, is now handled by fetchmail sending
mailfilter in to do a prescan & nuke the real badasses. So they are
deleted at the mail server I use, and fetchmail never even see's them to
download them.
I must admit, staying on top of the mailfiler rules can be a nearly an
hour a day job, so I've been a bit lax of late. And I need to get
better at writing rules, but the actual regex used has too many
surprises to make a universal rule possible.
I get a kick out of the current notice that the internet is finally out
of IPV4 addresses. Thats a laugh, as the spammers have at least 50% of
the address space reserved and have had for years. They'll use a big
block of addresses, different block every day. So the gored oxen you
hear screaming about it are having trouble finding a new class D to use
today. If they are forced to reuse a block of addresses to send their
crap, that will just improve the effectiveness of our filter efforts.
When I write a mailfilter rule, I usually write it to blow that whole
class D space away. And I have 729 lines of rules, most of which hit on
the whole class D (256 addresses at once) none of which other than the
glegroups rule, have been triggered recently. That rule stops 10 to 20
mails a day but thats only because I got tired of their crap not being
properly mimetyped, and virtually unreadable with all the markup crap
glegroups does to a message. If google knew how bad the rest of the
planet hates that, they'd fix it. But its like dealing with Redmond,
folks think webmail is the cats meow, so they keep buying the cat food.
I need to get back at that maintenance again... Maybe when I get this
new mill producing parts, but thats a week+ away yet I expect. Next is
furniture, a shelf to hold the drivers and computer, with a hangdown for
the monitor, keyboard and mouse, and move 300lbs of midden heap so I can
sit down and write code in comfort, this one is NOT going to be a
standup operation. My back has had 500% of its share of that already.
Thanks Erik.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
