Except for someone trying to run a service out of
their house. To
do so, is... well...
[...]?
Trying to do it off a line with dynamic address
assignment -
...which != "out of their house"; for example, my mailserver is in my
condo, but addressed out of a statically assigned /28 - which is
SWIPped and has rDNS delegated to me.
fighting DSL bottlenecks at the DSLAM, etc. etc.
So far this hasn't proven to be a problem. Averaging over the last 30
days, I have used 3158.7 bytes/sec incoming, 2235.1 bytes/sec outgoing
(both figures in error by less than 1 unit in the last place shown,
assuming netstat is telling the truth about byte counts).
Certainly my DSLAM could in principle be maxed out, but that seems
unlikely; more likely would be that my wire would be maxed out,
something that doesn't seem to happen in practice - at least not
unexpectedly. (I have for example deliberately redlined it when
stress-testing it or the networks adjacent to it; I don't count that.)
Is simply not the best way to run a mail server.
Actually, for me, I believe it is the best way to run a mailserver.
That is, of course, taking into account issues such as cost. Yes, if
cost were not an issue, I agree there would be ways in which it could
be run better. But I daresay the same could be said of almost any
mailserver in existence.
I'm not saying people shouldn't do it
actually. I'm merely saying
that when it's done under those conditions, it's hard to complain
about sporadic problems.
Perhaps - but my experience over the past few years has been that I
have fewer problems inbound to my mailserver than through other
mailservers which forward to me.
Now, that could be just a question of what I view as "problems", and
where I see the problem as lying when I see a problem as present. But
since it's my mailserver, it's my metric of goodness too.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B