Andreas Pettersson wrote: > Ole Nomann Thomsen wrote:
>> Performing callouts will probably cause it to emit strange noises and >> smoke. > > > Why would it? > It would generate the same amount of connect attempts to FC as it > already does today, but the spam gets rejected instead of accepted and > then bounced. No, see, the problem is nondeliverable spam (NDS). Consider the setup: Net -(1)-> [my box] -(2)-> [FC] At present, I receive everything at (1) and then NDS gets rejected at (2), generating a bounce. That's one connection to the overworked FC per NDS. Using callouts, every NDS causes one callout at (2) and then gets rejected at (1). The load at (2) must be about the same. But then comes the deliverable spam and ham: They will now generate a callout at (2), be accepted at (1) and then delivered at (2). The total difference would the be one additional "VRFY" or "RCPT TO" (ot whatever callout uses) at (2) per deliverable message, wouldn't it? This is to much for FC. (But the bounce problem would be solved, I guess).
