Paul van Tilburg: Off to CONCUR 2007
I had some posts planned, but didn’t get around to it. I’m off to Lisbon
for CONCUR 2007 now. I’m flying with
TAP (flight TP661) at 18:05. I’ll be back next
Saturday (September 8)!
It will be published on placesofinterest.info, which is currently in public beta state, but definitely worth a look (just don't use IE, but I doubt you use non-free software, right?). I'll blog more about placesofinterest.info as soon as the page is finished.
As usual, the pano was created with the help of The Gimp, hugin and enblend. The only commercial software involved was the software for the Imacon scanner at university. Original resolution: 24044×2551 pixel, stitched from 14 slides. If anybody is interested - large format prints for Debconf participants are available for the cost of paper and ink.
postfix/master[7287]: warning: service "smtp" (25) has reached its process limit "100": new clients may experience noticeable delaysThis is not really because your system is overloaded. To me, it looks more like a (deliberate?) malfunction of some spammers software. When you rejected it's spam mail a few times, it starts opening up lots of connections to your system, but never sends any data. They just sit there and time out.The solution is simple: limit the number of connections per client. Make sure the 'anvil' service is enabled (default at least on Debian) and then add
smtpd_client_connection_count_limit = 10to your postfix configuration.You should now begin to see messages such as
postfix/smtpd[21680]: warning: Connection concurrency limit exceeded: 11 from unknown[210.210.247.52] for service smtpA corean cable IP. Yeah, I don't think this would have been legitimate mail traffic anyway.Feel free to pick the limit value even lower than 10 on really busy systems (or if these 'attacks' become stronger) - most people should never need more than 2 parallel connections (note: you can send multiple emails over one connection, there isn't much to be gained by using more than one connection).
You can, of course, change the way date is shown. That's because 'YYYY-MM-DD hh:mm' is also a valid input format for date as it is 'YYYY/MM/DD'.
ls -l while read perms links user group size d t name
do
echo $perms $links $user $group $size $( date -d "$d $t 1 day" ) $name
done
lbdb is invoked at the beginning of procmailrc harvesting From: addresses
from all incoming mail, so that they can later be queried with mutt. It's
really neat.
However, if it's put at the beginning of procmailrc, it harvests From addresses
from spam, too. This causes the ldbd databse to become very big, slow to
query, and in some unlucky cases, to return lots of bad results.
Problem is, I run the spam filter AFTER I delivered to the mailing lists. The
rationale is that mailing lists already do their own spam filtering to some
useable level. At least those I'm subscribed to.
So, my current procmailrc goes like:
feed a copy through lbdb
filter list 1
filter list 2
...
filter list N for N very big
filter out spam
deliver to inbox
Now, is there a way I could invoke lbdb for every mail except what is caught
by the spam filter? A way, I mean, that doesn't involve hooking into each and
every of the N list rules an lbdb invocation?
Here is the way. In .procmailrc, add:
TRAP=~/bin/scan-nonspam
Then write ~/bin/scan-nonspam:
#!/bin/bash
if [ $ LASTFOLDER:0:4 != 'spam' ]
then
/usr/bin/lbdb-fetchaddr
fi
exit 0
For reference, this is the documentation of TRAP:
When procmail terminates of its own accord and not because it received a signal, it will execute the contents of this variable. A copy of the mail can be read from stdin. Any output produced by this command will be appended toAnd this is the documentation of$LOGFILE. Possible uses forTRAPare: removal of temporary files, logging customised abstracts, etc. See alsoEXITCODEandLOGABSTRACT.
LASTFOLDER:
This variable is assigned to by procmail whenever it is delivering to a
folder or program. It always contains the name of the last file (or program)
procmail delivered to. If the last delivery was to several directory folders
together then $LASTFOLDER will contain the hardlinked filenames as a space
separated list.
Next.