1st off: It was my own damn fault.
If you leave an http proxy open on a system that also
does smtp, spammers will use the http proxy to talk to
the smtp daemon and send spam (since the smtp sees
communication from 'localhost').
It would be REALLY nice if mman would block/forbid
proxying for localhost/127.0.0.1 by default.
What valid reason is there to proxy for localhost, anyway?
Logged In: YES
user_id=432781
I was thinking about adding a feature that allows filtering based on
resolved IP address, which would have been useful for the recent crap
verisign pulled with making unregistered domains resolve to a verisign
website. However, as you pointed out... the error was in your
configuration, proxying to localhost is useful in some situations so I
don't want to hardcode anything that would prevent it.
Logged In: YES
user_id=6449
Yes, there are a few valid reasons to proxy to localhost. But I submit
that they are few and far between, and that the default config should not
allow it. I suspect the most used localhost proxy is as a spam relay :-(
My request would be
config file:
proxy_localhost=<true/false> with false as the default.