>>It does nothing to actually fix the core problem, i.e. buggy software
>>and poor support, but I'm offering this suggestion for those of you
>>pushed against the wall by this.
>
>So lets see, we build a product that adheres to the IETF standard for MTA
>relaying, and you call it "buggy" as a result? I don't think that's fair.
Then perhaps you need to bend the standard, as the Unix g00r00s have done
with Sendmail. (And yes, it is still buggy, considering that regardless of
whether it should be allowed, when it HAPPENS -- when that volume of mail
comes into the SMTP port, post.office cannot handle it, and crashes
repeatedly, and allows its disk to fill up, suspending or interfering with
other services. Yes, I know this was fixed to a certain extent in 2.0,
but post.office simply cannot handle the load that others seem to be able to).
>What we're working on is a workaround to the problem, one that doesn't
>corrupt the spec we must adhere to.
Not really possible, Lee. Either you adhere to the standard, and allow the
spam to flow, or you violate it by adding software filters.
It may be moot if the hardware filtering idea works.