MESSAGE
| DATE | 2008-12-19 |
| FROM | Ron Guerin
|
| SUBJECT | Re: [NYLXS - HANGOUT] tracking mail
|
Ruben Safir wrote:
> There is a couple of problems with this. First, there is no real account for
> hangout, so there is no ./procmailrc file to hang SA off of. Secondly, the
> last time I ran spamassasin it pinned the server's CPU resources.
That's generally a configuration issue. It certainly can pin the CPU,
quite easily depending on what you add into it.
> The procmail file for my personal account doesn't apear to be hit. It seems
> the solution is to prevent domains from not matching the wrong IP addressses.
> More directly, nothing from mrbrklyn.com should be allowed to come from
> anywhere accept my local IP addresses, which I actually thought was the case.
This certainly will prevent someone forging your domain successfully for
the purpose of injecting mail into hangout. And given the likelihood
that you won't get hit again by random matching of somedomain.com to
hangout-at-mrbrklyn.com this may "solve" the problem.
But do keep in mind, that if someone forges my address on spam and sends
it to hangout, everyone's going to get that spam. The real moral of the
story is that you can't trust your subscribers addresses as the sole
gatekeeper of what goes out to your list(s).
However, a second moral to this story may be (especially given the
restriction you plan on enforcing above) that doing nothing is the
appropriate thing. This is only one piece of spam, and you don't start
major tinkering with infrastructure unless you expect to see more of it.
- Ron
|
|
