jonr writes "I just wanted to went (and with luck, get an advice). I have written a system for a employee agency, where registered applicants can subscribe to new jobs. This means 1000's of outgoing emails for every new job posted.
The real headache (besides of convincing other domains that you are not a spammer) is parsing bounced emails.
Sometimes grepping for 550 is enough, but I also want to keep track of full mailboxes, auto-replies and other things.
Parsing all this is a real headache, I curse the non-standardness of this system every time.
I did write something similar in.NET, there I found a package that did just this, but now I am using unix-based tools (PHP), and I still haven't found a good solution.
Grepping bounces will get the most of it, but not nearly enough. Some tricks that I have considered:
Running netnanny under mono. (even possible?)
Using MailMan to parse it (I think it has something to parse bounces)
jonr writes "I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years. In recent years, a number of program analysers like PREfix and PREfast in Microsoft have been used to check references, and give warnings if there is a risk they may be non-null. More recent programming languages like Spec# have introduced declarations for non-null references. This is the solution, which I rejected in 1965.
This is an abstract from Tony Hoare Presentation on QCon. I'm raised on C-style programming languages, and have always used null pointers/references, but I am having trouble of groking null-reference free language. Is there a good reading out there that explains this?" Link to Original Source top
jonr (1130) writes "Phantom doesn't have files. Well, there are no files in the sense that a developer opens a file handle, writes to it, and closes the file handle. From the user's perspective, things still look familiar — a desktop, directories, and file icons. But a file in Phantom is simply an object whose state is persisted. You don't have to explicitly open it. As long as your program has some kind of reference to that object, all you need to do is call methods on it, and the data is there as you would expect.
This is what has been bugging me for years. Why, in the year 2009, after 50 years of OS development, are we still opening and closing files manually? Why don't we just edit data in memory and let the OS handle the physical storage? More in The Register" top
jonr writes "At the Las Vegas Consumer Electronics Show Sony presented the new camera from its Cyber-shot product line. The DSC-G3 comes with a Zeiss lens with 4x zoom, a large 3.5" touch display and 4 GBytes of internal memory. Most interesting is the camera's software that includes, among other things, face and scene recognition, based on Busybox and Kernel 2.6.11 for the Access Linux Platform (ALP)." Link to Original Source