I hope you all had a better festive season than me. -4 degrees on Christmas morning with a broken boiler in the heart of northern France wasn’t much fun. We perceivered for a couple of nights with the loan of some crappy electric heaters and a temperamental example of French home wiring. We had to give up when the elder family decided it was way too cold and enough was enough. I’m going to cause a lot of pain for somebody at cottages4you today – their emergency numbers were off-line for the duration of our troubles. Update: c4u customer care are now in the office and have been very responsive. If only they could have been like this out of normal hours. Update #2: Situation resolved. c4u do not deny our situation and their errors and have resolved matters accordingly.  Comments: None
|
Insurance companies and health-care providers ask the most ridiculous security questions every time we cross paths. Name, Address, Date of Birth. Every single time they want this triplet of information under the guise of a security verification. I’ve a very good feeling that this is not for my or my accounts security since it’s all pretty much public information isn’t it? Or at the very least obtainable with little effort. The pessimist in me (who is usually right!) believes this triplet is actually an anti fraud measure. It sucks that anti-fraud actually actually prevails over security with near-essential services like these. Comments: 1 Comment
|
I should leave… Dear [Director of customer service@bank], Comments: None
|
One of the most creative videos I’ve seen in ages. Enjoy! You can see more of Tony & Pauls work at freeposterfilms.com. Got to stop lurking around online entertainment and get on with my laundry & packing, I’ve got two very full weeks on the road ahead at APWG and MAAWG. Comments: None
|
Trying to research a few errors in my maillog relating to spf revealed an own goal by the top pished company in the world. 10 interactive terms. Ten is the default, because SPF is supposed to be a “light check”. With eBay/PayPals current deployment of SPF they have scored an own goal. Its so complicated that it does not conform to the RFC and fails (in the defacto implementation) with a permanent error. Take a quick look at why is fails the 10 record test: mx s._spf.ebay.com m._spf.ebay.com p._spf.ebay.com p2._spf.ebay.com liveworld.com emarsys.net c._spf.ebay.com c2._spf.ebay.com c3._spf.ebay.com c4._spf.ebay.com Pheww.. Do you think that’s more than 10 entries? No wonder it’s not helping [X] Your infrastructure is too complicated. Comments: None
|
Just a quick ‘n’ simple howto on installing SPF tests in postfix on ubuntu:
policy unix - n n - - spawn user=nobody argv=/usr/bin/perl /usr/sbin/postfix-policyd-spf-perl
That’s it! Here is a citezns bank phish soft failing in the log: Now how can I convince the banks to use -all records?? Comments: None
|
...and mummy Mason too. Congratulations on your last good nights sleep in a couple of years!
As you can see from the close-up she inhereted her good looks from mum
Very best withes to all three of you! You’re all looking very well so now on with the serious business of wetting the baby’s head! Comments: 3 Comments
|
Here is a sneak peek at the next tool in the rrd-client suite. A daemon that monitors your MTA’s logs real-time and feeds stats into rrd-server. Not sending all that mail through spamassassin is really helping my CPU usage too. This is really going to help when I get my colo box next week. Comments: None
|
It would appear that some 3-4 hours of spam was cluelessly sent with a fake from address aimed at me, but this time there was no grief with it unlike the last big last time. This attack was about half the size of the awesome flood a year ago.
So this gave me an excellent opportunity to test out many mail servers sending me ‘ham’ via the greylist service (set to accept after 40 seconds). So here is a small random selection: X-Greylist: delayed 1107 seconds (postfix) So a revisit time of 580-620 seconds might be worth a spamassassin point or two. One observation that also caught my eye is that yahoo are sending a lot of user-unknown messages out of the SMTP session. Yahoo are whitelisted on postgrey and hence have no greylist header added (though I wish it would with the reasoning) so I caught a lot of their blow-back for user unknown errors. Thats just wrong Y! guys! Comments: None
|
With nothing better to do on a dull/hungover Sunday morning I thought I’d investigate a rumor I’d heard in the week regarding greylisting. sudo apt-get install postgreyThen a quick edit of postfix’s main.cf. At this time I also reduced the timeout from 5 minutes to 40 seconds since all I’m interested in is if they come back at all. At the same time I deliberately turned off all rbl’s so that I’d get a big & fair dataset on the trap server. Then all I had to do is sit and watch. Now of course this let through all the spam being sent via ISP’s relays but looking for direct sending bots running on DSL’s is pretty easy because they don’t have Wanadoo/Orange or Tiscali in the headers X-Greylist: delayed 651 seconds by postgrey; <image /knob pills X-Greylist: delayed 602 seconds by postgrey; <PDF X-Greylist: delayed 602 seconds by postgrey; <Ecard X-Greylist: delayed 605 seconds by postgrey; <Image/knob pills X-Greylist: delayed 608 seconds by postgrey; <PDF X-Greylist: delayed 604 seconds by postgrey; <Stock X-Greylist: delayed 685 seconds by postgrey; <Ecard X-Greylist: delayed 603 seconds by postgrey; <StockThese were all definitely dialup/dsl pools. The interesting thing is how long they all took to come back but nevertheless it shows that at least some bots are well wise to greylisting. Comments: None
|
| « newer posts | previous posts » |
