MySQL Student wrote:
Hi,
Maybe this will sound dumb but wouldn't it be perfectly
safe to blacklist "example.com" after all, that isn't a
domain your ever going to get mail from.
I could be wrong, but I'm guessing the example.com is the OP's munging.
Yes, that's correct. My apologies.
Are we to make guesses on what else might be munged?
Is just example.com munged or the 172.0.0.1 also munged?
In the future when you munge, make it obvious. Here's
how to do it WRONG:
s...@northpole.com
becomes
s...@example.com
23.45.67.6
becomes
192.168.1.5
Here's how to do it RIGHT:
s...@northpole.com
becomes
x...@xxxxxx.xxx
23.45.67.6
becomes
X.X.X.X
Also, if the same e-mail address or IP number appears multiple
times in the mail, use the same munge char for it. If
different ones appear, use YYYY, ZZZZ, AAAA, BBBB, and so
on for each new successive item.
It just makes it a lot easier on us when we have to tell
you that your munging some critical piece of information
we need to help you and that you need to un-munge if if
you want any help. This way we don't have to guess
as much.
:-)
Ted
PS I suspected example.com was a munge but wasn't willing
to assume it was - spammers can be pretty ingenious.
