I ran into this over this about a year ago, but I got reminded of ittoday:

Regardless of what interface a service is bound to, its outgoingpackets are going out through the interface that the default routesits on.

(Or the route to the specific destination.)

The only packets that are guaranteed to go out the same interface theycame in on are those from sources on that interface's local networks.

This would have bit me hard a year ago if we'd had more load on

I will admit up front that I am not an IMAP person; I'm an MH and exmh person and have been for years. The only reasonI'm playing around with IMAP is that I'm more or less responsible for anIMAP server, so it behooves me to be able to test whether or not it'sworking. I picked Evolution as my IMAP test environment for variousreasons including that it's the Gnome default.

As a result of this, I have formed some opinions about

It's practically an article of faith in the open source world that it'sto your benefit to file bug reports. However, it isn't really so; withmany packages, users actually derive very little practical benefits forgoing through the effort.

The problem is that to file a bug report, you necessarily need to havefound a bug. Since people are generally not software testers, this meansthat you have found the bug in the process of actively trying to use thepackage. Unless you have

Unless I am missing something, in Debian and Ubuntu there is no way tobring up an interface without having it try to obtain an IP address insome way. The interfaces(5) manpage suggests that ' auto ethN ',possibly with ' iface ethN inet manual ' should work, but it doesn'tseem to go in my testing on Ubuntu.

You might rationally ask what use there is in bringing up an interfacewithout an IP address. It turns out that there's a number of things that

We recently had a fun adventure of debugging indirect XDMCP on our Ubuntu LTS 6.06 (Dapper Drake) servers. The problem was that youcouldn't go from the chooser on one server to logging in on another server,although you could log in to the machine the chooser was coming from.

It turns out that this is broken by default in pretty much every modernLinux distribution, and the culprit is IPv6 support. In fact it makes agood illustration of why adding IPv6 support is not

A periodically annoying limitation of Python properties on instances isthat you cannot remove or replace a property. (You can implement del in your property, but this is not the same thing.)

This restriction exists because properties are actually attributes onthe class, not attributes on the instances. Because of how attributelookup works, you can't even sneak a replacement in through theinstance's __dict__ .

This means that you can't use properties to implement a highly efficient'generate once and

This week, we:

• got 13,022 messages from 240 different IP addresses.
• handled 18,021 sessions from 1,234 different IP addresses.
• received 169,572 connections from at least 5,382 different IPaddresses.
• hit a highwater of 43 connections being checked at once.

Volume is about the same as last week ,although evidently we got a big burst of connections some timethis week.

I recently got around to setting up a web site for a top level .orgdomain that has existed for more than a decade but previously neverhad a website or even had a 'www..org' host defined in its DNSrecords. I did this with a name-based virtual host on a machine that hadnot previously been running a web server on port 80.

Within minutes , crackers were poking that virtual host in an attemptto exploit a PHP vulnerability; by contrast, it